YouTube Revenue Estimator
Estimate YouTube revenue from views and RPM. Results are illustrations, not payment promises.
- Est. revenue
- $350.00
- Per view
- $0.0035
- Views
- 100,000
- RPM
- $3.5
Runs in your browser. Nothing you enter is uploaded.
Overview
Ad revenue on YouTube reduces to one multiplication, which is why the estimate is easy and the interpretation is not. Views divided by a thousand, multiplied by RPM, gives the figure. Everything difficult about the question lives inside RPM - a number that varies by topic, audience country, season, video length, and the day of the month you happen to be looking at.
This calculator takes monthly views and an RPM figure and returns estimated revenue, along with what that implies per individual view. It is a projection tool: change the RPM and watch the answer move, which is a better use of it than treating any single output as a forecast.
The honest framing is that you supply the hard part. The calculator does the arithmetic reliably and knows nothing about your channel.
RPM versus CPM, and why the gap is the whole story
These two acronyms are the source of most disappointment about YouTube earnings. CPM is what advertisers pay per thousand ad impressions. RPM is what lands in your account per thousand video views, after YouTube takes its share and after all the views that carried no ad at all are counted in the denominator. RPM is therefore always the smaller number, often substantially, and it is the one that answers "what did I earn".
The reason the gap is large is that many views are not monetisable. Viewers with ad blockers, viewers on Premium, videos where advertisers declined to bid, and impressions that never happened because the viewer left before the pre-roll all sit in your view count and contribute nothing to the ad line. RPM absorbs all of that automatically, which is exactly why it is the right input for this calculation.
So take your RPM from your own analytics rather than from a general figure. YouTube reports it directly, and it is specific to your topic, your audience geography, and your video lengths in a way that no published average can be. A channel whose audience is predominantly in high-CPM advertising markets and a channel with the same view count elsewhere can differ by a multiple, not a percentage.
- CPM is what advertisers pay; RPM is what you receive per thousand views.
- RPM already accounts for unmonetised views and YouTube’s revenue share.
- Read your own RPM from analytics rather than using a generic figure.
- RPM moves seasonally - advertising spend is higher late in the year.
What the estimate leaves out of channel income
Ad revenue is one line among several, and for many channels it is not the largest. Channel memberships, Super Thanks and Super Chat, Shopping, and YouTube Premium watch-time payments all arrive through the same programme and none of them appear in this calculation. Off-platform income - sponsorship, affiliate links, your own products, consulting that came from being visible - is frequently a multiple of the ad line for smaller channels with engaged audiences.
It also ignores every cost. Editing time, software, equipment, thumbnails, music licensing, and tax all sit between the estimated figure and anything spendable. A channel earning a few hundred a month in ads while spending twenty hours a week on production is not earning a few hundred a month.
Where the calculator earns its place is in scenario work. Enter your current views and RPM to get a baseline, then ask what doubling views would produce, or what a shift in audience geography that moves RPM by a dollar would mean. Those comparisons are robust even though the absolute figure is soft, because the same uncertainty applies to both sides.
The division behind the estimate
Views are divided by 1,000 and multiplied by RPM to give estimated revenue, displayed to two decimal places. The per-view figure is a restatement of the same relationship: RPM divided by 1,000, shown to four decimals so the value is legible at typical RPMs. Both inputs are read as plain numbers, and a blank or non-numeric entry is treated as zero.
There is nothing else in the model. No account connection, no analytics lookup, no assumption about your niche, no adjustment for country mix or video length, no revenue share applied - that share is already inside the RPM you provide. The calculation is linear, which means it will happily project a figure from a hundred million views at an RPM you invented.
Because it is linear, it also cannot express the things that make real revenue non-linear: a month where one video carries most of the views at a different RPM from the rest, or a change in the proportion of Shorts, which monetise on a different basis and pull blended RPM down. Feeding in a blended monthly RPM handles this adequately for a monthly estimate and poorly for anything per-video.
A 100,000-view month at two different RPMs
Input
Monthly views: 100,000 RPM A: $3.50 RPM B: $1.20
Output
A → Est. revenue $350.00 · Per view $0.0035 B → Est. revenue $120.00 · Per view $0.0012
Same audience size, nearly a threefold difference in outcome, and neither RPM is unusual - the spread between topics and audience regions is genuinely that wide. This is the argument for pulling RPM from your own analytics rather than a general figure: guessing wrong by two dollars on a 100,000-view month misestimates the result by $200, which is more than the whole answer at RPM B.
Limitations
- RPM is entirely your input. The calculator has no knowledge of your niche, audience geography, or season and cannot suggest a realistic figure.
- Only ad revenue is modelled. Memberships, Super Thanks, Shopping, and Premium watch-time payments are excluded.
- Off-platform income - sponsorship, affiliate, product sales - is not represented at all, and is often larger than the ad line.
- No costs, taxes, or production time are subtracted, so the output is gross platform revenue rather than earnings.
- The model is linear and blended. Shorts, long-form, and individual outlier videos monetise differently and cannot be separated here.
- Eligibility for monetisation is assumed. A channel outside the Partner Programme earns nothing regardless of what the arithmetic says.
When not to use this tool
- If you are estimating what a sponsor should pay rather than what ads will pay, a CPM-based calculation on delivered impressions is the right model.
- If you want to know whether a video length fits a platform tier before publishing, the length checkers answer that instead.
How to use it
- 1
Pull your RPM from YouTube Studio for a full month or a rolling 28 days rather than using a published average.
- 2
Enter that RPM with your monthly view count and note both the revenue and the per-view figure.
- 3
Re-run with an RPM a dollar higher and a dollar lower to see how wide the plausible range is before you rely on any single number.
- 4
Add your non-ad income separately and subtract production costs, since neither appears anywhere in the output.
Questions
Where do I find my actual RPM?
In YouTube Studio, under the revenue tab of your analytics, reported for whatever date range you select. Use a full month or a rolling 28 days rather than a single day, because daily RPM swings considerably with which videos happened to get views.
Why is my RPM lower than the CPM figures I see quoted?
Because they measure different things. CPM is the advertiser-side price per thousand ad impressions before YouTube’s share; RPM is your side, per thousand video views, after the share and after every unmonetised view is counted in the denominator. A large gap between the two is normal, not a sign that something is wrong.
Do Shorts views earn the same as long-form views?
No - Shorts are monetised through a separate pooled arrangement and typically produce a much lower RPM than long-form watch time. A channel posting both will see a blended RPM that shifts as the mix changes, so a single RPM input describes a month with a stable mix and misleads on one without.
How far ahead can I project with this?
Treat it as a one-month arithmetic check rather than a forecast. Projecting a year forward compounds two uncertain assumptions - that views grow as expected and that RPM holds - and RPM in particular is seasonal enough that a figure measured in November flatters the rest of the year.