> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/pdf-a.md).

# PDF/A

- [PDF/A Conversion Library using JavaScript](https://docs.apryse.com/web/pdf-a/pdfa.md): Convert generic PDF documents to PDF/A with our API for archiving and preservation. Explore PDF/A conversion, validation, and tools. Find the right version of PDF/A for your needs. Get started today!
- [Convert PDF to PDF/A using JavaScript](https://docs.apryse.com/web/pdf-a/convert.md): Convert PDF to PDF/A format with ease using our tool. Supports various PDF/A versions and ensures compliance. Check out the full sample code for validation and conversion. The Apryse Web SDK streamlin
- [Validate PDF/A documents using JavaScript](https://docs.apryse.com/web/pdf-a/validate.md): Validate all versions of PDF/A using JavaScript. All you need is full API enabled in WebViewer to validare pdf/a using JavaScript.
- [Code samples to validate & convert PDF to PDF/A using JavaScript](https://docs.apryse.com/web/pdf-a/samples.md): Convert PDF to PDF/A Sample Code - Learn how to validate existing PDFs for PDF/A compliance and convert generic PDFs to PDF/A format. Try our demo now! The Apryse Web SDK streamlines secure, serverles
- [APIs for PDF/A conversions & validation using JavaScript](https://docs.apryse.com/web/pdf-a/apis.md): Discover utility classes for PDF/A or PDF documents with Web (Javascript) PDFNet.PDFACompliance. Enhance your PDF files effortlessly. The Apryse Web SDK streamlines secure, serverless document process


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/web/pdf-a.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.