๐ Input Nginx Config
โ๏ธ Conversion Options
๐ฆ Caddy Config Output
// Paste Nginx config on the left to auto-generate Caddyfile
Free online tool to convert Nginx configuration to Caddyfile format with auto HTTPS, reverse proxy, and rewrite rules conversion
Zero Dependencies ยท Works Offline// Paste Nginx config on the left to auto-generate Caddyfile
The Nginx to Caddy Config Generator is an online tool for DevOps engineers and developers that automatically converts Nginx server configuration blocks into Caddyfile format. When migrating from Nginx to Caddy, this tool saves you from manually rewriting configurations by generating clean Caddyfile configs with one click, including automatic HTTPS certificate handling.
1. Paste your Nginx configuration in the input box, or click "Load Example" for a demo; 2. Select auto HTTPS mode and output format; 3. The tool auto-generates Caddyfile config in real-time; 4. Click "Copy" to copy the config; 5. Save as Caddyfile and start the server with caddy run.
When migrating from Nginx to Caddy, batch convert existing Nginx configs to Caddyfile for a quick web server switch.
Tired of manually configuring SSL certificates? Convert Nginx configs to Caddy and enjoy automatic HTTPS.
Caddyfile syntax is simpler than Nginx. Use this tool to convert complex Nginx configs into clean Caddyfiles.
Caddy is a modern web server created by Matthew Holt, known for automatic HTTPS via the ACME protocol (auto-provisioning Let's Encrypt certificates). Caddyfile is Caddy's native config format with simple, intuitive syntax that significantly reduces code compared to Nginx. Caddy supports HTTP/3, reverse proxy, load balancing, static file serving, logging, and other common web server features. Caddy v2 is written in Go with performance close to Nginx while providing a better developer experience.
A modern web server known for automatic HTTPS and simple Caddyfile syntax, auto-provisioning SSL certificates.
server_name, listen, location, proxy_pass, rewrite, return, root, index, try_files, and more.
Auto-detects domains and provisions Let's Encrypt certificates. Just write the domain in Caddyfile.
Yes. Follows Caddy's official conventions. Use with caddy run. Test in staging first.
Nginx: flexible but complex. Caddy: auto HTTPS, simpler config. Nginx has mature ecosystem, Caddy better DX.
Completely safe. 100% browser-based processing, no server uploads.