INI to JSON - Migrate Windows Config Files

Convert INI config files to JSON format instantly. Parse php.ini, my.cnf, Windows registry exports, and legacy configs. Fast, private, browser-based.

INI Input

0 sections, 0 keys

JSON Output

Parse numbers/booleans

Convert dot notation to nested objects

Minify output

Copied to clipboard

Related Tools

REG to JSON - Windows Registry Parser

Cron Expression Parser - Validate Schedu…

Nginx Config to JSON - Parse Configurati…

Hosts File to JSON - Parse System DNS Ov…

Apache .htaccess to Nginx Converter - Se…

COBOL Copybook Parser - Data Layout Anal…

View all Config parsers →

Frequently Asked Questions

INI is a configuration file format consisting of sections, keys, and values. Popularized by Windows, it uses simple text structure: [section] headers followed by key=value pairs. Common in PHP (php.ini), MySQL (my.cnf), and legacy applications.

Windows .reg exports use INI-like syntax with [HKEY_...] sections. This converter parses them into nested JSON objects, preserving the registry path hierarchy and converting quoted strings.

PHP configuration files are parsed with sections like [PHP], [Date], [MySQL]. All key=value pairs become JSON properties. Comments are stripped, and multiline values are supported via continuation syntax.

Sections become top-level JSON objects. [database] becomes {"database": {...}}. Values before any section are stored in a "_global" object or at root level depending on options.

No. Lines starting with semicolon (;) or hash (#) are treated as comments and excluded from JSON output. INI format is for configuration, JSON doesn't support comments natively.

INI format stores everything as text. While you can enable type parsing to convert "123" to numbers and "true" to booleans, INI itself has no data type definitions. String preservation is safest for exact migration.

Yes. Some INI dialects use dot notation (section.subsection) or colon syntax. Enable nested parsing to convert these into deep JSON structures: {"section": {"subsection": {...}}}.

Values spanning multiple lines with backslash continuation (\) or indentation are concatenated. The converter joins them into single JSON string values, preserving content but removing formatting.

UTF-8 is standard. Windows INI files may use Windows-1252 or other legacy encodings. If special characters appear corrupted, convert the file to UTF-8 before processing.

JSON is easier to parse in modern languages, supports nesting naturally, integrates with APIs, and works seamlessly with JavaScript applications. Perfect for modernizing legacy configurations into microservices or web apps.