Skip to content

Clarify Browser Rendering limits vs pricing relationship #27803

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

Jump to bottom
Open
kathayl wants to merge 2 commits into
base: production
Choose a base branch
from
Open

Clarify Browser Rendering limits vs pricing relationship #27803

kathayl wants to merge 2 commits into from

Conversation

@kathayl
Copy link
Contributor

@kathayl kathayl commented Jan 22, 2026

  • Add 'Concurrent browsers and pricing' subsection explaining 10 included, 30 max
  • Create 'Rate limits and errors' section with 'Understanding rate limits' subsection
  • Consolidate rate limit explanation with clear table showing per-second fill rates
  • Replace duplicate browser timeout notes with single footnote
  • Clarify upgrade path: Free users should upgrade first, then request higher limits
  • Remove duplicate DashButton from FAQ section

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@kathayl
Clarify Browser Rendering limits vs pricing relationship
3691007 
- Add 'Concurrent browsers and pricing' subsection explaining 10 included, 30 max
- Create 'Rate limits and errors' section with 'Understanding rate limits' subsection
- Consolidate rate limit explanation with clear table showing per-second fill rates
- Replace duplicate browser timeout notes with single footnote
- Clarify upgrade path: Free users should upgrade first, then request higher limits
- Remove duplicate DashButton from FAQ section
@kathayl kathayl requested review from a team, ToriLindsay, celso and mchenco as code owners January 22, 2026 18:35
@github-actions
Copy link
Contributor

github-actions bot commented Jan 22, 2026

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/browser-rendering/ @mchenco, @cloudflare/pcx-technical-writing, @celso, @kathayl, @ToriLindsay

@github-actions
Copy link
Contributor

github-actions bot commented Jan 22, 2026 •
edited
Loading

Preview URL: https://7cf784da.preview.developers.cloudflare.com
Preview Branch URL: https://br-limits-pricing-clarity.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link Updated Link
https://developers.cloudflare.com/browser-rendering/limits/ https://br-limits-pricing-clarity.preview.developers.cloudflare.com/browser-rendering/limits/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mchenco mchenco Awaiting requested review from mchenco mchenco is a code owner

@celso celso Awaiting requested review from celso celso is a code owner

@ToriLindsay ToriLindsay Awaiting requested review from ToriLindsay ToriLindsay is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

@celso celso

@mchenco mchenco

@ToriLindsay ToriLindsay

Labels

product:browser-rendering size/s

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kathayl @celso @mchenco @ToriLindsay