> 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/reusable-content/shared/shared-overview-extraction.md). # shared/overview/extraction Content extraction provides the ability to access specific content from a document. Apryse SDK benefits include: * Extract digital signatures (timestamps, etc) * Intuitive page content extraction based on a concept of graphical elements * High-quality and efficient text recognition engine (pdftron.PDF.TextExtractor). TextExtractor can be used to extract structured Unicode text including style and positioning information from any PDF document. The API is simple to use and has a number of advanced options related to hidden or duplicated text, ligature expansion, etc * Low-level text extraction (including positioning information for text runs and individual characters) * Complete access to the graphics state (for color spaces and colorants, dash properties, etc) * Full access to fonts, including glyph outlines * Image extraction. All compression filters allowed in PDF are supported and images can be optionally extracted in RAW format * Image color-conversion and normalization filters * Full access to marked content (e.g. used in tagged PDF documents to preserve logical structure or to mark transparency groups) * Full access to page form fields and annotations * Extraction of embedded fonts, ICC color profiles, U3D streams, embedded files, etc * Access to a document's metadata * High-level Logical Structure API and support for 'Tagged' PDF documents * Extract and render PDF layers (also known as Optional Content Groups, or OCGs) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.apryse.com/reusable-content/shared/shared-overview-extraction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.