> 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/core/get-started/platforms/linux.md).

# Linux PDF library documentation

Discover the Apryse Server SDK for secure document processing with Linux with native libraries and wrappers, samples and guides for C++, Java, .NET Core, Electron, Python, Ruby, and PHP. Access PDFNet

On the Apryse Server SDK for Linux platform, we provide a native library as well as wrappers for Java, .NET Core, PHP, Ruby, and Python.

The PDFNetC library can also be accessed from alternative languages, such as Java, PHP, Ruby, and Python. Please see our [samples collection](/core/get-started/samples/pdfviewform.md) for samples in the language of your choice. Code sample is available in C# & VB.

## Get started

* [C++ guide](/core/get-started/languages/cpp.md): If you are looking to develop native applications on Linux, starting with `C++` would be a good starting point.
* More step-by-step guides:
  * [Java](/core/get-started/languages/java.md): Get started with the Apryse SDK using Java.
  * [.NET Core](/core/get-started/frameworks/dotnetcore.md): Get started with the Apryse SDK using .NET Core.
  * [Electron](/web/get-started/libraries-and-frameworks/electron.md): Get started with the Apryse Web SDK using Electron.
  * [Python](/core/get-started/languages/python3.md): Get started with the Apryse SDK using Python.
  * [Ruby](/core/get-started/languages/ruby.md): Get started with the Apryse SDK using Ruby.
  * [PHP](/core/get-started/languages/php.md): Get started with the Apryse SDK using PHP.
  * [C interface binding](/core/get-started/languages/c-interface-binding.md): Get started with the Apryse SDK using C interface binding.

## SDK contents

The SDK contains the following files and folders in it.

| File/Folder Name | Description                                                                                                                                                                      |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Lib              | The folder containing Apryse libraries/components.                                                                                                                               |
| CosEdit          | An evaluation version of CosEdit, a stand-alone, low-level PDF editor. Using the evaluation version the users can inspect the low-level structure and contents of PDF documents. |
| Samples          | Folder containing Apryse sample projects.                                                                                                                                        |
| legal.txt        | Legal and copyright information.                                                                                                                                                 |
| license.pdf      | CPU license agreement and warranty for this product.                                                                                                                             |

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

For Alpine Linux-specific instructions, see the [Alpine Linux guide](/core/get-started/get-started/alpine.md).
{% endhint %}

<a href="/core/get-started/readme/api.md" class="button primary">API docs</a><a href="/core/get-started/samples.md" class="button primary">Samples</a>


---

# 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/core/get-started/platforms/linux.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.