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

# Content management

Use **Content management** to prepare and distribute media files to devices across the estate.

Content management helps you upload files once and deploy them to selected devices through rollouts.

### Before you start

Confirm that:

* your role allows you to manage content or schedule content rollouts
* the content files are ready for upload
* you know which devices or device groups should receive the content

If you plan to deploy the content next, review:

* [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md)
* [Manage rollouts](/verifone-central-device-management/verifone-central/rollouts/manage-rollouts.md)
* [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md)

### What content management supports

Use content management to:

* upload static images, animations, audio files, and video files
* prepare content before rollout
* distribute media to selected devices
* support targeted messaging across the device estate

### How content is used

Content files are uploaded to Device Management first.

After upload, the content can be scheduled for download to selected devices through the rollout workflow.

This approach helps you manage estate-wide content updates without loading files onto devices one by one.

### Common use cases

Use content management when you need to:

* update branded media on devices
* deliver promotional or informational messaging
* distribute shared content to many devices at once

### How content management fits into rollouts

Content management is the preparation stage for content deployment.

Most content rollout work follows this order:

1. Upload the content files to Device Management.
2. Select the target devices or groups.
3. Schedule the rollout.
4. Monitor rollout progress and results.

### Related deployment areas

Use these pages when you need to manage other rollout content:

* [Software management](/verifone-central-device-management/verifone-central/rollouts/software-management.md) — manage software packages and reference sets
* [Parameter management](/verifone-central-device-management/verifone-central/rollouts/parameter-management.md) — manage application parameter configuration

### Result

Content management prepares media files for controlled rollout to the right devices.

### Next steps

* [Content rollout for batch devices](/verifone-central-device-management/verifone-central/rollouts/content-management/content-rollout-for-batch-devices.md)
* [Content rollout for single device](/verifone-central-device-management/verifone-central/rollouts/content-management/content-rollout-for-single-device.md)
* [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md)
* [Managing rollouts](/verifone-central-device-management/verifone-central/rollouts/managing-rollouts.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 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.verifone.com/verifone-central-device-management/verifone-central/rollouts/content-management.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.