PDF/A Validate

Pre-validate PDF documents for PDF/A archival compliance

Structural PDF/A pre-flight check: XMP claim, encryption, font embedding, JavaScript and forbidden features.

Example Results

1 examples

Pre-validate a PDF for PDF/A compliance

Check XMP metadata, encryption and font embedding against PDF/A rules.

{
  "verdict": "non-compliant",
  "claimedProfile": null,
  "counts": {
    "critical": 2,
    "warning": 1,
    "pass": 4
  }
}
View input parameters
{ "pdfFile": "/public/samples/pdf/sample-multipage.pdf" }

Click to upload file or drag and drop file here

Maximum file size: 100MB Supported formats: application/pdf

Key Facts

Category
Documents & PDF
Input Types
file
Output Type
json
Sample Coverage
4
API Ready
Yes

Overview

The PDF/A Validate tool performs a structural pre-flight check on your PDF documents to ensure they comply with ISO 19005 long-term archival standards. It scans for critical compliance issues including missing XMP metadata, active encryption, non-embedded fonts, and forbidden interactive features like JavaScript.

When to Use

  • Before submitting digital documents to government, legal, or institutional archives that mandate PDF/A compliance.
  • When verifying if a generated PDF contains forbidden elements like JavaScript, external references, or encryption that prevent long-term preservation.
  • To check if all fonts are fully embedded and XMP metadata is correctly structured within your PDF files.

How It Works

  • Upload the PDF document you want to verify for archival compliance.
  • The tool parses the file structure, checking the XMP metadata, font tables, encryption status, and interactive elements.
  • It evaluates these properties against PDF/A (ISO 19005) specifications.
  • The tool outputs a JSON report detailing the compliance verdict, claimed profile, and counts of critical errors, warnings, and passed checks.

Use Cases

Pre-flighting legal briefs and court filings to guarantee they meet electronic archiving standards.
Auditing corporate document repositories to identify PDFs that lack embedded fonts or contain active scripts.
Verifying academic theses and research papers before uploading them to university digital libraries.

Examples

1. Verifying Legal Documents for Court Archiving

Legal Assistant
Background
A law firm needs to submit a series of case files to a state court archive that strictly requires PDF/A compliance.
Problem
The assistant needs to verify if the generated PDFs contain non-embedded fonts or restricted features before submission.
How to Use
Upload the legal document PDF to the validator tool and run the pre-flight check.
Outcome
The tool returns a JSON report indicating a 'non-compliant' status due to 2 missing embedded fonts, allowing the assistant to fix the document before submission.

2. Checking Academic Dissertations for University Library

Academic Publisher
Background
A university library requires all digital thesis submissions to be compliant with PDF/A for long-term preservation.
Problem
A student's submission might contain interactive elements or JavaScript that violate archival rules.
How to Use
Select the thesis PDF file and run the validation check.
Outcome
The tool confirms compliance with a 'pass' verdict and zero critical errors, confirming the file is ready for the digital repository.

Try with Samples

pdf, file

Related Hubs

FAQ

What does this tool check for PDF/A compliance?

It checks for embedded fonts, XMP metadata claims, encryption, JavaScript, external device-dependent colors, and other features restricted by ISO 19005.

Does this tool modify my PDF file?

No, this is a read-only validation tool that analyzes the structure of your PDF and returns a compliance report without altering the file.

What does a 'non-compliant' verdict mean?

It means the PDF contains elements (like missing fonts or active encryption) that violate PDF/A standards, making it unsuitable for long-term digital archiving.

Can I validate password-protected or encrypted PDFs?

Encrypted PDFs are automatically flagged as non-compliant because PDF/A standards prohibit encryption to ensure future readability.

What PDF/A profiles are supported for validation?

The tool checks general structural requirements across common PDF/A profiles (such as PDF/A-1, PDF/A-2, and PDF/A-3) by identifying forbidden features and missing metadata.

API Documentation

Request Endpoint

POST /en/api/tools/pdf-a-validate

Request Parameters

Parameter Name Type Required Description
pdfFile file (Upload required) Yes -

File type parameters need to be uploaded first via POST /upload/pdf-a-validate to get filePath, then pass filePath to the corresponding file field.

Response Format

{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}
JSON Data: JSON Data

AI MCP Documentation

Add this tool to your MCP server configuration:

{
  "mcpServers": {
    "elysiatools-pdf-a-validate": {
      "name": "pdf-a-validate",
      "description": "Pre-validate PDF documents for PDF/A archival compliance",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=pdf-a-validate",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.

Supports URL file links or Base64 encoding for file parameters.

If you encounter any issues, please contact us at [email protected]