Code · Made a little simpler

INI Compressor

Remove unnecessary separator spacing and blank lines in supported INI. Keep full-line comments when needed and preserve the contents of ConfigParser-style multiline values.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Section headers required, case-insensitive keys and indented continuation lines. Quotes and interpolation stay literal.

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

INI Compressor: how to use it

  1. Open a UTF-8 INI file or paste the source. Choose its dialect.
  2. Choose whether to keep full-line comments and select Compress INI. Compare source and output byte counts.
  3. Review the compact result and download the INI. Verify settings in the application that reads it.

Limits and notes

Accepts UTF-8 files or pasted text up to 250,000 UTF-16 code units. Literal INI allows global keys and compares names by exact spelling. ConfigParser-style raw INI requires sections, compares keys case insensitively and supports indentation continuations. Quotes and interpolation stay literal in both. This produces plain INI text. Surviving lines retain their separators and a leading UTF-8 BOM is preserved.

How your privacy works →

INI Compressor: common questions

Why did a blank line stay in the compressed file?

A blank line between parts of a ConfigParser-style multiline value can contribute a newline to that value. Compression keeps it.

Can I keep my full-line comments?

Select Keep full-line comments. Text after a separator remains part of the value, including any inline semicolon or hash.

Will the compressor change 0012 or resolve %(key)s?

Those strings keep their spelling. Compression only changes supported layout and optional comments.

Guides