YouTube Earnings Calculator – See What Your Views Could Pay

Same views, different RPM

Views alone do not set the payout. These boxes keep your views fixed and change only the RPM, so you can see how much the rate itself matters.

Related tools

How it works

Understanding YouTube earnings

The formula: views divided by a thousand, times RPM

One division and one multiplication give every earnings figure on this page, and the RPM you enter decides all of them.

Earnings equal views divided by 1,000, multiplied by RPM, where RPM is the revenue received per 1,000 views, after YouTube’s share, as the page’s own FAQ defines it. At the defaults, in total mode, 1,000,000 views at an RPM of $3.00 give 1,000,000 divided by 1,000, which is 1,000, times $3.00, which is $3,000.00. The per-view figure is the same calculation written smaller: $3.00 divided by 1,000 is $0.0030 per view, and $0.0030 times 1,000,000 is again $3,000.00. The page’s own FAQ confirms the anchor in words: at an RPM of $3.00, 1,000,000 views pay an estimated $3,000.00, at $1.00 they pay $1,000.00, and at $10.00 they pay $10,000.00, and entering your own RPM from YouTube Studio gives an estimate based on your channel.

Every figure in that table was produced by this page’s own calculator and is quoted exactly as displayed, including the per-view figures, which are the RPM divided by 1,000 in every row. The table’s shape is the whole lesson of the page: earnings scale linearly with both inputs, so doubling the views doubles the earnings at a fixed RPM, and doubling the RPM doubles the earnings at fixed views. At RPM $3.00, 100,000 views give $300.00 and 10,000 views give $30.00, which are the million-view figure divided by ten and by one hundred, and at 1,000,000 views, doubling the RPM from $3.00 to $6.00 doubles the earnings from $3,000.00 to $6,000.00. Linearity is convenient for planning and dangerous for prediction, because it means a small error in the RPM input produces a proportionally equal error in the earnings figure, and the next section explains why the RPM input is the least certain number on the page.

Total mode and month mode: the same arithmetic, a different label

Switching modes does not change the formula. It changes what the views figure means, and the result’s label follows it.

In total mode, the views entered are the total views for the video or period being estimated, and the result is the estimated earnings for those views. In month mode, the views entered are views per month, and the result is labelled per month: at the defaults, 1,000,000 views a month at an RPM of $3.00 gives $3,000.00 per month, with the sub-line reading “1,000,000 views a month at an RPM of $3.00”. The arithmetic is identical in both modes, views divided by 1,000 times RPM, and only the interpretation changes. That identity is worth stating because it prevents a double-counting error: month mode does not multiply by twelve, and it does not annualise anything. A monthly figure of $3,000.00 per month becomes an annual figure only if the same monthly views and RPM held for twelve months, which would give $36,000.00 by multiplication, but that annual figure is the reader’s extrapolation, not the page’s output, and it inherits every uncertainty in the monthly inputs twelve times over.

The mode choice also affects which RPM to enter. The page’s own FAQ advises using a recent full month’s RPM from YouTube Studio for a steadier figure, and that advice fits month mode naturally, because a monthly RPM pairs with monthly views. For total mode, the RPM should match the period the views cover: a lifetime RPM for lifetime views, or a recent RPM if the question is what the same views would earn at today’s rates. Mixing them, lifetime views with a single month’s RPM, or a month’s views with a lifetime RPM, produces a figure that is arithmetically correct and interpretively confused, because the two inputs describe different periods. The page cannot know which periods the inputs describe; it can only multiply them. Keeping the views period and the RPM period matched is the user’s job, and the mode label, total or per month, is the reminder to do it.

CPM is not RPM, and the difference is YouTube’s share

The page uses RPM for a reason, and using CPM instead would overstate the creator’s earnings.

