Config File Diff compares two configuration files at the key level instead of the line level, so you only see meaningful changes. Reordering keys, adding blank lines, or changing quoting style produces no noise. Paste an old and new .env, .ini, or .toml file and instantly see which keys were added, removed, or had their values changed — perfect for reviewing deployment configuration drift between environments.
How it works
Each file is parsed into a flat map of fully-qualified keys. For ENV files, every KEY=value line becomes one entry. For INI and TOML, a section header like [database] namespaces the keys beneath it, so host = localhost is stored as database.host. Before comparing, the parser strips inline comments (text after # or ;), trims whitespace, and removes a single matching pair of surrounding quotes from values.
The two maps are then compared by key:
- Added — keys present only in the new file.
- Removed — keys present only in the old file.
- Changed — keys in both whose values differ, shown with old → new.
- Unchanged keys are counted but not listed, to keep the output focused.
Tips and notes
Pick the format that matches your files so sections are interpreted correctly — using ENV mode on an INI file will treat the [section] line as a malformed entry. Because comparison is value-based after normalisation, DEBUG=true and DEBUG = "true" are equal. Everything runs locally, which matters because config files frequently contain API keys and database passwords.