Configuration review
Compare YAML 1.2 streams by structure or inspect their original text.
Both inputs are processed in this browser; no content is uploaded.
For example ["/0/metadata/time"]. /0 is the first document; /0/ targets its empty key. Use ~0 for ~ and ~1 for /. Exclusions remove subtrees from structural counts and reports; array indices never shift. Text mode remains unfiltered.
YAML 1.2 core + explicit timestamp/binary. Mapping order is ignored; documents and arrays match by index. Integer and float types differ. Timestamps compare original spelling, not instants.
Each side: 200,000 characters / 800,000 UTF-8 bytes; 100 documents, 50,000 expanded nodes, depth 100, 5,000 anchor/alias reference rows. Up to 5,000 changes, 1 million cumulative path characters and 4 million report characters. Worker: 5 seconds. Text: 500 ms, 2,000 edit distance, 50,000 tokens.
Enter configurations or run a comparison.
YAML diff helps when a deployment review mixes a changed replica count with reordered keys. The structural view matches names and retains value types; the text view shows what actually changed in the file.
Use YAML compare to compare YAML files before rollout. This semantic YAML diff pairs every document by its position, so a multi-document stream never silently becomes a comparison of only its first document.
Two views answer different review questions
YAML diff keeps a stream as an ordered set of documents. Matching keys ignore their written order, while a removed document or a typed value change remains visible. Reordering documents is deliberately meaningful.
A changed comment can matter to a maintainer without changing configuration data. Switch to original text to see comments, spacing and line endings; this view does not inherit structural path exclusions.
Pairing, scope and freshness determine what an export says
The first document on each side pairs with the first, then the second with the second. Paths begin /0, /1 and so on. A new document in the middle shifts later pairings; Kubernetes names do not trigger automatic realignment.
Enter a JSON string array such as ["/0/metadata/time"]. Each pointer excludes that node and its descendants. Escape slash as ~1 and tilde as ~0; JSON escapes let a path contain a newline. /0/ identifies an empty key, while /0 excludes the entire first document.
Structure exports typed JSON changes after exclusions. Original text exports unfiltered line blocks, including unchanged source. Editing immediately disables stale exports. Automatic comparison waits 350 ms; manual mode supports Ctrl/Cmd+Enter. Replacement previews offer one Undo.
Names, positions and scalar types retain their roles
All documents participate, including explicit empty documents. Added or removed whole documents have their own marker. Arrays pair by index; an insertion may change several following entries instead of being guessed as a move.
Integers use arbitrary-size digits within the token budget. Finite decimal floats use exact coefficient/exponent equality: 1.0 equals 1e0 but differs from integer 1. Float negative zero differs from positive zero; NaN equals NaN for this review.
Excluded subtrees are removed from both structural inputs before comparison, including an added container or a container replaced by a scalar. Reports retain original array indices. Counts describe the remaining changes, not the hidden values.
Scalar values remain strings with an explicit type, preserving large integer digits and nonfinite floats. Container entries carry keys or original indices. Screen, clipboard and download use the same current report; the report is descriptive and cannot be applied as a patch.
Read these before treating two configurations as equivalent
Common configuration-review situations
YAML diff compares parsed mapping keys and typed values. Reordering keys or switching block and flow presentation does not change that structure. Open Original text when the written form itself needs review.
List items are compared by their original zero-based index. Adding an item at the start may change later positions. Excluding an item preserves those indices rather than compacting the list.
Yes. Every document is paired by index, up to 100 per side. A missing trailing document is added or removed as a document. This page does not silently select only the first document.
Yes if the rendered output fits this YAML subset. Render the template before pasting it. Resources pair by document position, not kind, namespace or metadata.name, so align their order for an intentional review.
Structural comparison ignores comments. Original text compares the exact source and shows comment edits alongside key order, whitespace and line-ending changes. Structural path filters do not apply to that text report.
Have a YAML review case we missed?
Use YAML diff to check typed configuration changes, then inspect original text before selecting the report to share.
Original-text reports remain unfiltered.