> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/settings/files.md).

# Files

Upload and manage the images your experiences use.

**Files** holds the images your experiences use, such as icons, banners, and illustrations in campaigns, Finders, and Sagent. Each file gets a public URL on the Crobox CDN.

Open **Settings → Files**.

{% hint style="info" %}
Files is available when it's included in your plan. Contact your Customer Success Manager to enable it.
{% endhint %}

### Upload files

Drag images onto the upload area, or click it to choose them. Supported file types are **SVG**, **JPG**, and **PNG**.

{% hint style="warning" %}
Uploaded files are publicly accessible through the Crobox CDN. Don't upload anything that shouldn't be public.
{% endhint %}

If a file with the same name already exists, you're asked to confirm before it's overwritten. Overwriting changes the image everywhere it's used, so give a new image a new name unless you mean to replace it.

### Find and open a file

Use **Search files by name...** to filter the grid. Click a file's name to open it in a new tab, where you can copy its public URL.

### Delete files

Click files to select them, then click the delete icon in the header and confirm with **Delete anyway**. Deleting can't be undone, and any experience that uses the file will show a broken image.

{% hint style="info" %}
When a search is active, only the selected files that match the search are deleted.
{% endhint %}

### Copy files to another container

Select files and use the copy menu in the header to **Copy to clipboard**. Switch to the other container, open **Settings → Files**, and **Paste from clipboard**.


---

# 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.crobox.com/how-to-guides/settings/files.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.
