Skip to content

Update pricing.mdx #25123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 15, 2025
Merged

Update pricing.mdx #25123

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e1e8b2a
Update pricing.mdx
kathayl Sep 12, 2025
c6c27cc
Update src/content/docs/browser-rendering/platform/pricing.mdx
kathayl Sep 15, 2025
7774d1c
Update pricing.mdx
kathayl Sep 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/content/docs/browser-rendering/platform/pricing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,4 +54,9 @@ Then, you can use [the pricing page](/browser-rendering/platform/pricing/) to es
No. If a request to the Browser Rendering REST API fails with a `waitForTimeout` error, the browser session is not charged.

### How is the number of concurrent browsers calculated?
Cloudflare calculates concurrent browsers as the **monthly average of your daily peak usage**. In other words, we record **the peak number of concurrent browsers each day** and then average those values over the month. This approach reflects your typical traffic and ensures you are not disproportionately charged for brief spikes in browser concurrency.
Cloudflare calculates concurrent browsers as the **monthly average of your daily peak usage**. In other words, we record **the peak number of concurrent browsers each day** and then average those values over the month. This approach reflects your typical traffic and ensures you are not disproportionately charged for brief spikes in browser concurrency.

### How is billing time calculated?
Cloudflare calculates usage on a daily basis. At the end of each day, we total all your **browser usage in seconds**. At the end of the billing cycle, we add up all the daily totals and convert them to browser hours. Billing is based on the total browser hours used during the month, with rounding only applied once at the end of the month (to the nearest hour).
Copy link
Contributor

@ToriLindsay ToriLindsay Sep 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Cloudflare calculates usage on a daily basis. At the end of each day, we total all your **browser usage in seconds**. At the end of the billing cycle, we add up all the daily totals and convert them to browser hours. Billing is based on the total browser hours used during the month, with rounding only applied once at the end of the month (to the nearest hour).
At the end of each day, Cloudflare totals all of your browser usage for that day. At the end of each billing cycle, we add up all of the daily totals to find the monthly total of browser hours, rounded to the nearest hour.

Just trying to simplify it a bit.


For example, if you only use 1 minute of browser time in a day, that day counts as 1 minute. If you do that every day for a 30-day month, your total would be 30 minutes. For billing, we round that up to 1 browser hour.