INI Config Example: Valid Application Settings
Check INI text for sections, key=value lines, comments, and duplicate names. It does not look for HTML tags.
🔒 Processed entirely in your browser — nothing you enter here is ever uploaded.
The result appears on this page after you run the tool. Nothing you enter is uploaded.
Result
About this tool
This page opens the INI validator preloaded with a small, realistic configuration file: an [application] section with a version and a debug flag, a [database] section with connection details, and a [logging] section with a level and a file path. The pass result below is computed the instant the page loads, using the same section-and-key parsing as any file you paste in yourself.
This shape — bracketed section headers followed by plain key = value lines, with no key repeated inside the same section — is the classic INI format used by countless legacy Windows applications, PHP's php.ini, and many services that still read simple config files at startup. It's a useful reference for what a clean, unambiguous INI file looks like before you paste in your own.
Replace the text in the box with your own configuration to validate it the same way. If a section name is left empty, a line is missing its = separator, or a key is repeated twice inside the same section, the validator reports the exact line — the same class of mistake demonstrated on the duplicate-key-error preset page.
Example. [app]\nname = demo passes. A second [app] fails with Duplicate INI section found. Inside one section, debug = 0 followed by debug = 1 fails on the second line with Duplicate key "debug".
Limit. Comments are only whole lines that start with # or ;. Values are not typed, continuations are not joined, and the checker does not look for HTML tags.