Cloudflare Pages / Workers Static Assets
Catch `_redirects` problems before deployment.
Paste a Cloudflare _redirects file to check documented syntax,
status codes, ordering, placeholders, proxy rules, and rule limits in your browser.
- No account; pasted or selected files stay in this tab
- Input stays in this browser tab
- Source-linked, conservative checks
Browser-only preflight
Inspect your rules
or drop a plain-text file here · maximum 2 MiB
Paste rules or choose a local file. Nothing is uploaded.
No rules checked yet.
Diagnostics
- Run the preflight to see source-linked checks.
Parsed rules
| Line | Source | Destination | Status | Type | State |
|---|
What this checks
The limits that are easy to miss
Conservative classifications
Only confirmed errors block the result.
- CONFIRMED_ERROR
- Directly contradicted by reviewed Cloudflare documentation.
- CONFIRMED_WARNING
- Documented behavior that may make the rule ineffective or surprising.
- POTENTIAL_ISSUE
- Likely compatibility risk that needs platform review.
- UNSUPPORTED_CHECK
- Outside this local checker’s scope.
- UNKNOWN
- Not established by the reviewed documentation.
Important limitations
Preflight, not a production guarantee.
- Checks are based on public Cloudflare documentation and a versioned local rule set.
- It does not run Cloudflare's production parser or inspect your account configuration.
- Pages Functions, Bulk Redirects, framework output paths, and deploy-mode differences need separate review.
- Workers Static Assets rules do not apply when Worker code serves the matching request.
- A clean report means “no documented blocking rule found,” not “deployment is guaranteed correct.”
Official sources: Pages redirects · Workers Static Assets redirects
Revenue-path hypothesis
Would a maintained CLI / CI check be useful?
This experiment has no payment flow. In the reviewed deployment package, this button sends only an aggregate event name after explicit deployment approval; it never sends redirect contents.
Privacy
Your rules stay in the browser.
The checker has no account, advertising script, payment integration, cookie, or persistent browser ID. Do not paste secrets: redirect rules can still contain private internal paths or tokens. A separately approved deployment may collect allowlisted aggregate events, but never rule text, paths, filenames, report contents, IP addresses in application storage, or detailed fingerprints.