> 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/xamarin/get-started/faq/full-vs-standard.md).

# Apryse full or standard? Which version is for me?

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

{% hint style="info" %}
**This tutorial only applies to Xamarin.Android.**
{% endhint %}

Apryse library comes in two versions: full and standard.

In order to help our customers to create applications with a smaller APK size, the standard version omits a number of features such as:

* [`Convert`](https://sdk.apryse.com/api/xamarinandroid/pdfnet/api/pdftron.PDF.Convert.html), [`Optimizer`](https://sdk.apryse.com/api/xamarinandroid/pdfnet/api/pdftron.PDF.Optimizer.html), [`Redactor`](https://sdk.apryse.com/api/xamarinandroid/pdfnet/api/pdftron.PDF.Redactor.html), [`Flattener`](https://sdk.apryse.com/api/xamarinandroid/pdfnet/api/pdftron.PDF.Flattener.html), [`DocumentPreviewCache`](https://sdk.apryse.com/api/android/javadoc/reference/com/pdftron/pdf/DocumentPreviewCache.html), [`ReflowProcessor`](https://sdk.apryse.com/api/android/javadoc/reference/com/pdftron/pdf/ReflowProcessor.html) classes
* PDF/A validation/conversion (i.e. [`PDFACompliance`](https://sdk.apryse.com/api/xamarinandroid/pdfnet/api/pdftron.PDF.PDFA.PDFACompliance.html))
* Converting PDF pages to TIFF format (i.e. [`PDFDraw`](https://sdk.apryse.com/api/xamarinandroid/pdfnet/api/pdftron.PDF.PDFDraw.html) will not work when using these formats)

{% hint style="info" %}
**Rendering speed and quality are the same for both versions of the library.**
{% endhint %}

The following table compares the APK size of a sample project in which different architecture and Apryse library versions were used.

| Apryse library | Architecture | the sample APK size |
| -------------- | ------------ | ------------------- |
| Full           | armeabi      | 16 MB               |
| Full           | armeabi-v7a  | 15 MB               |
| Full           | arm64-v8a    | 16 MB               |
| Full           | x86          | 16 MB               |
| Full           | x86\_64      | 17 MB               |
| Full           | combined     | 64 MB               |
| Standard       | armeabi      | 9 MB                |
| Standard       | armeabi-v7a  | 9 MB                |
| Standard       | arm64-v8a    | 9 MB                |
| Standard       | x86          | 10 MB               |
| Standard       | x86\_64      | 10 MB               |
| Standard       | combined     | 31 MB               |

Here are some scenarios to help you decide which one to use:

* I need minimum size possible and I only need to render PDFs\\

Standard version

* I want to use the Demo package\\

Full version

* I need to display non-pdf documents\\

Full version

* I need to display documents with reflow\\

Full version

* I need to optimize, redact, or flatten PDFs\\

Full version

* I need to convert PDF pages to TIFF formats\\

Full version

* I need to build a file browser that displays all files on a device with first page preview for each\\

Full version

* I need right to left support\\

Full version

If none of the above fits your situation, you are more than welcome to consult the Apryse [support team](https://apryse.com/support) to find the best option for you.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/xamarin/get-started/faq/full-vs-standard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.