Preflight
Variable-data printing · PDF/VT

What is PDF/VT?

PDF/VT is the ISO standard for variable-data and transactional printing — personalized statements, bills, and direct mail. Drop a file for a free structural scorecard — no signup.

ISO 16612-2 · validated as part of Preflight's Print & Archive module (the deterministic subset on the PDF/X-4 base — not full RIP-level validation).

PDF/X-4 base
All fonts embedded, device-independent color with an OutputIntent, and no encryption.
DPart hierarchy
A document-part tree (/DPartRoot) marking each recipient’s record boundary.
PDF/VT identifier
The GTS_PDFVTVersion that declares PDF/VT conformance.
Document-part metadata
DPM carrying per-record metadata for the variable-data RIP.
Traceable
Every finding maps to an ISO 16612-2 / ISO 15930 condition; RIP-level semantics are reported not-evaluable, never an invented pass.

PDF/VT (ISO 16612-2) is the PDF standard for variable-data printing — high-volume jobs where each recipient gets personalized pages. It is built on PDF/X-4, so it inherits print-ready color and font rules, and adds the structures a variable-data RIP needs: a DPart hierarchy that marks per-record boundaries, document-part metadata (DPM) for each record, and encapsulated content for caching. There are three flavors — PDF/VT-1 (a single self-contained file), PDF/VT-2 (which may reference external content), and PDF/VT-2s (a streamed variant).

How to make a PDF/VT-compliant file

  1. Start from a PDF/X-4 base — embed every font, use device-independent color with an OutputIntent, and remove encryption.
  2. Structure records as DParts — build the /DPartRoot hierarchy so each recipient’s pages are a distinct document part.
  3. Attach document-part metadata — add DPM to the records the RIP needs to route or personalize.
  4. Encapsulate reusable content — mark shared assets as encapsulated XObjects so the RIP can cache them across records.
  5. Write the PDF/VT identifier and validate — set GTS_PDFVTVersion, then run a deterministic check and fix each finding before you submit.
Try the free analyzer →See pricingPDF/VT in Print & Archive

Frequently asked questions

What’s the difference between PDF/VT and PDF/X?

PDF/X is print-ready static artwork; PDF/VT builds on PDF/X-4 and adds the record structure (DPart) and metadata (DPM) a variable-data RIP needs for personalized, high-volume printing.

What is a DPart?

A “document part” — a node in a hierarchy (/DPartRoot) that marks a record boundary, e.g. one recipient’s pages, so a VDP RIP can process each record independently.

What is the difference between PDF/VT-1 and PDF/VT-2?

PDF/VT-1 is a single self-contained file (on the PDF/X-4 base); PDF/VT-2 builds on PDF/X-4p / X-5 and may reference external content. PDF/VT-2s is a streamed variant.

Is PDF/VT only for mail?

No — it’s used for any high-volume variable-data printing: statements, bills, transactional documents, and personalized direct mail.

How do I check if a file is PDF/VT?

Preflight validates the determinable PDF/VT conditions (the PDF/X-4 base + the DPart hierarchy + the PDF/VT identifier + DPM presence) as part of the Print & Archive module — turn on a PDF/VT target in your Print settings. It is a pragmatic, deterministic subset, not full RIP-level validation.

Related

What is PDF/VT? The variable-data printing standard · Preflight