Which Apache flags are supported?

The converter handles the common subset: R and R=301/302 for redirects, L for last, QSA for query-string append, NC for case-insensitive, F for forbidden (403), and G for gone (410). Less common flags are ignored.

How is a RewriteCond handled?

A RewriteCond that tests HTTP_HOST, REQUEST_URI, QUERY_STRING, or HTTPS becomes an Nginx if guard around the rule. File-existence checks against REQUEST_FILENAME map to try_files instead, which the notes explain.

Why does Nginx not chain conditions like Apache?

Apache applies all preceding RewriteCond lines to one RewriteRule. Nginx if blocks do not chain, so multiple conditions are emitted separately and flagged in the notes so you can combine them manually.

Is the output production-ready?

Treat it as a strong first draft. Apache per-directory context and Nginx location context differ, so always test the generated rules against real URLs and confirm redirect status codes before going live.

Does my .htaccess get uploaded?

No. Parsing and conversion happen entirely in your browser with JavaScript. Your rules, including any internal paths or hostnames, never leave your device.

.htaccess to Nginx Rewrite Converter

Migrating a site from Apache to Nginx means translating mod_rewrite rules, which live in .htaccess, into Nginx’s rewrite, return, and location directives. The two engines share a PCRE-style regex syntax but differ in structure and flag handling. This .htaccess to Nginx converter parses your rewrite rules and produces matching Nginx blocks in your browser.

How it works

Apache rewriting is organised into rule blocks: zero or more RewriteCond lines followed by a single RewriteRule they apply to. The converter walks your input and processes each block:

A RewriteRule with R=301 or R=302 becomes a return <code> <target>;.
A plain internal rewrite becomes rewrite "<pattern>" <target> last; or break.
F becomes return 403; and G becomes return 410;.
A preceding RewriteCond testing %{HTTP_HOST}, %{REQUEST_URI}, %{QUERY_STRING}, or %{HTTPS} becomes an if guard wrapping the rule.

Because Apache per-directory rules match the path without a leading slash but Nginx matches with one, the converter adds a leading slash to anchored patterns and notes when it does so.

Example

The Apache rule:

RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

converts to an Nginx host guard with a permanent redirect:

if ($host ~* "^example\.com$") {
    return 301 https://www.example.com/$1;
}

Notes

This covers the most common directives, not every edge of mod_rewrite. Nginx does not chain if conditions the way Apache chains RewriteCond, and file-existence checks (-f, -d) map to try_files rather than an if. Read the conversion notes, then test each block against real URLs before deploying. Everything runs locally, so your rules stay private.