YouTube Revenue Calculator

Start with the revenue metric, not a payment-per-view claim

YouTube’s explanation of RPM and CPM distinguishes creator revenue per thousand relevant views from advertiser spending per thousand ad impressions. RPM is after platform revenue sharing; CPM is not the same denominator or income basis. A view without an ad can still be in an RPM denominator, while one playback can generate several ad impressions. Do not multiply an advertiser CPM by all public views or deduct a platform share again from an already net RPM.

This calculator offers an ad-only assumption and Total Analytics RPM. The latter can include more than ads, such as Premium and memberships, depending on the report. It therefore requires your own custom range and disables the separate membership addition. Select a definition you can explain: total platform revenue divided by matching views is a different quantity from an ad-only estimate.

The calculation is matching monthly views / 1000 * RPM. “Typical” means the central input scenario, not the statistically expected payment. Low and high are alternative assumptions, not confidence bounds. A neat range can still be misleading when its view count covers the wrong period or its RPM comes from a different format. Check those definitions before adjusting decimal precision.

Convert the view period without inventing a monthly ledger

Per Month uses the entered count directly. Per Day multiplies it by 30.4375, an average-month convention rather than the number of days in a named calendar month. Per Video multiplies it by uploads per month. A daily estimate of 10,000 therefore becomes 304,375 monthly views; 25,000 per video across four uploads becomes 100,000. Use the monthly mode with the actual dated total when reconciling a real report.

The per-video assumption needs a horizon. Lifetime views of old uploads are not the same as views arriving in the month of publication. A new upload may earn views for months, while older videos continue adding views now. Use comparable first-month performance for a new-upload plan, or your channel’s actual total monthly views for a channel-wide scenario. Do not add a back-catalogue total twice.

The daily display divides typical monthly platform revenue by the same average-month factor. The yearly projection multiplies it by 12. Neither models seasonal advertising, viral events, later claims or payout timing. Read these outputs as a constant-assumption conversion, then compare separate months if your own history changes materially through the year.

Match Shorts views and blend by comparable view share

YouTube’s Shorts counting guidance records the change on 31 March 2025: public Shorts views count starts and replays without a minimum watch-time requirement, while the previous measure remains as engaged views in Analytics. Shorts RPM uses engaged views. The view-denominator selector here labels your assumption; it does not convert a public count to engaged views. Multiplying public Shorts starts by an engaged-view RPM can overstate the comparable volume.

The Shorts monetization policy describes a pooled feed-ad model, unlike treating an ad impression beside every long-form playback as a payment unit. This tool does not reconstruct that pool, music allocation or eligibility. The illustrative Shorts RPM range is just a planning input. An owner’s matched Shorts report is the more useful basis for a specific channel scenario.

Mixed blends the built-in long-form and Shorts ranges by the percentage of views, not uploads. At General and Global Mix, a 75% Shorts share gives a typical illustrative RPM of 0.25 * 4 + 0.75 * 0.06 = 1.045 USD. At 100,000 comparable views the arithmetic is 104.50 USD. That example is valid only under a deliberately consistent denominator; it is not permission to merge incompatible public and engaged counts.

For a channel with separate long-form public views and Shorts engaged views, calculate each format separately and add the resulting revenue scenarios outside the tool. A single total Analytics RPM can be used only with its own matching denominator. When a custom range is active, it replaces the built-in blend, so changing Shorts Share no longer adjusts the RPM.

Use niche, geography and custom ranges as different kinds of evidence

The built-in long-form range is 1.5, 4 and 8 USD; Shorts uses 0.02, 0.06 and 0.15 USD before factors. These are illustrative defaults, not official rates, measured live averages or forecasts for every monetized channel. General, finance/business, technology/software, education/tutorials, fitness/wellness, travel, gaming, entertainment and music apply broad topic factors; audience regions apply another factor.

For example, the technology factor 1.35 and US/Canada factor 1.3 turn the built-in long-form typical 4 into 7.02 USD. At 100,000 monthly views that gives 702 USD. This only shows the model’s multiplication; it does not establish that technology content or a creator living in Canada earns that rate. Region concerns the assumed audience, not the creator’s residence. Seasonal demand and audience mix can change even within the same category.

A custom range bypasses those factors and the format blend. Use comparable owner reports to choose low, typical and high values, keeping currency, format, denominator and income basis consistent. If a few days were unusually strong, do not silently treat them as a full-year midpoint. To combine historical periods, a view-weighted RPM means total revenue divided by total matching views times 1,000; a simple mean of monthly RPMs can overweight a quiet month.

