htaccess to Nginx

How to use it

1. Paste your .htaccess into the left panel, or press Sample to see a realistic file converted.
2. Press Convert — the right panel shows a server block with the mapped directives.
3. Read the counter above the panels: it shows how many rules were mapped and how many need manual work.
4. Read the Rules that need manual handling list below; every entry is the original line, also kept as a comment in the output.
5. Copy or download the result as nginx.conf, then review it before deploying.

The converter is line based and deliberately conservative. Anything without a trustworthy equivalent stays visible instead of being thrown away.

Common use cases

• Moving a PHP site to Nginx — the classic WordPress front-controller rules come out as rewrite plus file-existence checks.
• Migrating redirects — Redirect becomes a location block with return, and RedirectMatch becomes a rewrite.
• Rebuilding cache headers — ExpiresByType becomes per-extension location blocks with expires, and AddType values are collected into a types block.
• Auditing a legacy file — the manual list tells you exactly which directives your new config still needs.

Why it stays private

Conversion runs on the text in your browser. Configuration files often contain internal hostnames and paths, and none of that leaves your machine.

FAQ

Q: Why is some output marked for manual review? A: Some Apache directives have no direct Nginx equivalent — PHP settings, environment matching, and custom handlers among them. Guessing would produce a config that looks done and fails at reload, so those lines are flagged instead.

Q: Do I still have to check the result? A: Yes. Nginx evaluates rewrite rules differently from Apache: patterns are matched against the URI with a slash at the front, and if inside location has known caveats. Treat the output as a strong draft, not a drop-in file.

Q: Are RewriteCond conditions converted? A: Where a direct equivalent exists, yes: server variables map to Nginx variables, file tests become -f and -d checks, and conditions become enclosing if blocks. Conditions using [OR] are noted, because Nginx if cannot express them.