> 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/basic-operations/extraction/extraction.md). # Server/Desktop PDF Content Extraction Library Unlock the power of PDF text extraction with our efficient tools and utilities. Extract text and embedded fonts effortlessly with PDF2Text. Get started now! The Apryse Server SDK streamlines secure do The Apryse SDK offers deep, programmatic access to PDF content—so you can extract exactly what you need, fast. Key capabilities include: * **Text Extraction:** Pull structured Unicode text with style, position, and layout details using `pdftron.PDF.TextExtractor`. Advanced options include ligature expansion, hidden/duplicated text handling, and more. * **Signature Extraction:** Retrieve digital signatures, timestamps, and verification details. * **Graphics-Level Access:** Extract and analyze graphical elements, including paths, color spaces, dash patterns, and transparency settings. * **Low-Level Character Data:** Access exact positioning of text runs and individual characters for precise downstream processing. * **Font and Glyph Access:** Extract embedded fonts and glyph outlines for advanced rendering or analysis. * **Image Extraction:** Extract all embedded images, with support for all PDF compression filters—including optional RAW output and color normalization. * **Layer (OCG) Extraction:** Programmatically access PDF layers and optional content groups. * **Annotations and Forms:** Retrieve all form fields, annotations, and widget data directly from the document. * **Tagged PDF Support:** Access marked content for tagged PDFs, enabling structure-aware extraction. * **Embedded Objects:** Extract ICC profiles, U3D streams, attachments, and embedded files. * **Metadata Access:** Read document metadata for title, author, keywords, and more. --- # 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/basic-operations/extraction/extraction.md?ask=&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.