/
Redirect Supply vs Netlify redirects: Change a redirect without a deploy
Netlify handles redirects well for sites it hosts: rules in a _redirects file or netlify.toml, with 301s, 302s, and placeholders for whole sections. Every change, though, ships with a new deploy, and the rules belong to that Netlify site. Redirect Supply keeps redirects outside your codebase: anyone on your team can update a rule in the dashboard, and old URLs keep working wherever your site is hosted next.
Redirect Supply vs Netlify: who can change a redirect, and when
Decision factor
Redirect Supply
Netlify redirects
Choose based on
How rules are written
A form in the dashboard, no code
Lines in a _redirects file or netlify.toml
Whether redirects should live in your codebase
Making a change
Edit the rule and save
Commit the change and run a new deploy
How often your redirects change
Who can change a redirect
Anyone on your team with dashboard access
Someone with access to the repository and deploys
Whether marketing can update links without a developer
After you leave Netlify
Redirects keep running, whatever platform comes next
Rules stay with the Netlify site they were deployed with
Moving your site to another host
Large redirect sets
Unlimited path rules on every paid plan
Above 10,000, Netlify recommends wildcards or Edge Functions
Big migrations with many old URLs
Best fit
Rebrands, migrations, and teams where non-developers manage links
Developer-run sites that stay on Netlify
If redirects shouldn't need a deploy, Redirect Supply
Why Redirect Supply
Choose Redirect Supply for redirects that stay out of your way. Every old URL lands on the right page, every domain runs on HTTPS, and nothing breaks when your website moves.
Netlify redirects or Redirect Supply? The short answer
Keep Netlify redirects if your site stays on Netlify and your developers are happy managing rules in the codebase.
Switch to Redirect Supply if marketers or designers need to change redirects themselves, if you're moving off Netlify, or if you're redirecting domains with no Netlify site behind them. There's a free plan to start, HTTPS included.
For redirects anyone on the team can manage, that makes it a Redirect Supply job.
FAQs
Questions about Netlify redirects and Redirect Supply
Where do Netlify redirects live?
In a _redirects file in your site's publish directory, or in the netlify.toml configuration file. Netlify processes the _redirects file first, then the rules in netlify.toml. In Redirect Supply, redirects live in a dashboard, separate from your code.
Do Netlify redirect changes need a deploy?
Yes. Netlify processes redirect rules during deployment, so every change ships with a new deploy. In Redirect Supply, you edit a rule and save it, with no build or deploy involved.
Can non-developers manage Netlify redirects?
Only if they can edit the repository and trigger a deploy. With Redirect Supply, anyone with dashboard access can add or change a redirect, so marketing can update campaign links without waiting for a developer.
What happens to my Netlify redirects if I move my site?
They're part of the Netlify site's deploy, so they stop applying once the site is hosted elsewhere. Connect the old domain to Redirect Supply, and every old URL keeps landing on its new page. See keep SEO intact.
How many redirects can Netlify handle?
Netlify recommends using wildcards or placeholders as much as possible once you reach around 10,000 redirects, and Edge Functions for more complex setups. Redirect Supply includes unlimited path rules and wildcards on every paid plan.
Can I move my Netlify redirects into Redirect Supply?
Yes. Each line in a _redirects file, like /old-page /new-page 301, maps directly to a CSV row in Redirect Supply's import format. Splat rules like /blog/* become wildcard rules.
Have more questions?
Daniel Kouba
Founder of FREAKS
Vojtech Elias
Reflektor Studio
