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

# Windows PDF library documentation

Develop with ease using Apryse's Server SDK - PDF library for Windows. Choose from .NET 2.0, .NET 4.x, or native C/C++ libraries for multi-platform support. Get started today with Apryse SDK! The Apry

Apryse's Server SDK - PDF library for Windows comes in a variety of versions including .NET 2.0 and .NET 4.x (with WPF) libraries that allow you to develop in any language that targets the .NET runtime.

If you are developing on Linux or macOS platform, or need to support multiple platforms, we provide a native C/C++ library, as well as .NET Core and Java wrappers over the native library.

## Get started

* [.NET development with WPF/WinForms support](/core/get-started/frameworks/dotnet.md): Apryse SDK using .NET Framework
* [Native C/C++ development guide](/core/get-started/languages/cpp.md): For native applications on Windows, `C++` would be a good starting point.
* More step-by-step guides:
  * [.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.
  * [Java](/core/get-started/languages/java.md): Get started with the Apryse SDK using Java.
  * [Python](/core/get-started/languages/python3.md): Get started with the Apryse SDK using Python.
  * [C interface binding](/core/get-started/languages/c-interface-binding.md): Get started with the Apryse SDK using C interface binding.

## SDK overview

Our Windows PDF library contains the following files and folders in it. See [What is Apryse SDK?](https://apryse.com/products/core-sdk/pdf) for more about PDF internals.

* Lib - The folder containing Apryse libraries/components.
* [CosEdit](/cli/pdf-cosedit/pdf-cosedit.md) - An evaluation version of CosEdit, a stand-alone, low-level PDF editor. You can use CosEdit to inspect the low-level structure and contents of PDF documents.
* Doc - A folder containing Apryse API Reference Manual as a WinHelp file.
* Samples - Folder containing Apryse sample projects.
* legal.txt - Legal and copyright information.
* license.pdf - CPU license agreement and warranty for this product.

<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/windows.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.