CPM is the cost an advertiser pays per 1,000 ad impressions, before YouTube’s share, while RPM is the revenue the creator actually receives per 1,000 views, after the share, and it is the figure YouTube Studio shows, as the page’s own FAQ explains. Earnings estimates should therefore use RPM, and this page does. Entering a CPM figure in the RPM field would inflate the result by whatever YouTube’s share amounts to for that channel and period, because the CPM counts money the creator never receives. The page cannot detect the substitution, because both figures are dollars per thousand and both look plausible as inputs, so the check is on the source: if the figure came from an advertiser-facing report, it is likely a CPM, and if it came from YouTube Studio’s Revenue tab, as the page’s own FAQ directs, it is an RPM. The FAQ also notes that RPM in YouTube Studio is an all-in figure, total revenue including ads and other revenue sources YouTube reports there, divided by all views and multiplied by 1,000, which is why it is lower than an ads-only rate but closer to what is actually received. That all-in character is another reason not to substitute an ads-only rate: the page’s formula multiplies all views by one rate, so the rate must already reflect all revenue, or the result will understate total revenue by the non-ads share.

RPM also moves, and the page’s own FAQ gives the reasons: advertiser demand changes, it often rises in the last months of the year and falls in January, and it shifts as audience, topics and video lengths change. A single viral video in a low-value topic can pull a channel’s average RPM down even while views go up, which means a channel’s earnings can fall while its views rise, if the new views carry a lower RPM than the old ones. That possibility breaks the naive intuition that more views always mean proportionally more money, because the proportionality holds only at a fixed RPM, and the RPM is not fixed across videos, audiences or seasons. Any estimate that holds RPM constant across a changing audience is therefore a scenario, not a forecast: it says what the views would earn at that RPM, and the RPM is the assumption to stress-test, by running the same views at a lower and a higher RPM and reading the range, rather than quoting a single figure as the answer.

What this page does not promise

Every figure on this page is an illustration at an RPM you chose. None of them is a promise, a guarantee, or a prediction about any channel.

The page’s own FAQ states the boundary directly: the estimate is not a guarantee of what you will earn, because it is built from the views and RPM you enter, and real RPM moves with topic, audience, advertiser demand and the time of year, so an actual payout will differ. These sections adopt that boundary for every figure they quote. The $3,000.00 for 1,000,000 views at $3.00 RPM is an illustration of the formula at those inputs, not a claim that any particular video or channel earns that amount, and the $10,000.00 at $10.00 RPM is the same formula at a different assumed RPM, not a claim that $10.00 is achievable for any particular content. No CPM rates, RPM benchmarks, or earnings claims for any topic, audience or channel size are stated anywhere on this page or in these sections, because the page contains no such data and inventing them would turn a mechanics calculator into a misleading earnings promise. The only RPM figures used here are the page’s own defaults, its own visual rows, and the doubled-RPM illustration, all labelled as inputs, not as market data.

The same boundary applies to the views input. The page multiplies whatever views figure is entered, without checking whether those views are achievable, whether they are monetised views, or whether the channel meets any eligibility requirement, because the page models arithmetic, not platform policy. A views figure that is aspirational, a round million entered as a goal rather than a measurement, produces an aspirational earnings figure, and quoting it without the “if” attached, if the video reached a million views at this RPM, misrepresents a scenario as a result. The honest form of every figure on this page carries its conditions: this many views, at this RPM, in this mode, gives this amount. Drop any of the conditions and the figure becomes a different claim from the one the page computed.

Four mistakes with earnings estimates

Each mistake below inflates the estimate in a way that looks like better performance, which is why each survives unnoticed.

1. Entering CPM as RPM. As the previous section explains, CPM counts advertiser spend before YouTube’s share, while RPM counts creator revenue after it. Substituting CPM inflates the result by the share that never reaches the creator, and the inflation is invisible in the output, because the output is just a larger dollar figure that looks like success.

2. Mixing periods. Lifetime views with a single month’s RPM, or a month’s views with a lifetime RPM, produce a figure whose inputs describe different periods. The page multiplies them anyway, because it cannot see the mismatch. Matching the views period to the RPM period, and the mode to both, is the check.

