Skip to content

Commit e1e8b2a

Browse files
authored
Update pricing.mdx
new faq
1 parent d3be1e4 commit e1e8b2a

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

src/content/docs/browser-rendering/platform/pricing.mdx

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,4 +54,9 @@ Then, you can use [the pricing page](/browser-rendering/platform/pricing/) to es
5454
No. If a request to the Browser Rendering REST API fails with a `waitForTimeout` error, the browser session is not charged.
5555

5656
### How is the number of concurrent browsers calculated?
57-
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.
57+
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.
58+
59+
### How is billing time calculated?
60+
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).
61+
62+
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.

0 commit comments

Comments
 (0)