InstantTools.siteZero Latency Utilities
dev Tool
100% In-Memory (Zero Server Upload)

Redirect Rule Generator

Convert old and new paths into Apache, Nginx, Next.js or plain redirect mappings, with 301, 302, 307 and 308 status codes.

Redirect rules

Same-host paths
Rule 1

Generated redirect config

Which status code to use

301 is a permanent move (use when the change is final). 302 is a temporary move. 307 and 308 are permanent/temporary versions that preserve the request method — important for API routes (for example 308 after a POST-to-GET migration). Next.js redirects() only distinguishes permanent (true) from temporary, so 301/308 map to permanent and 302/307 map to temporary. Tick "Wildcard / pattern" on a rule to emit RedirectMatch (Apache) and a location ~ … regex block (Nginx) instead of the exact-match forms; a * in the old path becomes a capture group.

About Redirect Rule Generator

Turn a list of old paths and their new destinations into configuration you can paste into your server. Choose the target — Apache .htaccess rules, an Nginx location block, the redirects array from next.config.js, or a plain old-to-new mapping — and pick a 301, 302, 307 or 308 status for each rule. The output switches between tabs so you copy exactly the format you need, and a note explains when a permanent redirect is the right choice versus a temporary one.

Key Features & Privacy Guarantee

  • Zero server transmission: all computation happens instantly in your local browser runtime.
  • No sign-up, no subscriptions, and no usage quotas.
  • Optimized for maximum speed, accuracy, and lightweight performance.
  • Instant one-click clipboard copying.

Frequently Asked Questions

Common questions and helpful answers about this utility.

A 301 is a permanent move and tells search engines to transfer ranking signals to the new URL. A 302 is temporary, so it suits a change that is under review or might be reverted.