Enter an ordered range: low no greater than typical, typical no greater than high. Values are not automatically sorted because that would conceal an input mistake. Zero is a valid hypothetical RPM for a non-earning scenario. A positive target at zero typical RPM has no finite view requirement; a missing target result is more honest than an invented infinity-shaped payment estimate.

Check which views could earn under the chosen assumptions. A video that remains public may receive limited or no advertising under YouTube’s advertiser-friendly guidance. Its views therefore cannot simply inherit the RPM of a different set of fully monetized videos. Review the relevant video’s monetization status and a matching owner report before choosing a range; do not invent a universal percentage deduction. Channel monetization policies also affect eligibility and can change over time. Record the report period and review current notices when reusing an older scenario. The calculator’s format and niche options do not decide whether your channel or a particular upload is eligible.

An estimate can change after the viewing period. YouTube’s earnings overview identifies invalid traffic and Content ID claims or disputes as reasons estimated revenue may be adjusted. The copyright-claims guidance also distinguishes blocking, tracking and monetizing a claimed video, sometimes with revenue sharing: a claim does not have one universal financial outcome. Check the owner’s restrictions and revenue reports rather than assuming every public view generated income or every claim made it zero. Keep the date of the report used for RPM, and revisit the scenario when those reports change. The low/high cases do not model these adjustments or resolve a claim, and a calculated monthly amount is not finalized earnings or a bank payment.

Separate platform revenue, additions and the target

Sponsorships, Memberships and Affiliate Income are entered as monthly USD amounts. With an ad-only basis, these separate amounts are added to typical platform revenue for the combined monthly scenario. Total Analytics RPM may already include membership revenue, so the calculator ignores only the amount entered separately in Memberships. It does not remove membership revenue from the RPM you supply. Check the other additions too: if income from an agreement already belongs to the report used to calculate RPM, do not add it again merely because a field is available.

At 100,000 views and a custom 4-USD typical RPM, platform revenue is 400 USD. Add 200 sponsorship, 50 memberships and 25 affiliate income under the ad-only basis: the combined scenario is 675 USD. Under the total Analytics basis, the same entered membership amount is ignored and the total becomes 625 USD. This is a comparison of definitions, not evidence that either hypothetical amount has been earned.

The target remains platform-only. A 1,000-USD target at 4 RPM needs 250,000 views even if additions make the combined total look closer to the goal. The range, daily and yearly platform outputs do not turn the optional additions into recurring guarantees. Totals also omit business expenses and taxes; revenue is not profit or spendable cash.

Keep currency assumptions visible when exporting or sharing

The output currencies are USD, INR, EUR, GBP, CAD and AUD. RPM and optional income inputs remain USD; the display conversion uses the editable “1 USD equals” factor. Those defaults are illustrative, not live exchange rates. For a deliberate EUR factor of 0.9, a 400-USD platform scenario displays 360 EUR. A 900-EUR target is first converted to 1,000 USD and then requires 250,000 views at 4 RPM.

Changing currency can restore that currency’s default factor, so check the factor again after switching. Record the date and origin of your chosen conversion in the accompanying planning notes; this tool does not model bank charges, settlement rates or exchange gains. More displayed decimals cannot make a rough revenue input precise.

Copy and CSV preserve key scenario values and bases. Share puts the view count, custom range, conversion and optional income into a link. Review it before sending: it can disclose business assumptions even though it does not grant access to Analytics. Keep a dated report with the reasoning behind the inputs, because a link reproduces assumptions rather than explaining why they were chosen.

Interpret a public channel sample without turning it into earnings

Optional lookup accepts a public channel identifier or supported handle/URL and requires the public-data service to be available. It can return channel counts and recent video statistics, including average, median, number checked and estimated upload frequency. It cannot retrieve private RPM, revenue, contracts or audience-country distribution. Authorized channel revenue reports require the owner’s authorization, as the YouTube Analytics channel-report documentation explains.

Suppose five sampled videos have 10,000, 10,000, 10,000, 10,000 and 200,000 lifetime views. The average is 48,000; the median is 10,000. A four-upload plan based on the average implies 192,000 views, but an outlier drives that number. Different video ages, formats and ongoing back-catalogue viewing weaken the monthly interpretation further. Median is useful context, not proof of a predictable future upload.

Use Average Per Video and Use Estimated Monthly Views apply sample-derived assumptions, not a measured monthly ledger. Check the view basis afterward, especially for Shorts. If no recent videos are returned or lookup is unavailable, enter your own volume instead. Cancel or edit the identifier to abandon a stale request; repeated public requests cannot uncover private income. A useful error report gives the public identifier and time, never account passwords.