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

# Code samples to create / generate PDFs on Server/Desktop

Learn how to merge, copy, delete, and rearrange PDF pages efficiently. Discover methods to build, write, and embed elements in PDF pages. Search & replace text or images in PDFs with ease. The Apryse

[Merge, copy, delete, and rearrange PDF pages](/core/get-started/samples/pdfpagetest.md) The sample illustrates how to copy pages from one document to another, how to delete, and rearrange pages and how to use ImportPages() method for very efficient copy and merge operations.

[Build, write, embed elements in PDF pages](/core/get-started/samples/elementbuildertest.md) Illustrates how to use PDFNet page writing API, how to embed fonts and images and how to copy graphical elements from one page to another.

[Search & replace PDF text or images](/core/get-started/samples/contentreplacertest.md) This sample shows how to use pdftron.PDF.ContentReplacer to search and replace text strings and images in existing PDF (e.g. business cards and other PDF templates)


---

# 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/core/create/samples.md?ask=<question>&goal=<endgoal>
```

`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.