> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/reference/resources/files.md).

# Files

Files stores the files your solution needs, such as company logos, illustrations, static documents, and documents you want Appfarm AI to read.

{% hint style="warning" %}
**Important**

Do not upload files with secret or sensitive content to Files.
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=b5Tf8NUq3os>" %}

## Internal, Public and System

Files has three areas, listed on the left. A line at the top of each area says who can see its files.

| Area         | Description                                                                                                                                                         |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Internal** | Only Appfarm Create users in this solution and [Appfarm AI](https://docs.appfarm.io/reference/appfarm-ai.md) can see these files. You can organize them in folders. |
| **Public**   | Anyone with the file URL can open these files. Only public files can be referenced from the data model and apps, for example as the image in an Image component.    |
| **System**   | A read-only view of what Appfarm AI writes, such as its `memory`, `skills`, `specs` and `tests`. Only Appfarm Create users in this solution can see it.             |

## Add files

There are several ways to add a file.

* In Files, open **Internal** or **Public** and click **Upload files**.
* In **Internal**, click the name of the current folder at the top and select **Upload files** or **New folder**. You can also right-click a folder.
* In the UI designer, add or select an Image component. Under the **Image** property, select **Resource File…**. Click **Upload File…**. The file is added to **Public**.

Folder names `public` and `system` are reserved, because those names are used by the **Public** and **System** areas.

{% hint style="info" %}
**Good to know**

Public files can be up to 50 MB each, and Internal files up to 25 MB each. In **Internal**, each folder or file name can be up to 128 characters, and folders can be at most 10 levels deep. **Internal** counts as the first level, so you can nest up to nine folders inside it.
{% endhint %}

## Find files

Use **Search all files** at the top to find a file by name. The buttons next to the search field switch between a list and a grid.

## Preview a file

Click a file to open a preview panel on the right. The panel header has a download button and a button to hide the preview.

## Manage files and folders

Right-click a file or folder to see what you can do with it.

* **Folders** in **Internal**: **New folder**, **Upload files**, **Rename**, **Move to…** and **Delete folder**.
* **Files** in **Internal**: **Download**, **Rename**, **Move to…** and **Delete**.
* **Files** in **Public**: **Download**, **Copy public URL**, **Edit file details** and **Delete**.

Files in **System** are written by Appfarm AI and can't be changed here.

### View/edit public file details

Right-click a public file and select **Edit file details**. In the modal dialog that appears you can:

* Set a **Title**. This is set to the filename by default.
* Set a description. This is for internal reference only.
* See the file's public URL. This is not typically required since you can bind resource files directly in an app, but it's shown for reference.


---

# 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.appfarm.io/reference/resources/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.
