ytcpm.online

Free · No login · Browser-only calculation

YouTube RPM Calculator

Calculate creator revenue per 1,000 views from your own report. Use the same date range and video format for both inputs; this is not a public channel earnings lookup.

Quick answer: RPM = creator revenue ÷ the corresponding view count × 1,000. A measured RPM already reflects the revenue share used by the report.

Calculate your RPM

Example inputs are prefilled. Replace them with matching figures from your own report. Results update instantly; inputs stay in your browser.

Creator revenue per 1,000 corresponding views

$2.75

Revenue and views must cover the same period, currency and format. Use total long-form video views or the matching engaged-view basis for Shorts. Do not deduct the platform share again.

RPM formula and worked example

With $55 creator revenue and 20,000 matching views, RPM is $55 ÷ 20,000 × 1,000 = $2.75. At an unchanged $2.75 RPM, a forecast of 100,000 comparable views would imply $275. Future RPM may change.

These are hypothetical examples, not measured averages, payout promises or official country rates. Values are displayed in USD; convert both amounts consistently before comparing different currencies.

Choose the right denominator

For long-form RPM, use all matching video views, including non-monetized views. YouTube describes Shorts RPM using engaged views. Separate formats and revenue sources; Studio RPM may include Premium, memberships and other eligible YouTube revenue that an ad-only forecast excludes.

Find and monitor your actual rate

Check your own YouTube Studio Analytics with a consistent date range, metric name, currency and audience filter. Our public tools do not authenticate to your channel. The website Usage Monitor is API usage analytics, not a connected YouTube revenue dashboard.

How to check and monitor CPM in YouTube Studio

Sources and scope

Content updated . Official documentation supports metric definitions and access rules, not our country or niche benchmark values.

Editorial policy and benchmark limitations