> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/dataset-configure-redaction/pdf-manual-overrides/configuring-pdf-options.md).

# Configuring PDF options

{% hint style="info" %}
**Required dataset permission:** Edit dataset settings
{% endhint %}

The **PDF Settings** section of the **Dataset settings** page provides options to configure how to work with PDF files.

<figure><img src="/files/SIK9nd3NB93FgKjrcfYN" alt=""><figcaption><p>PDF Settings section of the Dataset settings page</p></figcaption></figure>

You can also configure the signature, synthesis, and LLM classification mode options from the [Textual Agent](/textual/textual-agent/textual-agent-about.md).

## Configuring whether to redact PDF signatures <a href="#dataset-config-pdf-signatures" id="dataset-config-pdf-signatures"></a>

By default, Textual redacts scanned-in signatures in PDF files. You can configure the dataset to instead ignore the signatures.

Under **PDF Settings**:

* To redact PDF signatures, toggle **Detect and redact signatures in PDFs** to the on position. This is the default configuration.
* To ignore PDF signatures, toggle **Detect and redact signatures in PDFs** to the off position.

## Using the new synthesis process <a href="#synthesis-new-process" id="synthesis-new-process"></a>

Textual has developed an updated synthesis process that is currently implemented for the following entity types:

* URLs
* Names
* Custom entity types

In particular, the new synthesis process improves the display of the synthesized values in PDF files. The values better match the available space and the original font.

Under **PDF Settings**, the **New PDF synthesis mode (experimental)** determines which process to use.

To use the new process, toggle the setting to the on position.

## Using an LLM to analyze structured components <a href="#pdf-llm-classification" id="pdf-llm-classification"></a>

To improve the detection accuracy for sensitive values, you can optionally use an LLM to analyze structured components such as tables and form fields.

To enable this, under **PDF Settings**, toggle **Use LLM to classify structured data for PII detection** to the on position.&#x20;

## Selecting the OCR model to use (self-hosted only) <a href="#ocr-model-self-hosted" id="ocr-model-self-hosted"></a>

For PDFs as well as images, if multiple optical character recognition (OCR) models are available, you can select the specific model to use in the dataset. For information on how to enable specific models, go to [Enabling PDF and image processing](/textual/textual-install-administer/configuring-textual/enable-and-configure-textual-features/textual-config-pdf-image.md).

Under **PDF Settings**, from the **OCR Engine** dropdown list, select the model to use.

<figure><img src="/files/1nEWuBh6Nrmo7Awtr6sG" alt=""><figcaption><p>OCR Engine dropdown list in PDF Settings</p></figcaption></figure>


---

# 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.tonic.ai/textual/dataset-configure-redaction/pdf-manual-overrides/configuring-pdf-options.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.