> For the complete documentation index, see [llms.txt](https://docs.toomuchmedia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toomuchmedia.com/content-management/processing/cms-worker.md).

# CMS Worker

*Article Topics:* [*Content*](/getting-started/common-topics/content.md)*,* [*Sets*](/getting-started/common-topics/sets.md)*,* [*Worker*](/getting-started/common-topics/worker.md)*,* [*Transcoding*](/getting-started/common-topics/transcoding.md)

## What is the Worker?

The CMS Worker processes uploaded content to prepare it for visitors. This is done by transcoding videos to defined [formats](/content-management/formats.md), generating thumbnails, moving files to the correct locations on the server, and more. The worker is required before you begin uploading content.

<figure><img src="/files/Rjw4dYvcMVg80FOzKAfN" alt=""><figcaption></figcaption></figure>

You can have multiple workers on multiple servers. A list of all your workers connected to your CMS can be found on the right-hand side of the Processing tab.

### Worker Status

<figure><img src="/files/CWEc7ChEGKTfiXBxkrbw" alt=""><figcaption></figcaption></figure>

Each worker can be in 1 of three statuses:

* **Standby** - Indicates that the worker is ready to process content.
* **Active** - Indicates that the worker is currently processing content.
* **Offline** - Indicates that the worker has not been seen in a set amount of time and is thus declared as offline. This setting can be found in the Configuration Admin's CMS section.&#x20;

## Where is the Worker located?

If using the Object Store method, the CMS Worker can be on any server of your choosing, granted that the server allows video conversion.

You can find a full list of requirements in the [CMS Worker section of the Requirements](/setup/requirements.md#cms-worker-requirements) article.

{% hint style="danger" %}
**Important:** It is recommended not to put the worker on the same server as your NATS install, so they will not compete for resources.&#x20;
{% endhint %}

If instead, you wish to store and deliver content from your Hosted NATS server, the worker will be located in the **/home/\<username>/transcode/** directory.

## What if I don't need Transcoding?

Transcoding can be turned off using the **Disable CMS Video Transcoding** setting found in the CMS section of the Configuration Admin. When disabled, content is processed normally without video conversion. Ensure your sources already match the formats you wish to offer in the [Member Area's Available Formats](/content-management/member-areas-and-tours/member-area-and-tour-details.md#available-formats) section.

## Related Articles

{% content-ref url="/pages/dPNPRiO0BSqbJsbE22ZC" %}
[Setting up a Worker using MojoHost CDN](/content-management/processing/setting-up-a-worker-using-mojohost-cdn.md)
{% endcontent-ref %}

{% content-ref url="/pages/7JUmkvBG3K3FTowR1uj4" %}
[Content Processing - Details & Settings](/content-management/processing/content-processing-details-and-settings.md)
{% endcontent-ref %}


---

# 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.toomuchmedia.com/content-management/processing/cms-worker.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.