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

# Overview

All VIESUS on-premise interfaces (CLI, PDF Enhancer, Node.js module, C/C++ SDK) share the same **per-image enhancement** configuration file: `viesusini.json`. It defines how each image is enhanced — color, sharpening, AI upscaling, and the rest — and is documented in the [Parameter Reference](/configuration/parameter-reference.md).

{% hint style="success" %}
**You don't need to write one.** VIESUS enhances with sensible built-in defaults out of the box — if no `viesusini.json` is supplied, a default one is used for you. You only provide or edit a file when you want to change those defaults.
{% endhint %}

{% hint style="info" %}
**The PDF Enhancer uses two files.** `viesusini.json` controls the enhancement applied to each embedded image (as above). The PDF Enhancer *also* has its own top-level `settings.json` that governs the **PDF pipeline** — watched folders, triggers, file handling, and resizing of embedded images. The two are separate: `settings.json` points to a `viesusini.json` for the actual enhancement. See the [PDF Settings](/configuration/pdf-settings.md) reference.
{% endhint %}

***

## Where to start

For most workflows you don't need to edit the configuration file by hand:

* **Use a preset.** Pick the [preset](/configuration/presets-gallery.md) closest to your use case, download it, and run — no manual tuning needed for the common cases.
* **Tune interactively.** Load a preset (or the defaults) into the [VIESUS Viewer](/tools/viesus-viewer.md), open a representative image, and change parameters live with before/after preview. Export the resulting `viesusini.json`.
* **Edit the JSON directly.** When you know exactly which values you want, edit `viesusini.json` by hand — every parameter's type, default, and range is in the [Parameter Reference](/configuration/parameter-reference.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 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/overview.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.