veraPDF now supports PDF/A-4

Excerpt: The latest veraPDF adds support for PDF/A-4, the archival subset specification for PDF 2.0.

About the author: The staff of the PDF Association are dedicated to delivering the information, services and value members have come to expect.

January 24, 2022
by PDF Association staff

The latest release of veraPDF, the industry-supported, open source PDF/A validator and a key component of the Open Preservation Foundation’s reference toolset, is now available.

New in version 1.20

January 20, 2021


  • added support for PDF/A-4 including conformance levels F (file attachments) and E (engineering)
  • added more informative logs in batch processing
  • added new parameter to specify the default validation profile in case of missing standard identification in XMP metadata

PDF Model

  • extended the model to support PDF/A-4 rules

PDF Parser

  • more robust handling of malicious PDF documents
  • improved parsing of PostScript and CFF fonts


  • allow empty Lang Alt arrays in XMP metadata
  • excluded All and None colorants from the PDF/A-2 and PDF/A-3 requirement to have the same tintTransform and alternateSpace
  • disabled JPEG2000 colr box checks in case of explicitly defined ColorSpace in the Image dictionary
  • fixed validation of predefined XMP value types if they are redefined in the extension schema
  • validate XMP URL type as Text
  • fixed CIDSet and CharSet validation for PDF/A-1
  • fixed validation of the permissions dictionary in PDF/A-2 and PDF/A-3
  • added validation of Lang against RFC 1766 regular expression
  • fixed validaiton of permitted transfer functions in Halftone dictionaries


  • added test corpus of ~600 new atomic documents covering PDF/A-4 specification
  • extended PDF/A-2u tests on ToUnicode mapping and character encodings in simple fonts

Core library

  • added support of Java versions from 11 to 16
  • fixed validation of documents with non-PDF extension in multi-process mode


If you encounter problems, or would like to suggest improvements, please add them to the project’s GitHub issue tracker: