# Checking Whether a PDF Is PDF/A Compliant

Learn how to run a PDF/A format check on archived vehicle files, read a compliance report and keep service records readable over the years.

Checking whether a PDF is PDF/A compliant means testing the file against the PDF/A standard for long-term archiving, then reading the result before you file it away. A vehicle record is only useful later if the software of that day can still open it, so the check belongs in your routine when you save service notes and cost documents. The page explains the tools, the settings and the report so you can confirm a file yourself without guesswork. 

## What PDF/A compliance actually tests 

PDF/A compliance tests whether a file carries everything needed to display the same way on a future system. The standard requires embedded fonts, no reliance on external content, and color information defined inside the file. A PDF/A format check therefore looks at structure and resources rather than at whether the document looks correct on your screen. 

## Running a validation with veraPDF 

The veraPDF validator is an open tool built specifically for PDF/A validation and it reports which profile a file claims to meet. You load the document, choose the profile or let the tool detect it, and the validator lists every rule the file breaks. A preflight check in document software follows the same idea and flags fonts, transparency or missing metadata. 

## Reading the compliance report 

A compliance report lists each failed rule with a short code and a pointer to the place in the file. Errors about fonts and color spaces matter most for archiving, while warnings may only affect how strictly the profile is applied. Keep the report beside the converted file so a later reader can see which profile was targeted. 

## PDF/A questions for vehicle records 

### Can I check PDF/A compliance without special software? 

Yes, some document programs include a preflight check that names the PDF/A profile of a file. The check is less detailed than a dedicated validator and may miss rules outside the profile it tests. For a record you plan to keep for years, confirm the result with a validator built for PDF/A. 

### What does a failed PDF/A check mean for my file? 

A failed check means the file breaks at least one rule of the PDF/A profile it targets, not that the file is unreadable now. Missing embedded fonts and undefined color spaces are typical causes, and a conversion step can repair them. Rerun the validation after conversion and keep the new report. 

### Which PDF/A profile should a service record use? 

The right PDF/A profile depends on what the file contains and on the rules of the archive that receives it. Profiles differ in the features they allow, such as transparency or embedded files, so the choice follows the document and the receiving system. Ask the archive which profile it expects before you convert. 

### Does a PDF/A file stay compliant after I edit it? 

No, editing a compliant file can remove embedded fonts or add content the profile forbids. Save edits as a new file, run the PDF/A validation again and store the fresh compliance report with it. Treat the earlier report as out of date once the content changes.
