Skip to content

Conformance

Standards, and how to verify them.

We don’t ask you to take conformance on faith. For every standard NextPDF targets, here is the edition, the exact command to verify it yourself, and an honest note on scope. Generate a file in the free trial and run the validator on your own machine.

Start the trialDownload real samples

  • PDF 2.0

    ISO 32000-2:2020Core

    Documents built on the PDF 2.0 object model from the core out — valid file structure and cross-reference, not "PDF-ish" bytes.

    Verify it yourself
    qpdf --check invoice.pdfParses the file like a conforming reader; a clean file reports no structural or stream-encoding errors.
    Evidence today
    Download a sample →
    Spec reference
    ISO 32000-2 §7.5 (file structure — cross-reference table / streams)

    Scope Confirms structural validity. A specific conformance profile (PDF/A, PDF/UA) is a separate check, below.

  • Tagged accessibility (PDF/UA-2)

    ISO 14289-2:2024CoreRegulated

    Tagged real content in the logical structure tree, with figure alternative text and a document language — so the meaning travels, not just pixels.

    Verify it yourself
    verapdf --flavour ua1 tagged.pdfveraPDF is the PDF Association reference validator. Use the UA-1 flavour today; UA-2 tooling is maturing.
    Spec reference
    ISO 14289-2 (PDF/UA-2); real content tagged in reading order; Alt + Lang carried per ISO 32000-2 §14.7–14.8

    Scope The engine emits conformant structure; meaningful alt text and reading order are your editorial responsibility.

  • Archival (PDF/A-4)

    ISO 19005-4:2020EnterpriseRegulated

    Archival output with a PDF/A OutputIntent + embedded ICC profile, the pdfaid identification schema, and embedded fonts.

    Verify it yourself
    verapdf --flavour 4 archival.pdfValidates against the PDF/A-4 rule set and lists every passed and failed clause.
    Spec reference
    ISO 19005-4 §6.2.3 (OutputIntent); §6.7.3 (pdfaid identification); §6.2.10 (fonts)

    Scope A passing validator confirms the file conforms; long-term archival suitability also depends on your inputs.

  • Digital signatures (PAdES)

    ETSI EN 319 142-1Core → EnterpriseRegulated

    PAdES signatures across the levels: B-B baseline (Core), B-T trusted timestamp (Pro), B-LT / B-LTA long-term + archival (Enterprise).

    Verify it yourself
    openssl cms -verify -binary -in token.p7sOr open the signed PDF in Adobe Acrobat and inspect the signature panel.
    Spec reference
    ETSI EN 319 142-1 clause 6 (§6.1 levels; Table 1); ISO 32000-2 §12.8 (signatures), §12.8.4.3 (DSS)

    Scope NextPDF emits real CMS SignedData. Whether a signature is legally qualified depends on your certificates, trust service, and process.

  • E-invoicing (ZUGFeRD / Factur-X)

    EN 16931-1EnterpriseRegulated

    A hybrid invoice: the readable PDF plus an embedded structured XML targeting the EN 16931 core invoice model, in a PDF/A-3 container.

    Verify it yourself
    pdfdetach -saveall einvoice.pdfExtracts the embedded XML (poppler-utils); validate it against the EN 16931 schematron, or submit to your buyer / tax-authority portal — the recipient’s validator is the real test.
    Spec reference
    EN 16931-1 §7 (core invoice semantic data model)

    Scope NextPDF builds output that targets the model; acceptance is determined by the recipient’s validator and the correctness of your data.

  • AES-256 encryption

    ISO 32000-2 §7.6Pro

    AES-256 (AESV3, R6 security handler) encryption of strings and streams.

    Verify it yourself
    qpdf --show-encryption encrypted.pdfReports the encryption algorithm and key length in use.
    Spec reference
    ISO 32000-2 §7.6 (encryption); AES-256 per FIPS 197 / ISO/TS 32004

    Scope Encryption protects content at rest in the file; key management and distribution remain yours.

How we ground this

Where the confidence comes from — and where it stops

  • Clauses are verified against the primary specs. Each spec reference above is checked against the source standard (ISO, ETSI, CEN, IETF), not folklore — we cite the clause and summarise it in our own words.
  • Samples are real engine output. The downloadable PDFs are produced by NextPDF and pinned by SHA-256 in a provenance manifest; nothing on the showcase is a mock-up.
  • Conformance is your validator’s verdict. A passing veraPDF / qpdf / OpenSSL run confirms the file meets the format rules. Whether your document is legally accessible, archival, qualified, or accepted by a given authority also depends on your content, certificates, and process. NextPDF gives you the capability and the receipts; it does not, by itself, make you compliant.
Generate & validate in 5 minutesTrust Center