3. Annualising a monthly figure without saying so. Month mode gives a per-month figure. Multiplying it by twelve gives an annual scenario only if the same monthly views and RPM held all year, which the page’s own FAQ says they typically do not, because RPM moves seasonally. An annual figure quoted without that condition is a scenario presented as a forecast.

4. Treating an illustration as a promise. A figure computed at an assumed RPM, for assumed views, is a scenario. Quoting it as expected income, guaranteed income, or typical income for a topic or channel size adds claims the page never made and the inputs cannot support. The page’s figures are mechanics: they show what given inputs imply, and the inputs, not the page, carry every assumption.

A routine for an earnings estimate

The routine is short, and it ends with a range, not a single number.

First, choose the mode that matches the question: total for a video or period already completed, month for a recurring monthly figure. Second, enter the views for that period, and enter the RPM from YouTube Studio’s Revenue tab for the same period, using a recent full month for a steadier figure, as the page’s own FAQ advises, and checking that the figure is RPM, not CPM. Third, read the earnings and the per-view figure, and run the same views at a lower RPM and a higher RPM, to see the range the uncertainty in RPM implies, rather than quoting the single central figure as the answer. Fourth, label the result with its conditions: this many views, at this RPM, in this mode, gives this amount, and note that the actual payout will differ as RPM moves with topic, audience, demand and season. Finally, do not use the result as a promise to anyone, including yourself: it is an estimate built from entered inputs, and the page’s own FAQ states that it is not a guarantee of what you will earn.

Reading the visual rows as a sensitivity table

The page’s visual rows are not decoration. They are a ready-made sensitivity analysis at one million views.

The page displays, for 1,000,000 views, the earnings at RPM $1.00, $2.00, $3.00, $5.00 and $10.00 as $1,000.00, $2,000.00, $3,000.00, $5,000.00 and $10,000.00, and this section’s table adds the probed per-view figures for each: $0.0010, $0.0020, $0.0030, $0.0050 and $0.0100. Read as a ladder, the rows show what a change in RPM is worth at this view count: moving from $3.00 to $5.00 is worth $2,000.00 per million views, moving from $5.00 to $10.00 is worth $5,000.00, and moving from $1.00 to $2.00 is worth $1,000.00. The ladder also shows why RPM improvements matter more at scale: the same one-dollar RPM improvement, from $2.00 to $3.00, is worth $1,000.00 per million views, $10,000.00 per ten million views, and $100.00 per hundred thousand views, because the value of an RPM point is the view count divided by 1,000. A channel deciding where to invest effort, in more views or in a higher RPM, can read both levers from this ladder: views multiply the whole ladder, while RPM moves along it, and the two levers compound, because more views at a higher RPM earn the product of both improvements.

The ladder has a second use, as a reality check on any single figure. An earnings claim for a million views that falls far outside the ladder’s range, below $1,000.00 or above $10,000.00, implies an RPM outside $1.00 to $10.00, which may be genuine for an unusual topic or audience, but which should be stated explicitly, because the ladder’s range covers the page’s own displayed examples. A claim inside the range can be checked by finding its rung: $6,000.00 per million views implies an RPM of $6.00, as probed, and $2,000.00 per million views implies $2.00. The ladder therefore turns any earnings figure back into the RPM that produced it, which is the assumption that most needs scrutiny, because the views figure is usually known and the RPM figure is usually estimated.

A channel month, worked two ways

The same inputs in the two modes give the same amount with different labels, and the labels are the whole difference.

Take 500,000 views at an RPM of $4.00. In total mode the page displays $2,000.00, with the sub-line “500,000 views at an RPM of $4.00”. In month mode the same inputs display $2,000.00 per month, with the views understood as monthly views. The amount is identical because the arithmetic is identical, and the difference is purely interpretive: the total-mode figure is the earnings for those 500,000 views whenever they occurred, while the month-mode figure is the earnings for a month in which 500,000 views occurred at that RPM. A reader who copies the total-mode figure into a monthly budget, or the month-mode figure into a lifetime total, has made an interpretation error, not an arithmetic one, and the page’s mode label is the only guard against it. Stating the mode alongside the figure, $2,000.00 total or $2,000.00 per month, is therefore not pedantry but the difference between a correct and an incorrect claim, even though the digits are the same.

