> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.6.0/getting-started/tech-specs/helmut4-clients.md).

# Helmut4 Clients

Although Helmut clients can be used for various tasks, the following list of system requirements is recommended for Helmut4 clients that will perform render-intensive tasks.

**Recommended System Requirements:**

* CPU: Single socket system with AMD TR 3970X, Intel i9 10980X or Xeon W-3345 or similar. Priority should be given to clock speed over core count
* OS:\
  Microsoft Windows 10 (64-bit), v1903 or later\
  MacOS 10.12 or later
* RAM: 64GB or higher
* GPU: Nvidia Quadro RTX A4000 or higher.
* Ethernet: 10GbE<br>

{% hint style="info" %}
For detailed information on the recommended system requirements, please visit the official Adobe Media Encoder website - <https://helpx.adobe.com/media-encoder/system-requirements.html>
{% endhint %}

{% hint style="warning" %}
&#x20;A permanent internet connection is required to activate Adobe licenses, validate subscriptions every 90 days, and access online services
{% endhint %}

## Linux Render Node :

* CPU: A minimum of 2 Cores
* RAM: A minimum of 2GB of RAM
* GPU: not supported
* Ethernet: A minimum of 1 GbE provided by the host, while 10 GbE is recommended for file move/copy operations or heavy rendering

{% hint style="info" %}
The Linux client is available as a Docker container and is only compatible with x86-based Linux distributions
{% endhint %}

{% hint style="warning" %}
Please note that the Docker container version of our client is designed for unattended operation and cannot run any UI applications.
{% endhint %}


---

# 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.helmut.de/helmut4-releases/v4.6.0/getting-started/tech-specs/helmut4-clients.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.