DevToolsmith

Config Diff

Compare two configurations by their parsed structure. Find changed fields, added values and type differences without noise from key order or indentation.

Runs 100% in your browser — nothing is uploaded

Compares parsed values and types. Comments and key order are ignored; arrays are compared by position. Environment values stay strings, and interpolation is not evaluated.

Original configuration
Tip: drop a file here58 chars · 58 bytes · 6 lines
Updated configuration
Tip: drop a file here82 chars · 82 bytes · 7 lines

3 structural differences

Structural difference report
111 chars · 111 bytes · 11 lines

Compare two deployment configurations

Choose each input format independently. For example, compare YAML debug: false with JSON containing "debug": "false" to see a type change, or check a port change without differences caused by indentation.

Understand format boundaries

YAML and TOML parsing preserves supported integer precision and rejects numeric values that would silently change. TOML dates are represented as strings in the comparison. This is a value comparison, not validation against your application’s schema.

Example: boolean versus string

Choose YAML on the left and JSON on the right, then paste these configurations. Reordering the keys creates no change, but quoting the boolean and changing the port do:

Left: YAML
debug: false
port: 8080
Right: JSON
{"port":8081,"debug":"false"}
PathChangeBeforeAfter
$.debugtypefalse"false"
$.portchanged80808081

Choose structural or source comparison

Use Text Diff to review changed comments or whitespace, and JSON Diff for two JSON documents. Config Diff can compare different supported formats, but an environment file’s values remain strings: PORT=8080 is not automatically the JSON number 8080.

For deployment review, follow this comparison with Compose Validator when the target is Docker Compose. Structural similarity alone does not prove a service will accept a configuration or that its environment interpolation has been resolved.

Documentation examples checked: . How these tools are checked.

Frequently asked questions

Are comments and array order compared?

Comments, formatting and mapping key order are ignored. Arrays are compared by position. Use Text Diff when the exact source, comments or whitespace matter.

Are environment variables or includes resolved?

No. Environment values remain strings, and interpolation is not evaluated. Duplicate or malformed .env entries are reported rather than silently skipped. Compare the final resolved configuration separately when your service merges or expands values.

Sources

Spotted a mistake? Email hello@devtoolsmith.com and we’ll fix it.