> For the complete documentation index, see [llms.txt](https://docs.viesus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viesus.com/configuration/pdf-settings.md).

# PDF Settings

The PDF Enhancer's settings.json — general behavior, resizing, folders, triggers, file extensions, and special rendering modes.

The VIESUS PDF Enhancer uses a JSON **`settings.json`** file for its pipeline: general processing behavior, resizing, folder paths, the trigger workflow, file naming, and special rendering modes.

{% hint style="info" %}
**`settings.json` vs `viesusini.json`.** `settings.json` governs the **PDF pipeline** — which folders to watch, how files are handled, triggers, and the resizing of embedded images. The **per-image enhancement** applied to each extracted image (color, sharpening, AI upscaling, etc.) is controlled separately by `viesusini.json` — see the [Parameter Reference](/configuration/parameter-reference.md).
{% endhint %}

**Default path on Windows:** `C:\Program Files\Imaging Solutions\VIESUS\PDFEnhancer\settings.json`. Changes take effect on the next hotfolder start (or immediately in stand-alone mode). For boolean parameters, **0** = OFF, **1** = ON.

***

## Settings groups

| Group              | What it controls                                                            | Reference                                                                 |
| ------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| General            | Core processing behavior, image filtering, adjacency and soft-mask handling | [General](/configuration/pdf-settings/general.md)                         |
| Resizing           | Image resizing, AI Upscaling, and artifact-removal modes                    | [Resizing](/configuration/pdf-settings/resizing.md)                       |
| Folders & Triggers | Source / destination / archive folders and the file-based trigger workflow  | [Folders & Triggers](/configuration/pdf-settings/folders-and-triggers.md) |
| File Extensions    | Naming conventions for processed and archived files                         | [File Extensions](/configuration/pdf-settings/file-extensions.md)         |
| Special Functions  | Render to Image (RTI) and Render to PDF (RTPDF)                             | [Special Functions](/configuration/pdf-settings/special-functions.md)     |

***

## Troubleshooting

For PDF-specific error codes, see [PDF Error Codes](/support/error-codes/pdf.md). For CLI exit codes from the underlying enhancement engine, see [CLI Exit Codes](/support/error-codes/cli.md).

| Symptom                 | Likely cause / fix                                                                             |
| ----------------------- | ---------------------------------------------------------------------------------------------- |
| **File not found**      | Verify all paths exist and are accessible to the PDF Enhancer process                          |
| **Permission denied**   | Ensure exclusive read access to source files and write access to dest/archive folders          |
| **Invalid JSON**        | Check syntax and parameter values against this reference                                       |
| **Port conflict**       | Use `-p` to specify an alternative port if the default (12033) is in use                       |
| **Memory errors**       | Reduce `maxFactor` or `maxTargetSize`; process smaller batches                                 |
| **Images not enhanced** | Verify `minFileSize`, `minImageWidth`, `minImageHeight`, and resize `threshold`                |
| **Trigger not working** | Confirm the trigger filename matches the `trigger` parameter and the folder is being monitored |


---

# 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.viesus.com/configuration/pdf-settings.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.