SQL Formatter
Re-indent a SQL query into readable clauses, joins and conditions.
Convert an INI or config file into structured JSON, sections and all.
The INI to JSON converter turns sections into objects, nests dotted section names, keeps pre-section keys at the root, strips both comment styles and types the values — with typing switchable off.
INI is still everywhere — php.ini, my.cnf, tox.ini, .gitconfig, systemd units, Windows desktop entries — and nothing reads it natively any more. This converter turns one into JSON so a script, a template or a test can work with it.
Sections become objects, and a dotted section name such as [db.pool] nests rather than becoming a key with a dot in it. Keys written before the first section stay at the root. Comments beginning with either a semicolon or a hash are dropped, quoted values have their quotes removed, and values are typed: true, yes and on become booleans, numbers become numbers, and everything else stays a string. You can turn typing off when the consuming system wants strings throughout.
A [db.pool] header becomes a pool object inside db, rather than a key with a dot in its name.
Semicolon and hash comments are recognised, including trailing ones — but not inside a quoted value, where they are content.
Keys written before the first section stay at the top level, matching how every INI reader treats them.
true, yes and on become booleans and numbers become numbers, or everything stays a string when the consumer expects that.
A quoted value has its quotes stripped, so the JSON holds the value rather than the quoting.
php.ini, my.cnf, a .gitconfig, a systemd unit or any key = value config.
Dotted names such as [db.pool] can nest, or stay as one flat key.
Type detection gives real booleans and numbers; turn it off to keep strings.
Formatted and ready to use in a script or a test fixture.
Both. A line beginning with a semicolon or a hash is a comment, and a trailing comment after a value is stripped unless the value is quoted.
They stay at the root of the JSON object, which matches how every INI reader treats them.
No — the last one wins, which is how most INI parsers behave. A file relying on repeated keys as a list needs a format that has lists.
Type detection reads true, false, yes, no, on and off as booleans. Turn detection off if your value is genuinely the word.
What people who use the INI to JSON 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 INI to JSON. It takes half a minute and no account.
Write the first reviewRe-indent a SQL query into readable clauses, joins and conditions.
Find the MIME type for any file extension, or the extensions for a type.
Build a valid package.json with scripts, exports and metadata.
Generate Go structs with json tags from a sample payload.
Break an emoji into its code points, modifiers and joiners.
Render Markdown to clean HTML, with tables, task lists and fenced code.
Generate Python dataclasses with type hints from a sample JSON document.
Encrypt text with a password using AES-GCM, and decrypt it back.