> 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/pdf-editing/edit.md). # Edit PDF pages with Server/Desktop library Discover how to stamp, remove, read, write, replace, and manage page content in PDF documents with this comprehensive guide. Learn about graphics state, undo, and redo operations. The Apryse Server SD Document editing provides the ability to change content so that its data can be improved or re-purposed. Apryse SDK benefits include: * Remove specific content from existing pages (e.g. based on some property or on positioning information on the page) * Insert or append new content to existing pages * Modify properties/attributes on existing graphical elements (e.g. change font, inter-character spacing, fill color, etc.) * Edit text, images, and paths * Edit document metadata * Edit bookmarks and page annotations * Undo or redo any change * Edit every aspect of the document through COS API ## Get started [Stamp content](/core/pdf-editing/stamp.md) To stamp text, image, or PDF page to a PDF document. [Remove images](/core/pdf-editing/remove.md) To remove all images from a PDF document page. [Reading page content](/core/pdf-editing/read.md) An introduction to reading page content. [Write page content](/core/pdf-editing/write.md) An introduction to writing page content. [Replace page content](/core/pdf-editing/replace.md) To replace PDF text or image with a target region. [Graphics state](/core/pdf-editing/graphics-state.md) An introduction to graphics state. [Undo and redo](/core/pdf-editing/undoredo.md) A guide to undo and redo operations. --- # 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/pdf-editing/edit.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.