IEC 62474 Checker
Drop an IEC 62474 material declaration and check it against the XML schema and the Developers' Table, or fill in an Excel template and get the XML. Compare two versions of your substance list. Nothing is uploaded.
Check an IEC 62474 material declaration in your browser, against the XML schema and the Developers' Table (X8.21). Drop the XML and get plain-language, field-level findings, or fill in an Excel template and get the XML. Add your own Declarable Substance List to check entry IDs, names and application text. Nothing is uploaded; your files are processed on your device.
Frequently asked questions
What does this tool check?
The structure of the file against the IEC 62474 XML schema X8.21, and the conditional rules in the Developers' Table that a schema cannot state, such as Mass or MassPercent but not both. With a Declarable Substance List you supply, it also checks entry IDs, names and the exact reportable application text.
Does a pass mean my file conforms to IEC 62474?
No. It means the file passed these checks. Conformity also depends on the declaration requirements in Clause 4 of the standard, which this tool does not check. The page lists what ran and what did not on every result.
Why do I have to bring my own substance list?
The IEC 62474 database is IEC's, under its copyright and database rights, so this tool ships none of it. You download the list from the IEC database, drop it here, and it stays in your browser. Nothing is stored or sent.
Can I work in Excel instead of XML?
Yes. Download the template, fill it in, and drop it back to get the XML. A conforming declaration is XML, so the Excel file is your working copy and the XML is what you send. An existing XML file also exports to the same template.
Does anything get lost when I export to Excel?
Some fields have no column, such as attachments, circularity data and SCIP detail. The page names exactly what was left out for your file, so you can decide before you rely on the export.
Are my files uploaded?
No. Everything runs on your own device via WebAssembly: enforced by a strict content-security policy, not just a promise.