> For the complete documentation index, see [llms.txt](https://docs.helix.voodoo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helix.voodoo.io/user-acquisition/upload-creative-assets.md).

# Upload Creative Assets

Before creating ads for your user acquisition campaigns, you need to upload the creative assets you want to use. The Assets library is where all your creatives are stored, managed, and prepared to create ads.

The following ad types are supported for Interstitial and Rewarded Video ads:

* **Playable**
* **Video + Playable**

## Upload assets

{% stepper %}
{% step %}
**Open the Assets library**

From the left menu, navigate to **User Acquisition → Assets** to open the Assets library.
{% endstep %}

{% step %}
**Start an upload**

Click **Upload assets** in the top-right corner of the page.
{% endstep %}

{% step %}
**Select your application(s)**

Use the dropdown menu to select the application(s) you want to add assets for. You can select both iOS and Android versions if you plan to use the same creative assets for both platforms.
{% endstep %}

{% step %}
**Add your files**

Add your files by dragging and dropping them into the upload area, or by clicking **Choose files** to browse your device.\
Supported formats include video files and HTML files.
{% endstep %}

{% step %}
**Review the selected files**

The selected files will appear in the list. Preview them by clicking the file name, or edit the name by clicking the edit icon next to it.
{% endstep %}

{% step %}
**Complete the upload**

Click **Upload all**, then hit the **Done** button once the process is complete. You will be redirected to your Assets library.
{% endstep %}
{% endstepper %}

## Browse the Assets library

The Assets library lists your assets newest first, 50 per page. Use the page buttons at the bottom to move between pages.

| Column        | Definition                                                               |
| ------------- | ------------------------------------------------------------------------ |
| Name          | Logo of each linked app, asset name, and asset type (Video or Playable). |
| Creation Date | Date the asset was uploaded.                                             |
| File size     | Size of the asset file. Shows **-** when the size is unknown.            |
| Duration      | Length of the video.                                                     |

* Click the **Name**, **Creation Date**, **File size**, or **Duration** header to sort the list.
* Use the **App** filter to show the assets of one or several apps.
* When an asset is linked to several apps, hover its name to see every app and its store. Click an app logo to open that app.
* Click an asset to open its details: status, type, apps, creation date, file size, and duration.


---

# 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.helix.voodoo.io/user-acquisition/upload-creative-assets.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.
