Stop hand-translating your redirects between platforms.

Paste your next.config.js redirects, headers, or rewrites block and get the equivalent config for Netlify, Vercel, or Nitro instantly.

Zeeshan Tofiq

Full Stack Developer

Share

How RedirectConverter works

1. 1

   Paste your next.config.js block

   Paste the full async function (e.g. async redirects() { return [...] }) or just the returned array. The tool accepts redirects, headers, and rewrites blocks. Comments and trailing commas are handled automatically.

2. 2

   Select the rule type

   Choose Redirects, Headers, or Rewrites, or leave it on "Auto-detect." The tool detects the type from the function name or from the shape of the objects (presence of a headers array, permanent field, etc.).

3. 3

   Pick your target format

   Choose between netlify.toml (Netlify), vercel.json (Vercel), or nitro.config.ts (Nitro, used by TanStack Start, Nuxt, and other Nitro-based frameworks).

4. 4

   The parser extracts your rules

   A restricted JavaScript object literal parser (not eval) tokenizes your input, handles unquoted keys and single-quoted strings, and produces a structured array of rule objects.

5. 5

   Path patterns are translated

   Next.js path patterns like :path* are converted to the target format's equivalent: * and :splat for Netlify, ** for Nitro. Named parameters like :slug are preserved where the target supports them.

6. 6

   Output, mapping table, and warnings

   You get the complete converted config with a copy button, a per-rule mapping table showing how each input rule translated, and warnings for any rules that don't convert cleanly (e.g. conditional 'has' matching).

What each target format looks like

The same redirect rule produces different syntax depending on the target platform. Here is how a simple permanent redirect from /old to /new looks in each format.

[[redirects]]
  from = "/old"
  to = "/new"
  status = 301

{
  "redirects": [
    {
      "source": "/old",
      "destination": "/new",
      "permanent": true
    }
  ]
}

export default defineNitroConfig({
  routeRules: {
    '/old': { redirect: { to: '/new', statusCode: 301 } },
  },
})

Path pattern translation reference

Next.js, Netlify, and Nitro use different syntax for dynamic path segments and wildcards. This table shows how RedirectConverter maps each pattern.

Vercel uses the same path syntax as Next.js (both are Vercel products), so redirect rules transfer with minimal changes. Netlify uses * for catch-all and :splat in the destination. Nitro uses ** for recursive glob matching.

When to use RedirectConverter

What does not convert cleanly between platforms

Next.js, Netlify, Vercel, and Nitro do not share a redirect model, so some rules have no exact equivalent. The converter flags these rather than guessing, because a silently wrong redirect is worse than one you were told to check.