YouTube Shorts RPM Calculator

Estimate YouTube Shorts revenue from eligible views and your own editable creator RPM per thousand views.

How to calculate youtube shorts rpm

  1. This Shorts revenue tool uses a direct relationship between views and creator revenue per thousand views. Enter the view count and an RPM measured on the same basis. The calculation divides views by one thousand and multiplies by the entered RPM. The second result shows the same rate scaled to one million views, making it easier to compare campaigns without confusing a tiny per-thousand rate with a per-view payment.
  2. The initial $0.05 RPM is an unverified editable illustration, not a YouTube average, official payout rate or guaranteed minimum. Use a value from your own Shorts analytics when possible, and match the time period, eligibility rules and view definition used to derive it. Geography, monetization status, advertiser demand and audience mix can all change results. A single historical RPM should be treated as one scenario rather than a reliable prediction for every future upload.
  3. Creator RPM already represents revenue attributed to the creator on its stated view basis. Do not subtract another revenue-share percentage from this output unless your input was something other than creator RPM. This model does not calculate advertising pool allocation, music licensing or monetization eligibility. It also excludes sponsorships, affiliate income, merchandise, production expenses and income tax. Whole nonnegative view counts and nonnegative dollar rates are accepted; empty or invalid entries show N/A.

Formula: estimatedCreatorRevenue = eligibleViews / 1000 * creatorRPM; revenuePerMillionViews = creatorRPM * 1000

Formula

estimatedCreatorRevenue = eligibleViews / 1000 * creatorRPM; revenuePerMillionViews = creatorRPM * 1000

Where:

Dollar inputs
= USD amounts on the same transaction or period basis described above
Percent inputs
= Editable percentage points, divided by 100 for calculation

Worked example

At the illustrative $0.05 RPM, 1,000,000 views are divided by 1,000 to give 1,000 revenue units. Multiplying by $0.05 estimates $50 of creator revenue. The revenue-per-million result is also $50 because the scenario uses exactly one million views. This is arithmetic based on your rate, not a platform commitment.

If your own matching analytics support a different $0.08 RPM, 250,000 eligible views produce 250 units of one thousand views. Multiplying 250 by $0.08 gives $20. At that same rate, the scale reference becomes $80 per million views. Entering zero views produces zero estimated revenue without suggesting that a channel has earned any minimum payout.

Building Shorts revenue scenarios from matching analytics

Use comparable periods when collecting an RPM assumption. A channel’s recent Shorts revenue divided by the corresponding eligible views, multiplied by one thousand, can provide a scenario input if the underlying definitions align. Do not mix long-form revenue with Shorts views or use total channel revenue that includes unrelated products. Preserve the original analytics period so you can later compare the forecast with actual results.

For planning, run a low, middle and high RPM scenario against the same view target rather than treating one number as a promise. Then compare estimated revenue with editing, filming and distribution costs in a separate budget. Shorts may contribute to a broader audience strategy, but sponsorship or merchandise revenue should not be silently included in an ad-revenue RPM. Keeping those streams separate makes the business assumptions easier to review.

Frequently asked questions

No. The $0.05 starting value is only an editable numerical illustration and should not be treated as typical earnings. YouTube does not owe this amount merely because a video receives views. Replace the example with your own observed creator RPM and evaluate a range when planning future uploads.

Related calculators

Illustrative US estimate only. Verify account-specific rates, fee bases and eligibility with the provider. Editable defaults are not guarantees. Taxes and unlisted charges are excluded.