Developer
Breaking Change Detector
Compare two JSON shapes and surface removals or type shifts that could break consumers, contracts, or fixtures.
Previous shapeBaseline JSON
Next shapeCandidate JSON
Review before release
Type changed from number to string.
Removed string path.
Removed boolean path.
Compatible additionsNew paths only
Added new string path.
Contract review
This is meant for quick compatibility reviews of payload samples, configuration objects, or API responses. Added fields are listed separately from actual break risks.
Use this tool when
These are the practical situations where this workflow usually earns its keep.
You need to spot change patterns that may break downstream consumers.
You want a browser-local pass before using the findings to drive compatibility discussion before shipping.
You need a smaller, cleaner review surface during release review and API evolution.
Daily workflow acceleration
Breaking Change Detector helps when teams need to spot change patterns that may break downstream consumers without opening a heavier system or rebuilding the same transformation manually every time.
Review and handoff clarity
A focused output is useful when the next step is using the findings to drive compatibility discussion before shipping and the current raw input would otherwise slow down the reviewer or teammate.
Lower-friction local handling
For release review and API evolution, keeping the task in the browser is helpful because the source material often does not need to leave the user’s machine just to answer this one question.
Common mistakes to avoid
These are the checks that usually keep the output useful instead of misleading.
Heuristics can highlight risk, but only domain context can confirm whether the change is truly breaking.
Treating every textual difference as equally important instead of focusing on the ones that change behavior or meaning.
Comparing already-summarized versions instead of the source material when the change is high risk.
Learn how to use this tool
Compare two JSON shapes to surface removed fields and type shifts that may break consumers. This guide focuses on how teams use it for release review and API evolution when the real job is to spot change patterns that may break downstream consumers.
Read the guideTell us what is missing
If this flow helped only partly, leave feedback so we can understand the missing step or edge case.
Leave feedbackRequest the next tool
Use the wishlist to suggest the next utility, workflow, or improvement that would complete this job to be done.
Open wishlistRelated tools
These tools often appear right before or right after this workflow.
Text Diff Checker
Compare two text blocks line by line to inspect additions and removals privately.
Open toolJSON Value Comparator
Compare two JSON payloads by path to review added, removed, and changed values.
Open toolBOM Diff Checker
Compare two BOM exports locally to find added, removed, and changed parts faster.
Open tool