JSON Compare
Compare JSON documents by structure, values, and selected array rules.
Open toolPrivate browser-based YAML comparison
Compare two YAML documents using semantic or text-based comparison. Find changed keys, values, types, sequences, and formatting without uploading your configuration files.
Original configuration
Paste YAML or choose a local file to validate it.
Changed configuration
Paste YAML or choose a local file to validate it.
Comparison results
Ready to compare.
A semantic match means parsed YAML values match under the selected rules. It does not confirm a configuration is valid for Kubernetes, Docker Compose, GitHub Actions, or another product.
Semantic YAML comparison reads mappings, sequences, scalars, and document boundaries instead of treating every space as a change. It reports paths such as $.services.api.image, preserves the difference between a missing key and null, and keeps scalar types significant: "1" is not numeric 1.
Use Semantic YAML when you need configuration meaning. Mapping order, comments, indentation, quote style, anchor names, and block versus flow style are presentation details. Use Text and formatting mode when reviewing comments, exact key order, indentation, quoting, anchors, aliases, or an ordinary source diff.
YAML mappings are key-based, so their written order is normally not meaningful. Sequences are ordered by default because moving an item can change configuration behavior. Choose Ignore sequence order only for collection-like data, or match mapping items by a reviewed identity key such as name or metadata.name.
Compare Kubernetes manifests as a multi-document stream by position or, when identities are complete and unique, by API version, kind, namespace, and name. The same local workflow helps review Docker Compose files and CI/CD configuration. Valid YAML alone does not prove that a platform-specific configuration will work.
Anchors and aliases are resolved with a strict local expansion limit before semantic comparison. Text mode keeps their original spelling visible. YAML streams are kept as separate documents; they are never flattened into one object.
Credentials and Kubernetes Secret-style fields can appear in configuration. Sensitive-looking paths are masked in results and exports by default, and Reveal affects only the current on-screen session. Base64-encoded values are not encrypted, so handle credentials carefully even when comparison stays local.
This tool does not fetch URLs, validate product-specific schemas, run templates, execute tags, or test runtime behavior. It limits input size, alias expansion, nesting, and node count to keep a browser comparison responsive. Use repository review and platform validation for production changes.
Paste two YAML documents or choose local .yaml or .yml files, select Semantic YAML or Text and formatting mode, then choose Compare YAML. Processing stays in this browser.
No. This page reads pasted text and selected local files only in the current browser session. It does not upload, store, or put YAML into a shareable URL.
Semantic comparison parses YAML values, ignores mapping order and formatting noise, and reports meaningful paths, values, container changes, and scalar type changes.
Mapping key order is normally presentation only, so semantic mode ignores it. Text and formatting mode shows key-order changes exactly as written.
Yes by default. YAML sequences are compared in order. You can explicitly ignore order for multiset-style lists or match mapping items by an identity key.
Yes. The tool supports multi-document YAML streams and can match Kubernetes documents by apiVersion, kind, namespace, and name when those identities are complete and unique.
The parser resolves aliases with a strict expansion limit. Semantic mode compares the resolved values, while text mode shows anchor and alias spelling changes.
Text and formatting mode can still compare it. Semantic comparison stops and shows the parser error, line, and column so your input is not silently treated as valid.
No. This tool checks YAML structure, not product-specific schemas, Kubernetes admission rules, Docker Compose behavior, GitHub Actions syntax, or runtime safety.
The tool masks sensitive-looking values in results and exports by default, but local comparison is not a substitute for your organisation’s credential-handling policy. Base64 encoding is not encryption.
Compare JSON documents by structure, values, and selected array rules.
Open toolCompare XML source or semantic structure without uploading a file.
Open toolReview prose, code, and configuration revisions as text.
Open toolChoose two local plain-text files for a line-by-line diff.
Open toolInspect URL paths and parameters locally.
Open toolExplore the full browser-based tool library.
Open tool