JSON to YAML
Convert JSON to clean, correctly quoted YAML in one step.
Check XML is well-formed and find the exact tag that breaks it.
The XML Validator checks a document is well-formed and, when it is not, names the line and the tag responsible. A document that passes is measured instead: elements, attributes, depth and text nodes.
Well-formedness is the bar every XML document has to clear before anything else can read it: one root element, every tag closed, tags nested in the right order, attribute values quoted, and the five reserved characters escaped.
The validator checks all of that and, when something fails, names the line and the tag rather than reporting a generic parse error. A closing tag that does not match the open one, a tag that is never closed, a second root element, an unterminated comment or CDATA section — each gets its own message. A valid document is measured instead: element count, attribute count, nesting depth and the number of text nodes.
A mismatched closing tag names both the tag found and the one still open, which is the pair you need to see.
Two elements at the top level is one of the commonest rejections, and it is reported as exactly that rather than as a parse error.
A comment or CDATA block that is never closed is reported by line instead of swallowing the rest of the document silently.
Element and attribute counts, nesting depth and text nodes confirm the document is the shape you expected.
Well-formedness is checked entirely in your browser, with no schema URL fetched and no document uploaded.
Any document you believe should parse — a feed, a config, an export.
Green means well-formed. Red names the line and the tag that caused the failure.
The verdict updates as you type, so a fix is confirmed immediately.
Element and attribute counts and the nesting depth confirm the document is the shape you expected.
Well-formed means the syntax is correct. Valid means it also conforms to a DTD or XSD schema. This tool checks well-formedness, which is the failure people actually hit.
No. Exactly one element must contain everything else. Two siblings at the top level is one of the most common reasons a document is rejected.
An ampersand must be written & and a less-than sign <. Greater-than, quote and apostrophe have entities too but are only required in specific positions.
No — that would mean fetching the schema from a URL, which this site never does. Well-formedness is checked entirely in your browser.
What people who use the XML Validator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the XML Validator. It takes half a minute and no account.
Write the first reviewConvert JSON to clean, correctly quoted YAML in one step.
Generate Java POJOs or records with Jackson annotations from JSON.
Convert an INI or config file into structured JSON, sections and all.
Check a JWT signature against a secret or a public key, and see why it fails.
Convert a TOML config to JSON, with tables and arrays of tables resolved.
Turn a .env file into JSON, with quotes, exports and comments handled.
Turn any text into a JSON string literal, or unwrap one back to plain text.
Convert an IPv4 address into every IPv6 form that carries it, and back.