Micro Tools
Advertisement

INI to JSONL converter

Convert INI to JSONL free in your browser. Paste your INI on the left, press Convert, and copy clean JSON Lines on the right. No sign-up, no uploads.

Converter

Paste INI below, press Convert, and copy the JSON Lines output.

Advertisement

How INI becomes JSONL

The parser scans the INI line by line, tracking the current [section] header and turning every key = value line into a row with section, key and value columns. Comments and blank lines are skipped, quoted values are unwrapped, and scalars are auto-typed, giving a tidy three-column table that maps directly onto JSON Lines.

Tips for the JSON Lines output

JSON Lines is the friendliest shape for big data: stream it into BigQuery, ClickHouse or a log pipeline without loading everything into memory. Because each row is independent, you can also split the output file by line count and process chunks in parallel.

Related tools

JSON formatterFormat and validate JSON, privately. Regex testerTest regex live with highlighting. Base64 encoderBase64 encode and decode, plus URL encoder and JWT decoder.

INI to JSONL FAQs

How are INI sections turned into rows?
Every key under a [section] becomes one row with three columns: section, key and value. Keys before the first section header get an empty section name. Comments starting with ; or # are ignored, and quoted values keep their inner text while numbers and true/false are typed automatically.
How is each line formed?
Exactly one compact JSON object per row, one per line, with no trailing comma and no outer array. That is the format log shippers, BigQuery, ClickHouse and most streaming ingest tools expect, so the output can be piped straight in.
What happens to nested or repeated sections?
Repeated [section] headers are merged in order, so duplicate keys keep their last value, and each section/key pair becomes its own row. That flat section/key/value table maps cleanly onto JSON Lines without losing which section a value came from.
Is there a size limit for INI input?
No hard limit, but everything runs in your browser tab, so tens of thousands of rows convert in seconds while millions of rows may slow the page. For very large INI files, split them into smaller chunks and convert each separately.
Is my INI data private, and who uses this?
Yes. The conversion runs 100% in your browser; nothing is uploaded to any server. Developers, analysts and DBAs use it to move INI data into JSON Lines for migrations, reports and config work without installing anything.
Advertisement