> 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/guides/smart-data-extraction/packaging.md).

# Smart Data Extraction - Packaging

Learn how to reduce package size for Intelligent Data Extraction module. Optimize storage in cloud computing environments. Remove unnecessary files to suit your specific needs. The Apryse Xamarin SDK

## Reducing Package Size

The Apryse Data Extraction module uses artificial intelligence in several of its engines, and as a result, can consume a substantial amount of disk space. This can be limiting for some users who need to work in constrained environments with limited storage, such as certain cloud computing environments. Here we will discuss how to reduce the package size depending on your Intelligent Data Extraction use case.

The Data Extraction module is composed of 4 engines, each of which have their own file requirements. If you only need some subset of these engines, then you can remove the files from the package that are not a dependency of your required engine.

The file dependencies of each engine are platform specific. Please refer to the [Windows](/core/smart-data-extraction/packaging.md) or [Linux](/core/smart-data-extraction/packaging.md) version of this page for a description of the dependencies of each data extraction engine.


---

# 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/xamarin/guides/smart-data-extraction/packaging.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.