Compare configuration files: review values, whitespace and secrets
Compare configuration text before applying a change. Paste the old version on the left and the new version on the right to see changed values and lines. This is a text review, not a configuration validator.
CompareText · Updated
Input and output example
PORT=3000 FEATURE_SEARCH=false APP_ENV=production
PORT=8080 FEATURE_SEARCH=true APP_ENV=production
Use a safe working copy
Remove passwords, tokens and private endpoints from a working copy before sharing it with another person. CompareText processes text in the browser tab, but copied results, screenshots and browser extensions are separate from the tool. The example uses invented values.
Review the two changed settings
In the example, PORT changes from 3000 to 8080 and FEATURE_SEARCH changes from false to true. APP_ENV stays the same. Expect two added lines and two removed lines; check both the new port and whether enabling search is intended.
Keep indentation meaningful
Leave ignore-whitespace off for indentation-sensitive formats such as YAML. The option ignores leading and trailing whitespace when matching lines; it does not understand YAML nesting. An apparently identical comparison with that option enabled is not proof that the files behave the same.
Separate formatting from values
For valid JSON, format each version with the JSON tool before comparing if indentation obscures the changes. Formatting does not sort keys or perform semantic comparison. Reordered properties can still appear as text differences; array order and values must be reviewed.
Validate before deploying
Run the application's own configuration checks and tests after reviewing the diff. Text comparison cannot detect every invalid setting or predict runtime behavior. Import supports UTF-8 .txt up to 1 MB and 20,000 lines per input; other configuration files can be pasted as plain text.