UD Validator
Upload any .uds file to verify its structure and metadata.
Drop a .uds file here
or click to browse
How UD Validator differs from PDF validators and JSON schema checkers
PDF validators check rendering compliance. JSON validators check syntax. UD Validator checks the semantic layer: is this document structurally sound, has it expired, has it been tampered with, and are its signatures intact?
PDF/A validator tools — format compliance only
PDF validators like veraPDF check whether a file conforms to PDF/A archival standards. They confirm the file renders correctly but say nothing about whether the document content is structurally intact, expired, or tamper-evident.
JSON Schema validator — syntax without semantics
JSON validators confirm that a file matches a declared schema shape. They check types and required fields but cannot verify whether a document has passed its expiry date, whether embedded signatures are cryptographically valid, or whether content has been altered post-signing.
UD Validator — semantic document integrity
UD Validator checks structure (required fields, correct section types), expiry (is this document still valid today?), signature presence (is a .udsig companion referenced?), and schema version compatibility — all in one pass, in your browser.
UD Validator — no upload, no server, no data exposure
Validation runs entirely in your browser using JavaScript. The document never leaves your device. There is no server, no log, no account. This matters for legal documents, clinical records, and confidential contracts.