Estimate monthly and annual website ad revenue from pageviews, page RPM or CPM, fill rate, and ad units per page, then compare daily revenue.
Last updated
Website ad revenue calculator Use this website ad revenue calculator to estimate monthly and annual display-ad income from pageviews, page RPM or CPM, fill rate, and ad density. It works as a page RPM calculator, a website RPM calculator, and a CPM-based ad revenue calculator for planning scenarios.
Quick examples
Pick a scenario or enter your own publishing assumptions.
Estimate basis
RPM mode is useful when you already know the revenue earned per 1,000 pageviews. CPM mode is closer to a website advertising revenue calculator that starts with ad impressions, ad density, and fill rate before deriving an effective page RPM.
Formula reference
RPM mode: Revenue = pageviews × RPM ÷ 1,000
CPM mode: Revenue = ad impressions × CPM ÷ 1,000
Ad impressions: pageviews × ad units × fill rate
Revenue estimate
$6,000.00
Estimated monthly website ad revenue from 500,000 pageviews, 3 ad units per page, and a 70% fill rate.
Annual revenue
$72,000.00
Daily revenue
$197.26
Monthly ad impressions
1,050,000
Effective page RPM
$12.00
Effective impression RPM
$5.71
Revenue per 100,000 pageviews
$1,200.00
Why RPM and CPM can disagree CPM prices ad impressions, while page RPM measures the publisher-side revenue earned per 1,000 pageviews. When fill rate or ad density changes, the same CPM can still produce a very different effective page RPM.
Traffic target reading
This estimate is strongest when you treat it as a planning worksheet. Use the target field to back into the pageview level your current RPM or CPM assumptions would need, then compare that with the projection table below instead of relying on one monthly guess.
Traffic projection table
Use these standard traffic milestones to see how the same monetization assumptions scale. This is usually more useful than a single estimate because real publishers plan around ranges like 100k, 250k, 500k, and 1M pageviews.
Monthly pageviews
Monthly revenue
Annual revenue
Ad impressions
Reading
50,000
$600.00
$7,200.00
105,000
Useful benchmark for testing whether monetization is scaling with traffic.
100,000
$1,200.00
$14,400.00
210,000
Useful benchmark for testing whether monetization is scaling with traffic.
250,000
$3,000.00
$36,000.00
525,000
Meaningful side-income range for many ad-supported sites.
500,000
$6,000.00
$72,000.00
1,050,000
Meaningful side-income range for many ad-supported sites.
1,000,000
$12,000.00
$144,000.00
2,100,000
Material publishing income if demand, policy health, and traffic quality hold.
Website ad revenue calculator guide: estimate page RPM, CPM revenue
A website ad revenue calculator helps publishers turn pageviews, page RPM, CPM, fill rate, and ad density into a more realistic advertising-revenue estimate. This page works as a website RPM calculator and a CPM-based ad revenue calculator, so you can compare publisher yield on a pageview basis and on an impression basis without switching tools.
What a website ad revenue calculator is estimating
Website advertising revenue is usually driven by traffic, yield, and ad supply. Traffic determines how many pages can show ads. Yield determines how much each thousand pageviews or ad impressions is worth. Ad supply depends on how many ad units exist on a page and how often they fill with paying demand.
That is why this page supports both RPM mode and CPM mode. RPM mode is best when you already know the publisher-side revenue earned per 1,000 pageviews. CPM mode is better when you want to start with ad impressions and market pricing, then translate that into a publisher revenue estimate.
RPM vs CPM for website revenue planning
RPM and CPM are related but not interchangeable. Page RPM is a publisher metric that expresses revenue earned per 1,000 pageviews. CPM is an advertiser pricing metric tied to 1,000 ad impressions. If fill rate is weak or ad density is low, CPM can look healthy while page RPM still stays modest.
For that reason, a website RPM calculator often gives the cleaner business planning view. A CPM-based estimate still matters, though, because it helps you understand how inventory pricing, fill rate, and ad units per page combine to shape effective page RPM.
Revenue (RPM mode) = Pageviews × Page RPM ÷ 1,000
Calculates publisher revenue directly from pageview yield.
Ad impressions = Pageviews × Ad units per page × Fill rate
Estimates how many impressions actually become monetizable ad opportunities.
Revenue (CPM mode) = Ad impressions × CPM ÷ 1,000
Converts advertiser-side pricing into a monthly revenue estimate.
Worked example: 500,000 pageviews at a $12 page RPM
If a site earns a page RPM of $12 and gets 500,000 pageviews in a month, the monthly revenue estimate is $6,000 because 500,000 divided by 1,000 equals 500, and 500 multiplied by 12 equals 6,000.
Now compare that with a CPM-based setup. If the same site runs 3 ad units per page with a 70% fill rate and an advertiser CPM of $4, the estimated ad impressions are 1,050,000 and the monthly revenue estimate is $4,200. That works out to an effective page RPM of $8.40, which is lower than the direct $12 RPM assumption.
Why real website ad revenue can differ from the estimate
Real-world ad revenue depends on audience geography, advertiser demand, content niche, viewability, policy compliance, ad blocker usage, device mix, seasonality, and demand-partner quality. The same pageview count can produce very different page RPM across different sites or even across different sections of the same site.
This page also does not model business costs. Hosting, writers, design, SEO, sales, commissions, and taxes all sit outside the advertising estimate. The calculator is useful for monetization planning, but it is not a full profit model.
How many pageviews you need to hit a revenue target
One of the most common publisher questions is not what a site earns today, but how many pageviews it would need to reach a target such as 1,000, 5,000, or 10,000 per month. That is why the calculator now includes target-revenue math. It takes the effective page RPM implied by your current setup and translates it into the traffic requirement needed to hit the target monthly revenue.
This is useful because monetization planning usually happens in reverse. A solo publisher might ask whether the current RPM and traffic mix can realistically support freelance costs. A media operator might ask whether a content section needs 250,000 or 750,000 pageviews to justify added editorial investment. Goal math turns a revenue estimate into a planning threshold.
Why traffic milestone tables matter
A single monthly revenue estimate can be too abstract to guide decisions. Publishers often plan around milestone ranges such as 50,000, 100,000, 250,000, 500,000, and 1,000,000 pageviews. Seeing those levels side by side makes it easier to judge whether a site is still in early testing mode, in meaningful side-income territory, or closer to a material publishing business.
That is also why revenue per 100,000 pageviews is a useful reference output. It gives you a compact benchmark for comparing sections, geographies, seasons, or ad-stack changes without needing identical traffic totals each time.
When to use RPM mode and when to use CPM mode
Use RPM mode when you already have publisher-side reporting or benchmarks expressed as revenue per 1,000 pageviews. Use CPM mode when you want to translate ad-impression pricing into publisher revenue with explicit assumptions about fill rate and ad density.
If you are comparing traffic plans or setting revenue targets, page RPM is usually the metric that ties most directly to publishing decisions. If you are negotiating inventory or modeling programmatic demand, CPM mode can explain how impression pricing turns into page-level economics.
Further reading
Google AdSense Calculator — Use the Google AdSense Calculator when you want a click-through-rate and CPC-based publishing model.
Creator Revenue Calculator — Use the Creator Revenue Calculator when the monetization model extends beyond on-site display advertising.
Frequently asked questions
How do you calculate website ad revenue?
In RPM mode, multiply pageviews by page RPM and divide by 1,000. In CPM mode, estimate ad impressions from pageviews, ad units, and fill rate, then multiply by CPM and divide by 1,000.
What is the difference between RPM and CPM?
RPM is a publisher metric based on revenue per 1,000 pageviews. CPM is an advertiser pricing metric based on cost per 1,000 ad impressions. CPM often needs fill-rate and ad-density assumptions before it becomes a page-level revenue estimate.
Why can the same CPM produce different website revenue?
Because pageviews do not translate into the same number of monetized impressions on every site. Fill rate, ad units per page, viewability, geography, and niche all affect how much revenue a CPM assumption actually produces.
What is page RPM?
Page RPM means revenue per 1,000 pageviews. It is often the clearest monetization metric for publishers because it combines traffic and revenue yield into one comparable number.
Does this website ad revenue calculator predict exact earnings?
No. It is a planning estimate based on the assumptions you enter. Real ad revenue changes with traffic quality, ad demand, seasonality, policy health, and inventory performance.
Why does fill rate matter?
Fill rate estimates what share of possible ad slots actually fill with paid demand. If fill rate falls, the same traffic and CPM assumptions produce fewer monetized impressions and lower revenue.
Why do ad units per page matter?
Ad units per page affect how many impressions a pageview can generate. More units can raise potential revenue, but only if those units fill and remain useful to visitors.
Should I budget from RPM or CPM?
Budgeting usually works better from RPM when you already know publisher-side performance. CPM is more useful when you are starting from inventory pricing and want to see how it translates into page-level yield.
How many pageviews do I need to make 1,000 a month from ads?
It depends on the effective page RPM. At a page RPM of 8, you would need about 125,000 monthly pageviews to make 1,000 from display ads. At a page RPM of 20, you would need about 50,000 pageviews. That is why target pageview math is more useful than one generic traffic claim.
Why is revenue per 100,000 pageviews useful?
It gives you a quick benchmark for comparing monetization efficiency across different traffic levels. If one content section earns 800 per 100,000 pageviews and another earns 1,600, you can see the yield gap immediately even if the traffic totals are different.
Does this include sponsorships or affiliate revenue?
No. This page estimates display-ad style revenue only. Sponsorships, affiliate income, subscriptions, and other monetization channels are outside the model.
Can a small site use this page?
Yes. The math works at any traffic level, but smaller sites usually see more volatility because a few traffic or demand changes can move RPM more sharply.
