Nginx Config to JSON - Parse Configuration Files

Convert Nginx configuration files to JSON format. Parse server blocks, locations, directives. Analyze configs in your browser.

Drop Nginx config here or click to browse

.conf configuration files

Nginx Configuration

Include comments

Compact JSON

JSON Output

Apache .htaccess to Nginx Converter - Se…

ENV to JSON - Parse Environment Files

COBOL Copybook Parser - Data Layout Anal…

REG to JSON - Windows Registry Parser

Crontab File Parser - Convert Jobs to JS…

View all Config parsers →

Frequently Asked Questions

Server blocks, location blocks, upstream definitions, all directives with their values, nested blocks, and comments. The full hierarchical structure is preserved in the JSON output.

Each block (server, location, upstream) becomes a JSON object with a 'type' field and 'directives' array. Nested blocks are placed in a 'blocks' array within their parent.

Yes, comments are extracted and can be included in the output. Each comment is associated with the directive or block it precedes. Toggle comment preservation in the options.

Absolutely. The output contains an array of all top-level blocks (http, server, events, etc.). Each server block with its locations is a separate object in the hierarchy.

Simple directives become key-value pairs. Multi-value directives (like server_name with multiple domains) become arrays. Quoted strings preserve their quotes for regex patterns.

Yes. All parsing happens in your browser. Your Nginx configs never leave your device. This is safe for parsing production configuration files.

Include directives are shown in the output but cannot be resolved (the tool doesn't have file system access). You'll see the include path for reference.

This tool parses syntax but doesn't validate semantics. Use 'nginx -t' to validate configs. This tool helps you understand and analyze the structure.

Nginx variables ($host, $uri, etc.) are preserved as-is in the output. They appear as string values exactly as written in your configuration.

The parser is tolerant and will parse what it can. Malformed sections may appear incomplete. Check the error count in the output for parsing issues.

Related Tools