Why structural comparison matters
Two JSON documents can look different as text while still representing nearly the same structure. Structural comparison reduces the noise from line wrapping, indentation, and layout differences.
Treease keeps the source document and the right-side comparison text in one editor route, which makes it suitable for support docs, migration guides, and comparison landing pages.
A prepared compare link
Inline compare example
Opens both sides and runs compare in the prepared session.
/editor?text={"service":{"port":8080}}&rightText={"service":{"port":9090}}&command=compare
Remote baseline compare
Loads two hosted documents into the comparison workflow.
/editor?textUrl=https://raw.githubusercontent.com/loggerhead/treease-testdata/refs/heads/main/json/complex.1.json&rightTextUrl=https://raw.githubusercontent.com/loggerhead/treease-testdata/refs/heads/main/json/complex.1.json&command=compare
When to use this article
- For “compare JSON online” landing pages.
- For migration guides that show a before-and-after payload.
- For docs that want to explain Treease compare parameters without explaining internal precedence details.