INI Validator
Validate literal or ConfigParser-style raw INI. Get physical line and column positions, including the first definition of a duplicate key or section.
Trace Duplicate INI Entries to Their Source
Case-sensitive keys, optional global assignments and one value per physical line. Quotes and interpolation stay literal.
INI Validator: how to use it
- Open a local UTF-8 INI file or paste the text and select the dialect used by the consumer.
- Choose Validate INI. Follow the reported positions and compare both definitions of a duplicate.
- Fix the source and validate again. Download the JSON diagnostics for positions and counts.
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. Shows up to 100 diagnostics. Checks syntax without resolving interpolation or applying an application schema.
How your privacy works →INI Validator: common questions
Why are Code and code separate in one mode and duplicates in the other?
Literal INI preserves case in key comparisons. ConfigParser-style raw INI folds option names to lowercase within each section.
Does the diagnostics file contain key names or values?
It includes the selected dialect, counts, positions, general error messages and first-definition positions. The actual key names and values stay out of the report.
Can a valid file still fail in my application?
Yes. A consumer may require specific fields, value types, interpolation or a different INI dialect. This check uses the rules of the selected dialect.