> 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/sanitization/sanitization.md). # Sanitize documents overview with Apryse Server SDK Sanitize content from a PDF document with ease using our helpful guide. Learn how to securely remove hidden, sensitive, or potentially unsafe non-visual content from your files. Sanitization is a process that removes hidden, non-visual content permanently from a PDF. This is typically used to strip sensitive metadata, embedded scripts, and residual data so documents can be safely shared externally. Apryse SDK's PDF sanitization offers a dedicated PDF sanitization API that provides programmatic control over sensitive data removal to improve document security and compliance. You can remove (not just disable or obscure) non-visual content embedded within a PDF's internal structures. While visible page content such as text and graphics may appear harmless, a PDF can also carry data that is not rendered but still persists and can be extracted. Sanitization permanently destroys this content including content groups such as metadata, form data, and hidden layers for safe distribution to clients, partners, regulatory bodies, or any other audience that should not have access to the document's underlying data. ## Get started [Sanitize content from a PDF document](/core/sanitization/sanitize.md) --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.apryse.com/core/sanitization/sanitization.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 `build a script that syncs our docs to a CMS` 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.