Netlify Redirects Tester

How to use

1. 1Paste the body of your _redirects file into the rules input on the left, or click a sample (basic migration, SPA fallback, rewrite, country-conditional, or chain/loop/shadow).
2. 2Paste the candidate URLs to test (one path per line, like /blog/launch-day) into the URLs input below. Absolute URLs are accepted and the path part is used for matching.
3. 3If your rules use Country, Language, Role, or Cookie conditions, fill in the optional request context fields. Leave them blank to ignore conditional rules.
4. 4Read each result card on the right: the verdict badge (Redirect 301, Rewrite 200, No match, Loop, 410 Gone, and so on), the matched rule and line number, the destination after :splat and :param substitution, and the full hop trace for chained redirects.
5. 5Use Copy report to grab a plain-text trace for a pull request, code review, or migration ticket. Fix any rule the parser flags as an error or warning, then re-run.

About this tool

Netlify Redirects Tester emulates Netlify's documented _redirects engine in your browser. Paste the body of a _redirects file (the same syntax Cloudflare Pages uses), then paste one or more candidate URLs. For each URL the tester walks the rules in order, picks the first match, and reports what would actually happen on a live deploy: the matched rule and its source line, the destination after :param and :splat substitution, the effective status code (301, 302, 303, 307, 308 for browser redirects, 200 for in-place proxy or SPA fallback rewrites, 404 for a custom not-found body, 410 for permanently gone), and the full hop trace when one redirect points at a URL that is itself redirected by another rule. A loop detector trips when a hop returns to a URL the chain has already visited, so you can see exactly which rule closes the cycle before you ship a broken deploy. A shadow detector flags later rules whose source is already covered by an earlier unconditional rule and that therefore never fire. The parser understands every part of the documented grammar: comments starting with #, path patterns with literal segments, wildcard * captured into :splat, named :param captures used in the destination, forced rules with a trailing !, and conditions (Country, Language, Role, Cookie) where multiple values are comma-separated OR and multiple keys are AND. The optional request context fields (Country, Language, Role, Cookie) let you evaluate conditional rules without spinning up a real deploy: leave them blank to ignore conditional rules entirely, or set them to see how a French visitor or a logged-in editor would actually be routed. The grammar checks also catch the small mistakes that survive into production: destinations using :splat without a wildcard source, destinations using a :param the source never captures, source paths missing a leading slash, status codes outside Netlify's documented set, and source-equals-destination rules that are no-ops or one-line infinite loops. Everything runs locally on your device; the rules file, the candidate URLs, and the request context never leave the browser tab.

Free to use. Works in your browser. No signup, no login.