INI to JSON Converter

Convert INI configuration files to JSON online. Sections become nested objects, with support for dotted section names — all in your browser.

Input INI
Drop INI file here
JSON Output

Features

📐 Faithful INI Parsing

  • Global keys (before any section) become top-level fields
  • [section] headers become nested objects
  • Dotted section names create deeper nesting
  • Comments (; and #) and quoted values handled

⚡ Privacy-First

  • All parsing happens in your browser
  • No data ever sent to a server
  • Pairs with our JSON to INI converter
  • Download or copy the resulting JSON instantly

🔧 Real-World Configs

  • PHP php.ini style configuration files
  • Windows application settings files
  • Game engine and legacy tool configs
  • Optional automatic number/boolean detection

INI to JSON Guide

INI files organize settings into [section] blocks of key=value pairs, with any keys that appear before the first section header treated as "global" settings. This converter reads that structure and builds an equivalent JSON object: global keys become top-level fields, and each [section] becomes a nested object holding its own keys. If a section name contains a dot — [profile.release] — the converter treats it as two levels of nesting, matching the same convention used by this site's JSON to TOML converter, so a file produced by our JSON to INI tool round-trips back to its original shape.

With "Infer types" enabled, values that look like integers, decimals, or true/false are converted to their JSON equivalents; disable it to keep everything as plain strings, which matters for values like version numbers or IDs that happen to look numeric but shouldn't be treated as numbers.

Frequently Asked Questions

Does it handle comments?

Yes — both ; and # style comments are stripped, whether they're on their own line or trailing after a value, as long as they're outside of a quoted string.

What about arrays?

INI has no universally standard array syntax, so this converter treats every value as a plain scalar rather than guessing at comma-splitting — a value like tags=a,b,c becomes the literal string "a,b,c". If your INI file was generated by our JSON to INI tool, split that string on commas yourself, or use YAML or TOML instead for a format with native array support.

Are quoted values unwrapped?

Yes — values wrapped in single or double quotes have the quotes removed and are always kept as literal strings, bypassing type inference, so a quoted "007" stays the string "007" instead of becoming the number 7.

What if the same key appears twice in one section?

The last occurrence wins, matching how a plain JavaScript object assignment behaves and how most INI parsers resolve duplicate keys — earlier values for the same key within a section are silently overwritten.