Skip to content

[Browser Rendering] pricing update #23727

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 6 commits into from
Jul 16, 2025
Merged

[Browser Rendering] pricing update #23727

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
46c0352
[Browser Rendering] pricing update
ToriLindsay Jul 16, 2025
fc751e6
Update src/content/docs/browser-rendering/platform/pricing.mdx
ToriLindsay Jul 16, 2025
812a843
Update src/content/docs/browser-rendering/platform/pricing.mdx
ToriLindsay Jul 16, 2025
742bc73
Update src/content/docs/browser-rendering/platform/pricing.mdx
ToriLindsay Jul 16, 2025
d5e6ff0
Fix ambiguity in table
ToriLindsay Jul 16, 2025
bd1b11a
Changelog addition
ToriLindsay Jul 16, 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
34 changes: 33 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 @@ -5,4 +5,36 @@ sidebar:
order: 31
---

Browser Rendering service is currently available at no cost up to the [limits](/browser-rendering/platform/limits/) specified until billing begins. Pricing to be announced and we will provide advance notice before any billing begins.
Browser Rendering is currently available at no cost up to the [limits](/browser-rendering/platform/limits/) specified, with billing beginning on August 20, 2025 at the following rates:

| Plan | Included duration | Included concurrency | Price (beyond included) |
|----------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|----------|
| **Workers Free** | 10 minutes per day | 3 concurrent browsers | N/A |
| **Workers Paid** | 10 hours per month | 10 concurrent browsers (averaged monthly) | **1. REST API**: $0.09 per additional browser hour <br />**2. Workers Bindings**: $0.09 per additional browser hour <br /> $2.00 per additional concurrent browser |

You can monitor your Browser Rendering usage in the [Cloudflare dashboard](https://dash.cloudflare.com). Go to **Compute (Workers)** > **Browser Rendering**.

### Examples of Workers Paid pricing
<br/>
Copy link
Collaborator

@kodster28 kodster28 Jul 16, 2025

Choose a reason for hiding this comment

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

These <br/> aren't needed, we have spacing built directly into our headers and other places.

Copy link
Contributor Author

@ToriLindsay ToriLindsay Jul 16, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

Without the br, I thought it looked too awkwardly close. And with double space, I thought it looked too far. But it can be removed if needed.

#### Example: REST API pricing
If a Workers Paid user uses the REST API for 50 hours during the month, the estimated cost for the month is as follows.

For **browser duration**:
<br/>50 hours - 10 hours (included in plan) = 40 hours
Copy link
Collaborator

@kodster28 kodster28 Jul 16, 2025

Choose a reason for hiding this comment

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

? should just be an unordered list?

Copy link
Contributor Author

@ToriLindsay ToriLindsay Jul 16, 2025

Choose a reason for hiding this comment

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

I think unordered list gives the impression that it's a list of separate things rather than a flow. But an ordered list would make it look like steps. I thought this was clearest. But I can change if you think it's better. If I do, I would need to change both examples.

<br/>40 hours × $0.09 per hour = $3.60

#### Example: Workers Bindings pricing
If a Workers paid user uses the Workers Bindings method for 50 hours during the month, and uses 10 concurrent browsers for the first 15 days and 20 concurrent hours the last 15 days, the estimated cost for the month is as follows.

For **browser duration**:
<br/>50 hours - 10 hours (included in plan) = 40 hours
<br/>40 hours × $0.09 per hour = $3.60

For **concurrent browsers**:
<br/>((10 browsers × 15 days) + (20 browsers × 15 days)) = 450 total browsers used in month
<br />450 browsers used in month ÷ 30 days in month = 15 browsers (averaged monthly)
<br/>15 browsers (averaged monthly) − 10 (included in plan) = 5 browsers
<br/>5 browsers × $2.00 per browser = $10.00

For **browser duration** and **concurrent browsers**:
<br/>$3.60 + $10.00 = $13.60
6 changes: 5 additions & 1 deletion src/content/release-notes/browser-rendering.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,18 @@ productLink: "/browser-rendering/"
productArea: Developer platform
productAreaLink: /workers/platform/changelog/platform/
entries:
- publish_date: "2025-08-20"
title: Pricing update to Browser Rendering
description: |-
* Billing for Browser Rendering starts on August 20, 2025, with usage beyond the included [limits](/browser-rendering/platform/limits/) charged according to the new [pricing rates](/browser-rendering/platform/pricing/).
- publish_date: "2025-07-03"
title: Local development support
description: |-
* We added local development support to Browser Rendering, making it simpler than ever to test and iterate before deploying.
- publish_date: "2025-06-30"
title: New Web Bot Auth headers
description: |-
* Browser Rendering now supports [Web Bot Auth](/reference/automatic-request-headers/) by automatically attaching `Signature-agent`, `Signature`, and `Signature-input ` headers to verify that a request originates from Cloudflare Browser Rendering.
* Browser Rendering now supports [Web Bot Auth](/reference/automatic-request-headers/) by automatically attaching `Signature-agent`, `Signature`, and `Signature-input ` headers to verify that a request originates from Cloudflare Browser Rendering.
- publish_date: "2025-06-27"
title: Bug fix to debug log noise in Workers
description: |-
Expand Down
Loading