Config File Comparator — Diff Tool
Compare two configuration files (JSON, YAML-like, TOML-like, INI) and show differences.
How it works
- 1Paste or type your text in the input field
- 2Click "Compare" — processing happens in your browser
- 3Copy the result or download as a text file
What to do next
About Config File Comparator
Config File Comparator is a free, in-browser developer tool. Compare two configuration files (JSON, YAML-like, TOML-like, INI) and show differences. The page exposes a small surface — input, controls, output — so a first-time visitor can complete the job without reading documentation.
Config File Comparator runs on standard browser APIs — an open-source, well-audited engine that performs the developer utility natively in the browser. It accepts the formats listed in the upload area and produces output that opens in any standard developer viewer. Per-run input is capped at 0 MB.
Config File Comparator works well as a bookmarked utility you reach for when you need it. The first visit shows you what the tool does; the second is when you realise it is a low-friction option for the task and worth keeping in your tab list.
Because everything runs in the page, the tool scales the same way for one user or a million — there is no per-user backend cost. The page is static, the engine is the same JavaScript bundle for every visitor, and the work happens on the visitor's own device. That keeps the tool free and keeps it fast on the first interaction.
The only practical limit is the 0 MB per-file ceiling, which keeps the tool responsive across a wide range of devices. Run the tool ten times in a row, run it ten thousand times — it behaves the same way and produces the same quality of result.
Even on its own, Config File Comparator composes well with the rest of your toolkit. The output is a standard developer file that opens in any program that handles the format, so the result of one run can become the input to whatever step you use next.
Common audiences for Config File Comparator include students learning new languages and engineers debugging API payloads, but plenty of people land on the page through a one-off search and never come back — that is also fine. The tool is built to be useful even when you only ever need it once.
Once the engine finishes, the output is offered as an immediate download. There is no preview gate, no email-wall, and no "register to download" intermediary — the file is yours the moment it is ready.
The transformation in Config File Comparator is deterministic — the same input plus the same options produces the same result every run. That predictability matters when the result has to match an upstream specification or be reproducible later.
From a product perspective, Config File Comparator is one of the simplest possible expressions of "do one thing well." The catalog contains dozens of related tools that each handle a slightly different developer utility task, and every one is a separate page rather than a tab inside a larger app. That separation keeps each tool fast to load and easy to bookmark.
A few practical tips that experienced users of Config File Comparator pick up over time. First, keep your default browser updated — the engine relies on standard web APIs and newer browser versions are noticeably faster than ones from a few years ago. Second, close other heavy tabs before processing a large input; the engine shares CPU and memory with whatever else is open. Third, if you re-run the same kind of job often, your last-used settings are remembered for the rest of the tab session, so subsequent runs are essentially one click.
Config File Comparator runs as a regular web page, so there is no install step or permission grant before the first run. The page can be audited by viewing the source or by watching the developer-tools Network tab while a job runs.
If Config File Comparator appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 0 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
That is essentially everything Config File Comparator does and how it does it. Open the tool above, drop in your input, and the work happens in the page. If you find yourself reaching for it often, bookmark the page — it loads quickly on subsequent visits, and your most-recent settings are remembered for the rest of the session.
How it works
- 1Land on the Config File Comparator page. The tool is ready to use the moment the page renders.
- 2Drop a developer file onto the upload area, or click to pick one from your device.
- 3Pick any non-default settings you need. Most users leave the defaults alone for the first run and only revisit if the result needs tuning.
- 4Trigger processing. standard browser APIs reads your input, applies the transformation, and writes the result back into the page.
- 5Download the result. The file is generated in your browser and saved through your normal download flow.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Validate a config blob before pushing to staging using Config File Comparator.
- Compare two API responses to spot a regression.
- Inspect a regex against a test string before committing it.
- Pretty-print a minified blob during incident triage.
- Decode a token to confirm its claims during a debugging session.
- Encode binary content for transport in a JSON body.
- Convert between data formats while wiring up an integration.
- Generate a quick fixture without leaving the browser.
FAQ
What formats?
JSON and key=value (INI-style) configs. YAML comparison uses line-by-line diff.
What differences are shown?
Added keys, removed keys, and changed values with old → new comparison.
Nested JSON?
Deeply nested JSON objects are flattened with dot notation for comparison.
Ordering differences?
Key order differences are ignored — only value changes are reported.
Large files?
Works well for files up to several hundred KB. Very large files may be slow.
Private?
Yes — comparison runs locally.
Can I trust the output of Config File Comparator for important work?
Config File Comparator is built on standard browser APIs, which is the same class of engine used by professional developer utility pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Are there any restrictions on using Config File Comparator at work?
Config File Comparator can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
What does the error message in Config File Comparator mean?
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is in a supported format and that it is below 0 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Do I need to install anything to use Config File Comparator?
No installation is needed. Config File Comparator runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Config File Comparator on any computer you have temporary access to without leaving anything installed on it.
Why does Config File Comparator feel slow on large inputs?
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 0 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
How accessible is the Config File Comparator interface?
Config File Comparator uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.
Will Config File Comparator keep working if my Wi-Fi drops mid-task?
Once the page is loaded, Config File Comparator can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
Does Config File Comparator support batch processing?
Config File Comparator processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.