Compare config files online for environment drift, releases, and setup review
Small configuration changes can break a build, a deployment, an integration, or production behavior. Compare the previous and new file before release, then choose Text Diff for raw config or JSON Diff for structured files.
Start with the input you already have
Which tool should you use for config review?
Use Text Diff when the source files are plain text, environment files, YAML, SQL, or mixed configuration snippets. Use JSON Diff when the source of truth is JSON, such as package manifests, exported settings, and machine-readable config bundles.
The same release can contain both raw configuration and JSON manifests. Use the format of the source file to decide the comparison mode.
Where teams use this workflow
Compare `.env` files between staging and production, review package.json after dependency updates, inspect CI/CD config changes, or validate deployment flags before shipping. These tasks are high-risk and benefit from a fast, private browser workflow.
If the input is broken JSON, repair it first. If the source is a rendered document instead of a config file, switch to PDF Diff.