Redirects

Redirect Generator

List old and new URLs, choose the status code, and get ready-to-deploy redirect configuration for your hosting platform. The tool only writes the code — it does not change your server or test live redirects.

Back

1. Redirect mappings

Local

Old: a path starting with / (or a full URL for one host). New: a path or a full http(s) URL.

Redirect mapping
#OldNewStatus

2. Configuration

.htaccess
Enter an old path and a new destination to generate redirect code.

This tool only generates configuration. Deploy it to your hosting platform yourself and test every redirect — it does not create, change or test live redirects.

About this tool

About Redirect Generator

Redirect Generator turns a list of old and new URLs into redirect configuration for Apache .htaccess, Nginx, Netlify _redirects or Vercel vercel.json, with 301, 302 or 308 status codes. It validates every mapping and blocks empty rows and obvious loops.

When pages move, redirects send visitors and search engines to the new address. Writing the rules by hand for each platform is fiddly and easy to get wrong; generating them from one table keeps them consistent. The tool writes code only — you deploy and test it on your host.

How to use

Step by step

  1. Enter the old path (starting with /) or full URL in the first row.
  2. Enter the new path or full URL and choose 301, 302 or 308.
  3. Add more rows for every page that moved.
  4. Fix any highlighted rows — empty, invalid or looping redirects are blocked.
  5. Choose your platform: Apache, Nginx, Netlify or Vercel.
  6. Copy or download the code, deploy it to your host, and test each redirect.
Key features

What it offers

  • Single or many redirects in one table
  • 301, 302 and 308 status codes per row
  • Apache, Nginx, Netlify and Vercel output
  • Checks for empty rows, invalid paths, duplicates and loops
  • Warnings for redirect chains
  • Readable mapping table, Copy and Download
Best practices

Tips for best results

  • Use 301 or 308 for permanent moves and 302 only for temporary ones.
  • Redirect each old URL straight to its final destination, not through a chain.
  • Point old pages to the most relevant new page rather than the home page.
  • Back up your existing configuration before adding new rules.
  • Test every redirect after deploying, and update internal links to the new URLs.
Benefits

Why people use it

One table, four platforms

Switch output without retyping your redirects.

Fewer mistakes

Validation catches loops, duplicates and malformed paths.

Readable

A mapping table shows exactly what each rule does.

Private

Generated locally; your server is never touched.

FAQ

Common questions

Use 301 (or 308) for permanent moves and 302 for temporary ones. 308 is like 301 but tells clients to keep the request method, which matters for forms and APIs.
Apache .htaccess (mod_rewrite), Nginx server configuration, Netlify _redirects and Vercel vercel.json. Switch platforms at any time; your redirects are kept.
Yes. Enter a full http(s) URL to redirect only requests for that host, or a path starting with / to match any host the configuration is used on.
Not in the old URL — enter the path only. Destinations may include a query string. Paths with spaces or unsafe characters must be percent-encoded (for example %20).
The tool blocks empty rows, a page redirecting to itself, duplicate old paths, and two rows that redirect to each other, and warns about redirect chains.
No. It only generates configuration text. You must deploy it to your hosting platform yourself and test each redirect, for example in a private browser window.
No. Everything is generated in your browser; nothing is sent to a server.
Private by design

This runs entirely in your browser

No file or text you enter here is uploaded. Encoding and decoding happen on your device using native browser APIs — close the tab and nothing remains on a server.

Install Toolisco Add it to your device for offline, one-tap access.