> ## Documentation Index
> Fetch the complete documentation index at: https://developer.pdf.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Convert PDF to PDF/A

> Convert a PDF to PDF/A-3b in Zapier and check its compliance with a veraPDF validation report.

Use the **Convert PDF to PDF/A** action to prepare PDFs for archiving. The action converts the source PDF to PDF/A-3b and validates the result with veraPDF.

> [!WARNING]
>
> A completed conversion can return `isCompliant: false`. Check this field before treating the output as a compliant PDF/A document. Open `validationReportUrl` to review any failed validation rules.

![Zapier Convert PDF to PDF/A action showing the Source File URL and optional File Name fields](https://mintcdn.com/pdfco/GdtF0b3J8SH7nlPG/images/integrations/zapier/pdf-to-pdfa-setup.png?fit=max\&auto=format\&n=GdtF0b3J8SH7nlPG\&q=85\&s=3448db81ac285728385c09ed90fab986)

The screenshot uses the sample PDF URL. In a live workflow, map the PDF file from your trigger or an earlier step to **Source File URL**.

## Input

| Name | Description | Required |
| - | - | - |
| **Source File URL** | Provide the URL of the source PDF. The file must be accessible to PDF.co. See [Integrating File Sources with PDF.co](https://developer.pdf.co/integrations/zapier/input-file-sources.md) for Google Drive, Dropbox, and other file sources. | Yes |
| **File Name (optional)** | Enter a name for the output PDF. If left empty, the original file name is used. | No |

## Example: Archive a PDF

1. Add a **PDF.co** action after the step that provides your PDF.

2. Select **Convert PDF to PDF/A** and connect your PDF.co account. See [Getting Started with Zapier](https://developer.pdf.co/integrations/zapier/getting-started.md) for connection instructions.

3. Map the PDF link from the previous step to **Source File URL**. To try a sample, use:

   ```text theme={null}
   https://pdfco-test-files.s3.us-west-2.amazonaws.com/pdfa/sample.pdf
   ```

4. Set **File Name (optional)** to `archived-document.pdf` and test the action.

5. Add **Filter by Zapier** after the conversion. Continue only when `isCompliant` is `true`.

6. Map `url` to your storage app's upload step to save the PDF before its temporary link expires. You can also save the JSON report from `validationReportUrl`.

> [!NOTE]
>
> This action is available in PDF.co app version **4.1.0** and later. If it is missing from an existing Zap, select the current PDF.co app version for that step.

## Output

| Name | Description |
| - | - |
| `url` | Temporary link to the converted PDF when a file was produced. |
| `pageCount` | Number of pages in the converted PDF. |
| `status` | Job result, such as `success`. A successful job does not by itself confirm PDF/A compliance. |
| `message` | Message describing the job result. |
| `isCompliant` | `true` when the converted document passes PDF/A validation, or `false` when it does not. |
| `validationStatus` | Whether validation completed. Check this alongside `isCompliant`. |
| `pdfaProfile` | PDF/A profile used for validation, such as `PDF/A-3B`. |
| `validationReportUrl` | Temporary link to the JSON validation report, when available. |
| `validationReportName` | Name of the validation report file. |
| `failedRules` | Number of validation rules that failed. |
| `failedChecks` | Number of individual validation checks that failed. |
| `validator` | Validator used, such as `veraPDF`. |
| `validatorVersion` | Version of the validator used for this job. |
| `validatedAt` | Time the document was validated, when available. |
| `outputLinkValidTill` | Expiry time of the converted PDF link, when returned. |
| `validationReportLinkValidTill` | Expiry time of the report link, when returned. |
| `jobId` | Identifier for the PDF.co background job. |
| `credits` | Credits reported for processing the document. |
| `remainingCredits` | Remaining PDF.co credit balance. |

## Timeouts and validation

> [!WARNING]
>
> In the Zapier editor, **Test step** has a [30-second execution limit](https://docs.zapier.com/integrations/build/troubleshoot-action-timeouts#testing-action-in-zap-editor). An editor timeout does not cancel the PDF.co job, which can continue processing and incur charges. Check [PDF.co API Logs](https://app.pdf.co/account/logs/api) before submitting it again.

Published Zaps receive the result through a callback and resume when processing finishes. A job that times out in the editor may still complete in a published Zap.

If conversion completes but the document is not compliant, the step can still succeed with `isCompliant: false`. Use the filter in the example to keep that document out of your archive, then review the validation report to see what needs attention.

If conversion or validation cannot complete, the step can fail and one or both file links may be unavailable. The error includes a **Validation report:** link when a report is available.

Save the converted PDF and report to your own storage before their temporary links expire. See the [PDF to PDF/A API reference](https://developer.pdf.co/api/pdf-to-pdfa.md) for validation details and file-retention limits.

To create a Factur-X or ZUGFeRD invoice with embedded XML, use [Convert PDF to E-Invoice](https://developer.pdf.co/integrations/zapier/pdf-to-e-invoice.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.