Validrelay
TR
Sign Up
Free tool

EUDAMED XML Validator

Check your DTX XML against the official EUDAMED XSD before you submit it. See every error with its line, column and a plain-language explanation.

Your XML is not stored. Your file is processed only to validate it and is never written to disk, a database or logs. The usage record holds no file content, only the result, the number of errors per category, the schema version and the duration. A keyed digest of your IP address that changes every day (not the address itself) is kept for 30 days to prevent abuse and, only in aggregate, to count daily unique users, and is then deleted. No account required.

As of 12 October 2026, the live EUDAMED environment uses 3.0.30; the test (Playground) environment uses 3.0.32. Sources

How it works

  1. 1

    Upload your EUDAMED DTX XML file or paste its content.

  2. 2

    Choose the XSD version of the target environment: Production 3.0.30 for live, Playground 3.0.32 for testing (as of 12 October 2026).

  3. 3

    The XML is validated against the official XSD package published in the EUDAMED Information Centre, and every error is listed with its line, column and an explanation.

Frequently asked questions

Which XSD versions does it validate against?
As of 12 October 2026, the official DTX XSD packages published on the EUDAMED Information Centre technical documentation pages: Production 3.0.30 and Playground 3.0.32. Choose the version of the EUDAMED environment you will submit to; the source links are below.
Is my XML file stored?
No. The file is processed in memory only for the duration of the validation and is never written to disk, a database or logs. The usage record holds no file content, only the result (valid/invalid), how often each error category occurred, the schema version and the duration. The daily-changing keyed IP digest added to the record is used only to prevent abuse and, in aggregate, to count daily unique users; it is not assessed per person and is deleted after 30 days.
Which messages can I validate?
Every message defined in Message.xsd: Push, PullRequest, PullResponse and Acknowledgement. All DTX entities, such as devices (Basic UDI-DI, UDI-DI), actors and certificates, are checked with the schema. A fragment of the data model on its own (e.g. a bare device:Device) is not a message and is reported as “Not a EUDAMED message”.
Are there usage limits?
Up to 5 MB per file; 10 validations per minute and 200 per day. No account required.
Will an XML that passes the schema be accepted by EUDAMED?
Schema conformance is the first step. When you submit, EUDAMED also checks business rules (e.g. UDI-DI uniqueness, actor permissions, certificate links). Validrelay automates both steps.

XSD versions and sources

As of 12 October 2026, according to the EUDAMED Information Centre technical documentation pages:

EUDAMED updates the DTX schema with its platform releases (usually Playground first). Check the version on the source page before you submit; this tool is updated when a new XSD package is published.

Catch these errors automatically before you submit

Validrelay generates your EUDAMED XML from your ERP data, validates it against the same schema before every submission and sends it to EUDAMED directly.

Try it free