> 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/low-level-pdf-api/low-level.md).

# Low-Level document editing (COS/SDF API) on Server/Desktop

Discover the benefits of working with low-level PDF APIs using Apryse SDK. Gain full access to COS/SDF object model, seamless integration, and unique functionalities for customizing PDF documents. Sta

Working with low-level PDF APIs can enable a wide variety of customizations with PDF documents.

Apryse SDK offers the following benefits:

* Full access to low-level PDF object model (also known as COS/SDF)
* Seamless integration between high and low-level API
* Functionality not available in the high-level API can be implemented using COS/SDF API

## Get started

[Adding custom information](/core/low-level-pdf-api/add-custom.md) To add custom information to an existing document.

[A short introduction to PDF file format](/core/low-level-pdf-api/pdf.md) An introduction to PDF file format.

[SDF / COS object model](/core/low-level-pdf-api/sdf.md) An introduction to SDF objects.

[Filters and streams](/core/low-level-pdf-api/filters.md) An introduction to filters and streams.

[Embedded Fonts](/core/basic-operations/extraction/embedded-fonts.md) An introduction to embedded fonts.

## Tools & utilities

[PDF CosEdit](/cli/pdf-cosedit/pdf-cosedit.md) A windows GUI tool for low-level PDF editing to view, add, or edit information for an existing document.


---

# 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/low-level-pdf-api/low-level.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.