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

# System Requirements

Minimum and recommended hardware and software requirements for each VIESUS interface.

The requirements below apply to on-premise installations. For VIESUS Cloud there is nothing to install — see the [Cloud API](/reference/cloud-api/overview.md) section.

***

## VIESUS CLI

| Requirement                   | Windows                                          | Linux                                    |
| ----------------------------- | ------------------------------------------------ | ---------------------------------------- |
| OS                            | Windows 10 or later (x64)                        | Ubuntu 22.04 LTS or newer (x64 or arm64) |
| Disk space                    | \~8 GB                                           | Same                                     |
| RAM                           | 4 GB minimum; 16 GB for production               | Same                                     |
| NVIDIA GPU (AI features only) | Ampere or newer; ≥ 8 GB VRAM; CUDA 12.6 or later | Same                                     |
| VIESUS package                | `VIESUS_Viewer_and_CLI_Setup_*.exe`              | Three `.deb` files from transfer portal  |

***

## VIESUS PDF Enhancer

| Requirement               | Windows                                     | Linux                           |
| ------------------------- | ------------------------------------------- | ------------------------------- |
| OS                        | Windows 10 or later (x64)                   | Ubuntu 22.04 LTS or newer (x64) |
| RAM                       | 4 GB minimum; 16 GB+ for large PDFs         | Same                            |
| VIESUS base               | VIESUS CLI packages must be installed first | Same                            |
| PDF Enhancer package      | `viesusPDF_Setup_*.exe`                     | `viesuspdf_*.deb`               |
| NVIDIA GPU (AI upscaling) | Ampere or newer; ≥ 8 GB VRAM                | Same                            |

***

## VIESUS Node.js Module

| Requirement          | Value                                      |
| -------------------- | ------------------------------------------ |
| OS                   | **Linux only** (Ubuntu 22.04 LTS, x64)     |
| Node.js              | Version 18 or later                        |
| VIESUS base packages | Must be installed before the npm module    |
| CUDA driver          | 12.6 or higher (for GPU features)          |
| RAM                  | 1–2 GB per worker with AI features enabled |

***

## VIESUS C/C++ SDK

| Requirement           | Value                                   |
| --------------------- | --------------------------------------- |
| OS                    | Windows x64, Linux x64, Linux arm64     |
| Compiler              | C++11 or later                          |
| `IsEnhance.h` header  | Request from <info@viesus.com>          |
| VIESUS shared library | Included in the standard VIESUS package |

***

## VIESUS Cloud API

| Requirement      | Value                                                    |
| ---------------- | -------------------------------------------------------- |
| Account          | Free account at [viesus.cloud](https://www.viesus.cloud) |
| API key          | Generated in the dashboard                               |
| Internet access  | Required (API calls to `api.viesus.cloud`)               |
| File size limits | Images: 20 KB – 50 MB; PDFs: 20 KB – 1,000 MB            |
| Starting credits | 200 free credits on new accounts                         |

***

## GPU quick-check

Run this before installing. If GPU acceleration is needed:

**Linux:**

```bash
nvidia-smi
```

Look for `CUDA Version: 12.6` or higher in the output header. If `nvidia-smi` is not found or shows a lower CUDA version, [install or upgrade the NVIDIA driver](https://docs.nvidia.com/cuda/cuda-installation-guide-linux/).

**Windows:**

```powershell
nvidia-smi
```

Or check: **Device Manager → Display Adapters** → right-click → Properties → Driver version.

{% hint style="danger" %}
GPU acceleration requires an NVIDIA GPU with **Ampere architecture or newer** (RTX 3000 series, A-series, or newer). Older cards (GTX 10xx, 20xx) do not support CUDA 12.6. AMD and Intel GPUs are not supported.
{% endhint %}

***

## What you can do without a GPU

Everything except AI features works on CPU:

| Feature                    | CPU  | GPU required    |
| -------------------------- | ---- | --------------- |
| Automatic color correction | ✓    |                 |
| Noise reduction            | ✓    |                 |
| Sharpening                 | ✓    |                 |
| Face detection             | ✓    |                 |
| Red-eye removal            | ✓    |                 |
| Classical upscaling        | ✓    |                 |
| AI Upscaling               | Slow | ✓ (recommended) |
| AI Artifact Removal        | Slow | ✓ (recommended) |
| Background Handling        | Slow | ✓ (recommended) |

For testing AI features without a local GPU, use [VIESUS Cloud](/reference/cloud-api/overview.md) — the GPU is hosted by Viesus AG.


---

# 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/installation/requirements.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.