OpenAPI Validator
Check a local Swagger 2.0, OpenAPI 3.0 or OpenAPI 3.1 document for schema errors and broken internal references. Read the reported paths without querying your API.
Open toolCompare two XML documents by parsed structure. Read changed paths while ignoring attribute order and whitespace used only for indentation.
Enter the inputs, then select Compare XML.
Result will appear here
Compare parsed XML trees, ignoring attribute order and whitespace-only text between elements.
Processing uses bundled libraries in this browser. The result table shows the supported checks; it does not query another service.
Start with the supported input, then check the generated result.
Use Original XML, Updated XML. The form starts with an example you can replace.
Read each reported path or recorded value. A clean table only covers the checks described on this page.
These workflows use the formats and behavior supported by this implementation.
Attribute order is ignored, but a changed attribute value is reported with a path and before/after text.

Changes in meaningful text and child order remain significant. Use the path table to locate the affected part of the documents.

Whitespace-only text between elements is ignored. Namespace prefixes are still compared as written, so this is not full XML semantic equivalence.

Keep the output format and conversion policy in view.
Changed XML paths and values. Compare parsed XML trees, ignoring attribute order and whitespace-only text between elements.
Compare the result with the original before replacing a source file. Conversion limits are listed below.

Check these conditions before relying on the result.
Child order and meaningful text remain significant. Namespace prefixes are compared as written. Up to 1,000 displayed differences. DTDs and entity declarations are rejected.
Input and results are not stored after leaving or reloading. Keep the original and download any output you need.

Check a local Swagger 2.0, OpenAPI 3.0 or OpenAPI 3.1 document for schema errors and broken internal references. Read the reported paths without querying your API.
Open toolGenerate plain Java model classes from a JSON object or object array. Download a ZIP with separate class files, then review inferred types and add your serializer mapping.
Open toolConvert a supported WOFF font to a TrueType container while keeping its table content. Use a font you have permission to convert and review the downloaded TTF.
Open toolChoose another tool for your next calculation, conversion, or text task.
Inspect quoted CSV cells in a readable table without uploading your data.
Open toolCheck CSV quoting and consistent column counts, then review the record count and selected delimiter.
Open toolCompare two JSON values by structure. See changed paths without treating object key order as a difference.
Open toolValidate JSON against a draft-07 or 2020-12 schema. Review error paths without sending the documents to a server.
Open toolRead the reported paths and values after processing your input.
Answers about using XML Diff Checker and understanding its results.
It produces changed XML paths and values. Child order and meaningful text remain significant. Namespace prefixes are compared as written. Up to 1,000 displayed differences. DTDs and entity declarations are rejected.
Processing runs in this browser with local bundled libraries. No input is sent to a conversion server. Download your result before leaving the page.