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

# Storage

The Storage tab is your app or agent's file system. It holds files the backend reads and writes (processed data, generated reports, uploaded documents) and assets served to users (images, downloadable files).

Available in both the App builder and Agent builder via the **+** button.

## What you see

Two upload buttons near the top:

* **Upload to internal storage** — files accessible to your backend code only, not publicly reachable
* **Upload to public storage** — files served publicly (e.g. images, downloadable PDFs)

Below the buttons: a table of all stored files, organised into categories — internal files, data objects, and public assets — with file sizes and last-modified dates.

## How to use it

**Upload manually** — click either button to open a file picker. The file is stored immediately.

**Ask the Riff agent** — *"Save this generated report to internal storage"* or *"Set up the agent to store invoice PDFs as they arrive."*

## Internal vs. public

<table><thead><tr><th width="173.77520751953125">Type</th><th>Who can access it</th></tr></thead><tbody><tr><td><strong>Internal</strong></td><td>Your backend code only — never exposed to the browser or public URLs</td></tr><tr><td><strong>Public</strong></td><td>Anyone with the URL — use for assets your app serves to users</td></tr></tbody></table>

Use Storage for files (PDFs, CSVs, images, documents). Use the [Database](/reference/app-builder/database.md) for structured data (tables, records, relationships).


---

# 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.riff.ai/reference/shared/storage.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.