Navigation

Tools

Monetization CheckerReview public monetization signalsRevenue EstimatorExplore an RPM scenarioKeywords ExtractorSample public topic phrases & tagsCompare VideosCompare public metrics side-by-sideVideo Data InspectorInspect public tags & metadataCategory CheckerInspect video category & topic estimateUsername CheckerLook up a public handleTranscript GeneratorVideo URL: transcript, TXT/SRT/VTTBanner & Profile DownloaderChannel: download banner and profile picture
Language
Monetization

YouTube RPM by Category: How to Use YTKits Assumptions

6 min read · Published 2026-07-02

Last updated:

YouTube RPM by Category: How to Use YTKits Assumptions

A public YouTube view count cannot tell you what a creator earned. The YTKits revenue tool combines that count with chosen RPM assumptions to explore a scenario. Its category ranges are calculator inputs; they are not a measured survey of creator earnings.

An earlier version of this page mixed illustrative assumptions with language about research and category benchmarks. Those tables did not include a reproducible source-level dataset, so they have been removed. This guide now explains the calculation and how to interpret it.

Start with the question you need to answer

For your own channel, use the revenue and RPM reported in YouTube Studio. For another creator, public metadata can help describe the channel, but you need their verified analytics to establish actual earnings or audience composition.

A scenario is useful for a narrower question: what would this view count produce if a specified RPM applied? It is not evidence that this RPM actually applies.

A calculation you can reproduce

For a simple scenario:

Revenue = eligible view count / 1,000 x assumed RPM

Consider a hypothetical period with 100,000 views. The amounts below demonstrate sensitivity to the input; none is a benchmark for a category or country.

Assumed RPM Arithmetic Scenario revenue
$0.50 100,000 / 1,000 x $0.50 $50
$2.00 100,000 / 1,000 x $2.00 $200
$5.00 100,000 / 1,000 x $5.00 $500

The result changes tenfold between the first and last row even though the view count is identical. That is why the provenance of an RPM input matters more than displaying extra decimal places.

Public views may differ from the eligible or engaged views used in revenue calculations. The tool cannot observe another creator's private denominator. Keep this limitation alongside any exported estimate.

What category contributes

YouTube video categories describe broad kinds of content. A channel can upload videos in several categories. The category is useful context for organizing a scenario, but it does not set an ad price or reveal audience purchasing behavior.

YTKits also predicts topics from metadata. These topic labels are estimates and do not always map to official YouTube video categories. A mismatch is not proof of a recommendation problem, lost revenue or incorrect settings.

Use the category checker to inspect public labels. Change your own video's category only when a different label describes the video more accurately.

How to choose your inputs

  1. Choose a period. Keep the view count and RPM tied to the same period and format where possible. Do not combine a lifetime view count with a claimed monthly revenue interpretation.
  2. Identify the audience assumption. A channel's registered country is not its viewer geography. A default country in a calculator is a starting choice, not audience evidence.
  3. Choose an RPM source. Your own Studio data or analytics shared by the creator is stronger evidence than an unrelated creator's screenshot. Record the date, format and revenue sources included.
  4. Test a range. When the RPM is unknown, try several explicit assumptions. Actual earnings can fall outside that range; it is not a statistical confidence interval.
  5. Keep the caveats with the number. If you share the estimate, share its view period, RPM input and unknowns too.

RPM and CPM are different inputs

CPM describes advertiser cost per 1,000 ad impressions before revenue sharing. RPM describes creator revenue per 1,000 views after revenue sharing and can include multiple revenue sources. They do not have the same denominator, and multiplying CPM by a fixed revenue-share percentage does not generally recover Studio RPM.

See YouTube's explanation of revenue metrics and the YTKits RPM versus CPM guide.

Common interpretation mistakes

  • Treating a category range as an official rate paid by YouTube.
  • Using the channel registration country as proof of audience location.
  • Combining Shorts and long-form inputs without examining their different revenue systems.
  • Treating additional decimal places as greater accuracy.
  • Assuming that changing a category changes the underlying RPM.
  • Using a public estimate to value a sponsorship or business without verified data.

A useful record to keep

Before using a result, write down the video or channel, retrieval date, view period, format, RPM assumption, audience assumption and source of each input. Then state what you would need to verify before making a decision. That record makes the estimate understandable even when the underlying public counts change.

The revenue estimator is a convenient way to explore assumptions. The calculator methodology guide describes the tool's public inputs and limitations in more detail.

Sources and limits

The arithmetic examples are hypothetical. This article does not claim to publish market-average RPMs or a dataset of private channel earnings.

Related creator guides

Research · 11 minA 30-Minute YouTube Channel Audit Using Only Public DataResearch · 10 minWhat Public YouTube Data Can and Cannot Tell YouResearch · 10 minHow to Compare Two YouTube Videos Fairly

About the author

Jayesh Mehta (YouTube creator and YTKits founder) has published more than 1,000 videos during five years of operating a gaming channel. He develops YTKits and writes about the tool methods, public YouTube API data, and lessons from his own channel. Personal observations are labeled separately from official YouTube rules and calculated estimates.

· About YTKits