> 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/samples.md).

# Code samples to validate & convert PDF to PDF/A using JavaScript

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

{% hint style="info" %}
[Full API](/web/what-is-webviewer/full-api.md) is mainly used for PDF processing situations that are not featured using the Standard API. The preferred recommendation is to use the Standard API to address your situation when possible. Standard API is easy to use, loaded by default, and performs best for most situations.
{% endhint %}

#### [Convert PDF to PDF/A Sample Code](/web/get-started/samples/pdfatest.md)

This sample illustrates how to validate existing PDF documents for PDF/A compliance as well as to convert generic PDF documents to PDF/A format. This is run programmatically, without the viewer.

#### [Validate PDF/A - Showcase Demo](/web/get-started/samples/showcase-demo-validate-pdfa.md)

Full sample code following the [Apryse Showcase: PDF/A Validation Demo](https://showcase.apryse.com/validate-pdfa)

#### [PDF/A Conversion - Showcase Demo](/web/get-started/samples/showcase-demo-pdfa-conversion.md)

Full sample code following the [Apryse Showcase: PDF/A Conversion Demo](https://showcase.apryse.com/pdfa-conversion)


---

# 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/samples.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.