Metric Prefix Converter
Move between kilo, mega, milli, micro, nano and every SI prefix — exactly.
JSON into INI sections — dotted section names for nesting, three list styles.
Drop a JSON file here, or click to choose one
Converted on your device — the file is never uploaded
The JSON to INI Converter writes JSON as an INI file: objects become [sections], deeper objects become dotted sections, and arrays take whichever of three list styles your reader expects.
INI files refuse to die: php.ini, my.cnf, Git config, desktop entries, countless Windows and game settings all use the same simple sections-and-keys format. When the settings you have are JSON — from an API, an export or a modern config — you need them rewritten in a shape those readers understand.
Paste JSON and get INI. Top-level values are written first, objects become [sections], and objects inside objects become dotted sections such as [database.options] — the nesting convention PHP’s parse_ini_file, Python’s configparser and most other readers follow. Arrays can be written as repeated key[] lines in PHP style, as numbered key[0] entries, or joined onto a single comma-separated line. Values containing ; # = or a quote are quoted, because an unquoted ; starts a comment and would silently truncate the value.
Nested objects become [database.options], the convention most INI readers use.
key[] for PHP, key[0] for indexes, or one comma-separated line.
Values containing ; or # are quoted so they are not truncated when read back.
Write true/false or on/off to match what the reader expects.
Add a generated-on comment at the top of the file.
It must be an object — an INI file is a set of named keys.
key[] for PHP, key[0] for numbered entries, or one comma-separated line.
true/false or on/off, spaces around the equals sign, an optional header comment.
Drop it into your application or service configuration.
One level becomes a [section]. Deeper levels become dotted sections such as [database.options], which PHP, configparser and most INI readers understand as nesting.
key[] = value for PHP’s parse_ini_file, key[0] = value when the reader expects indexes, and a comma-separated line for simple readers that split values themselves.
Because a semicolon or hash starts a comment in INI, and an unquoted value containing one would be cut short. Values with equals signs, quotes or line breaks are quoted for the same reason.
No. Everything is text once read back, so numbers and booleans are written plainly and it is up to the reader to cast them. That is a limitation of the format, not of the conversion.
What people who use the JSON to INI Converter think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON to INI Converter. It takes half a minute and no account.
Write the first reviewMove between kilo, mega, milli, micro, nano and every SI prefix — exactly.
Find the closest PANTONE® solid colour to any HEX, RGB or CMYK colour.
JSON records into a formatted .xlsx — nested keys flattened, dates typed, filters on.
YAML back into well-formed XML — lists as repeated tags, @keys as attributes.
Swap between comma, semicolon, tab and pipe — and fix comma decimals while you are there.
Strip RTF back to readable text, without the font tables and control words.
Turn 24-hour and military times into AM/PM, in bulk or inside text.
AWG and SWG to mm², diameter, circular mils and resistance per length.