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

# Compare PDF File Differences with JavaScript

Compare PDF files effortlessly with the Apryse SDK. Visually analyze differences in images, text, forms, and more. Start overlaying and pixel-by-pixel comparison now! The Apryse Web SDK streamlines se

{% hint style="info" %}
**Requirements**

*These packages are required to use these features in production. Trial keys have unlimited access to all features*

<a href="https://apryse.com/capabilities#Compare" class="button primary">Package: Compare</a>
{% endhint %}

Comparing files provides the ability to understand what has changed from one file to another.

With the Apryse SDK, you can visually compare the differences between 2 files (images, paths, text, forms, shadings, and other types of content).

## Demos

[Semantic Text Compare Demo](https://showcase.apryse.com/semantic-text-compare) [Compare by Image Overlay Demo](https://showcase.apryse.com/compare-files)

## Get started

[PDF Overlay](/web/compare-files/diffing.md) To provide a visual document comparison by [overlaying](https://en.wikipedia.org/wiki/Blend_modes#Overlay) and [masking](https://en.wikipedia.org/wiki/Mask_\(computing\)).

[Pixel-by-pixel (Image Overlay)](/web/compare-files/pixels.md) To provide a visual document comparison by gathering each pixel to find the [sum of absolute differences](https://en.wikipedia.org/wiki/Sum_of_absolute_differences).

[Semantic Text](/web/compare-files/semantic.md) To detect differences between two docuemnts on a word-by-word basis.


---

# 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 dynamically 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/compare-files/compare.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 `build a script that syncs our docs to a CMS` 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.