The month example also shows how to build a monthly estimate from mixed content. A month’s views rarely come from a single video at a single RPM, so a monthly estimate built from one RPM is an average-RPM estimate: total monthly views times the month’s average RPM, divided by 1,000. The page’s own FAQ advises using a recent full month’s RPM for a steadier figure, and that advice fits this use, because a full month’s RPM already averages across the month’s videos, topics and audiences. A monthly estimate built from a single video’s RPM instead, applied to the whole month’s views, would misstate the month whenever that video’s RPM differs from the month’s average, which, given the FAQ’s note about viral videos in low-value topics pulling the average down, is a common case rather than an edge case.

Seasonality as scenarios, not as data

RPM moves with the seasons, and the honest way to show that movement on this page is as scenarios at stated RPMs.

The page’s own FAQ notes that RPM often rises in the last months of the year and falls in January, as advertiser demand changes. These sections do not turn that qualitative pattern into seasonal RPM figures, because the page contains no seasonal data and inventing monthly RPM values would be inventing the very market data this page deliberately does not provide. What can be shown, using only the page’s own probed figures, is the size of the effect if RPM moves between two of the page’s own rows: one million views at $2.00 RPM give $2,000.00, and the same views at $5.00 RPM give $5,000.00, a difference of $3,000.00 per million views for a $3.00 RPM swing. Whether any particular channel’s RPM swings by that much, or by more, or by less, depends on its topic, audience and season, and the page’s figures cannot answer that. The scenario form is the honest form: if RPM were $2.00, the million views would give $2,000.00, and if it were $5.00, they would give $5,000.00, and the range between them is the uncertainty that any single-figure estimate hides.

When views and RPM move together

Views and RPM rarely move independently, and the page’s formula shows why their joint movement matters more than either alone.

Because earnings are views divided by 1,000 times RPM, a rise in views combined with a fall in RPM can leave earnings unchanged, or even lower them, even though the view count improved. The page’s own FAQ gives the mechanism: a single viral video in a low-value topic can pull a channel’s average RPM down even while views go up. In numbers from this page’s own rows, a million views at $5.00 RPM give $5,000.00, while two million views at $2.00 RPM give $4,000.00, which is less money from twice the views, because the RPM fell by more than the views rose. The product, not either factor alone, is what matters, and a channel report that celebrates a view milestone without stating the RPM that accompanied it has reported half the product. The page’s formula makes the joint check trivial: enter the new views and the new RPM together, and read the product, rather than extrapolating from either factor’s movement alone.

The joint view also clarifies what “growth” means for a channel. Growth in views at a constant RPM is genuine earnings growth, proportionally. Growth in views at a falling RPM is ambiguous, and may be growth, stagnation, or decline in earnings, depending on the relative sizes of the two movements. Growth in RPM at constant views is genuine earnings growth too, and it is often the cheaper growth to pursue, because it requires no additional audience, only a shift toward topics, formats or audiences that advertisers value more highly. The page does not advise on any of those strategies, and these sections do not either, but the formula’s structure, a product of two factors, is the reason any strategy discussion must consider both factors together, and why any earnings figure quoted without both its views and its RPM is incomplete.

New guide: YouTube Earnings Explained: RPM, CPM, Shorts, and How Creators Get Paid

Two YouTube channels with a million views each can earn amounts that differ by a factor of ten, and both figures can be honestly reported.

YouTube pays creators 55% of the advertising revenue on their videos, keeping 45%. The creator’s share is what RPM measures, after YouTube’s cut — so RPM, not CPM, is the number that predicts a creator’s ad income. The full guide, YouTube Earnings Explained: RPM, CPM, Shorts, and How Creators Get Paid, works through the method in detail, with worked examples and the cases that most often go wrong.

Frequently asked questions

More calculators