INI Beautifier

INI Beautifier

What the INI beautifier does

This page takes INI-style text and reformats it as one key-value pair per line. In Beautify mode it writes key = value with spaces around the equals sign. In Minify mode it removes those spaces. You can paste the text or load it from a public URL, then copy or download the result as an .ini file. It is a quick readability aid for a small, simple configuration file, not a faithful round-trip editor for every INI dialect.

Sections and comments are not preserved

This is the most important limitation. The formatter parses the input and writes a flat list of keys and values. Section headers such as [database] and comment lines beginning with a semicolon or hash are not carried into the output. If your file depends on sections to separate settings with the same name, the flattened result can be misleading or unusable. Keep the original file and do not replace a real configuration with the beautified copy.

Typed values can change

The parser uses typed scanning, which means it may turn a quoted or unquoted numeric value into a number. A value such as 0123 can come back as 123, and a string that looks like true or false may be treated as a boolean. That is fine for a display, but it can break an identifier, a version string or a value that must keep its leading zero. Check every value that looks numeric before you reuse the output.

How to use the page

Select INI as the language. Leave the mode on Beautify for spaced key-value lines, or switch to Minify for a compact form. Paste the configuration into the editor, or use the URL tab to fetch a public file. Press the format button. The output appears in a read-only editor. Use the copy control or download the .ini file. The server accepts up to 200,000 characters, so a large configuration should be split or handled locally.

Unquoted equals signs cause errors

INI parsers treat an equals sign as the separator between a key and a value. If a value contains an unquoted equals sign, such as a URL with a query string or a database connection string, the parser may reject the whole input. Quote the value if your INI dialect allows it, or use a different format for data that contains arbitrary punctuation. This page does not provide a delimiter or quoting option.

Duplicate keys and ordering

If the same key appears more than once, the later value can overwrite the earlier one. The output may also lose the original order or grouping. That makes the result unsuitable for a file where duplicate keys are intentional or where order matters to a reader. A real configuration parser may have its own rules for duplicates; this tool does not expose them.

Beautify versus minify

Beautify is for reading: it puts spaces around the equals sign so the file scans more easily. Minify removes those spaces for a smaller text output. Neither mode validates that the keys are known, that the values are safe or that the file will work in a particular application. Minify is not a compressor and will not make a meaningful difference to a small file.

When this page is useful

Use it to inspect a short, flat INI snippet, to compare a few values or to turn a messy line into a readable key-value list. It can help with documentation examples and quick troubleshooting. It is not a good choice for a production configuration with sections, comments, quoted values or secrets. For those, use the application's own config parser or a dedicated INI editor.

Limits and server processing

The input is sent to the Newisty server for parsing and formatting. The limit is 200,000 characters. URL loading also happens on the server, so a login-protected address will not work. The page does not save the result permanently. If the request is rejected, the input may exceed the limit or contain syntax the parser cannot handle. Split the file or use a local tool.

Privacy and configuration secrets

Configuration files often contain passwords, API keys and connection strings. Do not paste those into a public web page unless you accept that the server receives them. The page does not claim to encrypt or delete the input. For any real secret, use a local editor or a secrets manager. If you only need to check the layout, replace the sensitive values with placeholders first.

Common problems

If the output is empty, the parser may have rejected the syntax. Check for an unquoted equals sign, a stray quote or an unsupported construct. If sections disappeared, that is expected. If a numeric value lost a leading zero, typed scanning changed it. If the download is not valid for your application, do not use it; restore the original and edit it with a tool that understands your dialect.

What not to do

Do not overwrite a real .ini file with the beautified output. Do not assume comments, sections or duplicate keys survive. Do not paste production secrets. Do not use the page to validate a configuration. Do not treat a successful format as proof that the application will start. Do not rely on minify for security or compression.

INI dialects vary

Not every file called INI follows the same rules. Some parsers allow quoted values, some allow inline comments, some treat case differently, and some support arrays or nested sections. This page uses one general parser with typed scanning. It cannot promise compatibility with PHP, Python, Windows, a specific application framework or a custom loader. If the file must actually be read by an application, test it with that application's parser and keep the original. A clean web output is not proof of compatibility.

Before and after: how values are rewritten

The page reads the whole input with PHP's typed INI scanner and then writes each key back on its own line. Seeing one example makes the rules much easier to predict. Take this input:

[app]
enabled = on
debug = no
name = My App
port = 0123
ratio = 1.50
cache = null
path = "/var/www;old"

In Beautify mode the output is:

enabled = true
debug = false
name = "My App"
port = 123
ratio = 1.5
cache = 
path = "/var/www;old"

Several things happened. The [app] header is gone. The words on and yes are read as a boolean and written back as true, while off, no and false become false. The word null becomes an empty value. A decimal loses its trailing zero, so 1.50 turns into 1.5. Any text value that contains a space, a semicolon, a hash or an equals sign is wrapped in double quotes, and a double quote already inside that value is escaped with a backslash. Plain values with none of those characters are written without quotes.

If an application reads on and true the same way, these changes are harmless. If it compares the raw string, they are not. Read every changed line before you copy anything back into a real file.

Array keys, the URL tab and the download name

Keys written with square brackets, such as hosts[] = a, produce a list rather than a single value. The formatter only knows how to write single values, so a file with array keys either fails with an error or comes back with the word Array in place of the values. Remove those lines before formatting, or use a tool that understands INI arrays.

The page opens on the URL Input tab. After a successful fetch the text is placed in the editor and the page switches to Manual Code, where you can review it before pressing Process Code. The Language menu on the same page also offers other formats, but the rules above apply only when INI is selected. The download is saved as beautify-output.ini, or minify-output.ini in Minify mode, so rename it before placing it next to your original.

Frequently Asked Questions