Place the earlier YAML document on the left and the revised document on the right. In the example below, replicas changes from two to three while name stays demo. Read the reported path and the old and new values together. Comparison parses both inputs, so comments, indentation choices and mapping key order do not become data differences by themselves.
Correct a parser error on either side before interpreting the comparison. If you ignore case, repeat the final review with that option disabled whenever capitalization matters to the consuming program. Keep the original files for a separate text comparison when comments or presentation need review. This workflow compares two parsed values; it does not load a common ancestor or resolve a repository merge automatically.
Keep source files available when interpreting the report, particularly where sequence positions account for several apparently related modifications.
name: demo
replicas: 2
β
name: demo
replicas: 3
It compares the values produced by parsing each document and reports additions, removals and modifications at data paths. A changed number and a changed string may have different meanings even when their displayed text looks similar. Inspect both the path and value rather than relying only on a summary count.
Nested values are compared recursively. Sequence positions matter, so moving a list entry may appear as several changed positions rather than a single move operation. An ordered sequence and an unordered mapping need different interpretation. Review the relevant section of each original document when the reported paths look unexpectedly extensive.
Each side must parse as one YAML document. A parsing failure clears results and identifies the failing side. Split document bundles first. Render templates or adapt unsupported custom tags before comparing. Successful parsing does not prove that a Kubernetes manifest or another configuration meets its application schema; validate those rules separately.
Each upload allows 100 MiB, and both parsed documents must fit in browser memory. Processing time is not guaranteed. This is not a three-way merge, monitoring service, automatic conflict resolver, or command-line endpoint. For unwieldy configurations, compare representative sections while retaining enough surrounding structure to interpret each reported path and change.
Processing runs in your browser. Choosing Share uploads the selected tool state; anyone with the link can open it. Signing in to save sends content to your account library and records save history. Review the selection before either action. Closing the page does not delete those copies. Copying locally does not create a server share.
Array order is significant. Ignoring it is not supported.