Validate XML against XSD online
Drop an XML file and validate it against its XML Schema. When the document names its schema in
xsi:schemaLocation or xsi:noNamespaceSchemaLocation, the schema and everything
it imports is fetched and applied automatically; otherwise add an .xsd or a ZIP of schema
files. Every error is pinned to the node that caused it.
Export all errors to an Excel report — line, XML path, message and the surrounding lines — and hand it to whoever produces the file. Common errors are explained in XML validation errors explained. Browse the document as a collapsible tree or diagram, search it, and validate FundsXML and ISO 20022 files against their official schemas.
Sister tools by the same author: Online XSD Viewer, Online OData Viewer and Fund Data Converter.
Guides: validation errors to Excel, XRechnung and UBL, all guides and resources.
How do I validate an XML file against an XSD online?
Drop the XML file here. If it names its schema in xsi:schemaLocation or xsi:noNamespaceSchemaLocation, the
schema and everything it imports is fetched and applied automatically; otherwise add the .xsd (or a .zip with
all schema files) in the schema panel. Validation runs immediately and every error is pinned to its node.
Can I export the validation errors?
Yes, as an Excel workbook: one row per error with severity, line, column, XML path, message, the line before, the error line and the line after, and a link to an explanation of the error. See Excel error report.
Are my files stored?
No. Files are parsed in memory and dropped from a short-lived cache; nothing is written to disk and document content never reaches the usage statistics. To keep files inside your network, run the viewer with Docker.
What does an error like cvc-complex-type.2.4.a mean?
Each common validation error has a page with the libxml2 and Xerces wording, typical causes, an example and the fix: XML validation errors explained.
Does it check Schematron or business rules?
No — it validates against XML Schema (XSD 1.0): structure, data types, lengths, patterns and code lists. Rules defined in Schematron (for example XRechnung) or in bank implementation guides need a separate validator.