> 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/uwp/extraction/samples.md).

# Code samples for extracting & parsing PDFs in UWP

Learn how to work with PDF page labels, extract images, and more with this informative guide. Explore advanced PDFNet features for data extraction. The Apryse uwp SDK streamlines secure document proce

[PDF page labels](/uwp/get-started/samples.md#pagelabels) This example illustrates how to work with PDF page labels. PDF page labels can be used to describe a page.

[PDF logical structure reader](/uwp/get-started/samples.md#logicalstructure) This sample explores the structure and content of a tagged PDF document and dumps the structure information to the console window.

[PDF image extraction](/uwp/get-started/samples.md#imageextract) This sample illustrates couple of approaches to PDF image extraction.

[Read elements across all PDF pages](/uwp/get-started/samples.md#elementreader) Illustrates how to traverse page display list using ElementReader.

[PDF data extraction (images, text, paths)](/uwp/get-started/samples.md#elementreaderadv) The sample shows how to use some of more advanced PDFNet features. The sample code illustrates how to extract text, paths, and images.


---

# 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/uwp/extraction/samples.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.