Nginx Config Generator

The Nginx Config Generator is a free online tool that generate production-ready nginx configs with ssl, reverse proxy, php-fpm, gzip, caching, security headers, rate limiting, and redirects. 7 presets included.. It runs entirely in your browser with no installation or sign-up needed.

Seven: Static Site, WordPress, Node.js, Laravel, Next.js, Django, SPA (React/Vue). Each pre-fills appropriate settings.

Generates a server block for nginx.conf or sites-available. Rate-limiting zone directives shown as comments for the http block.

No. Everything runs client-side in your browser.

Yes, the Nginx Config Generator is 100% free with no registration, no hidden fees, and no usage limits. All processing happens locally in your browser, ensuring complete privacy.

Absolutely. The Nginx Config Generator processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the Nginx Config Generator is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the Nginx Config Generator in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The Nginx Config Generator works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

In Nginx, rate limiting needs two pieces that live in different contexts. The limit_req_zone directive defines a shared memory zone (for example, zone=ratelimit:10m rate=...) and is only valid in the top-level http block, because the zone is shared across all server blocks. The matching limit_req directive, which actually enforces the limit with a burst value, belongs inside the server or location block. If you paste limit_req_zone into a server block, Nginx fails to start with a "directive is not allowed here" error. That is why this generator places the limit_req line directly in your server block but emits the limit_req_zone line as a labeled comment, reminding you to move it up into the http context. Enable rate limiting in the tool and copy both pieces into the right place.

A reverse proxy config uses proxy_pass to forward requests to a separate application server running on its own port, such as a Node.js, Next.js, or Django/Gunicorn process on 127.0.0.1:3000 or :8000. Nginx adds headers like X-Real-IP, X-Forwarded-For, X-Forwarded-Proto, and Host, plus Upgrade and Connection headers when WebSockets are enabled. A PHP-FPM config instead uses a location ~ \.php$ block with fastcgi_pass pointing at a Unix socket and includes fastcgi_params, so Nginx hands PHP files to the FPM process directly rather than proxying HTTP. WordPress and Laravel use the FastCGI path; Node, Next.js, and Django use the reverse proxy path. Pick the matching preset in the generator and it wires up the correct directives for your stack.

Both redirects are handled cleanly in a single server block setup. For HTTP-to-HTTPS, a separate server listening on port 80 catches plain requests and issues a 301 to the https:// version, while your main server listens on 443 with SSL. For www versus non-www canonicalization, you redirect one host to the other, again with a 301, so search engines and browsers settle on a single canonical domain instead of treating www and root as duplicate sites. Doing this by hand risks redirect loops if the rules overlap or a directive lands in the wrong server. Toggle HTTP-to-HTTPS and your preferred www or non-www option in the generator, and it writes the correctly ordered redirect blocks for you to copy.

Adding http2 to the listen 443 ssl line enables HTTP/2, which multiplexes many requests over one connection and noticeably speeds up pages with lots of assets, with no application changes needed. Restricting ssl_protocols to TLSv1.2 and TLSv1.3 drops the older SSLv3, TLS 1.0, and TLS 1.1 protocols that are deprecated and vulnerable to attacks like POODLE and BEAST, so modern clients negotiate only secure ciphers. The generator also adds a hardened cipher suite, a session cache, optional HSTS with preload, and OCSP stapling so certificate revocation checks do not slow the handshake. These are defaults people often forget when hand-writing configs. Enable the SSL section in the tool and these settings are filled in for you to review before deploying.

Single-page apps handle routing in JavaScript, so when a user refreshes a deep link like /dashboard, the browser asks Nginx for a real file at that path. Without special handling, Nginx returns 404 because no such file exists on disk. The fix is a try_files directive that falls back to your index.html: try_files $uri $uri/ /index.html;. This serves real static assets when they exist but routes every unknown path back to the app shell, letting the client router take over. Forgetting this line is the single most common reason SPA refreshes break in production. The SPA (React/Vue) preset in this generator sets up that history fallback automatically, along with gzip and asset caching, so copy the output and your routes survive a hard refresh.