> 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/archive/features-legacy-databutton-web-app-builder/workspace-features/storage.md).

# Storage

What it is: Storage provides persistent file storage for your app, accessible via the Databutton SDK. Store CSVs, images, PDFs, and other files that your app needs.

How to access: Click the Storage tab in the workspace topbar.

Key features:

* File browser: View all stored files
* Upload/download: Manage files through the interface
* SDK access: Read/write files from Python backend code
* Persistent storage: Files persist across app restarts

How to use:

1. Upload files manually via the Storage tab, or
2. Ask the agent to create upload functionality in your app, or
3. Have the agent store data programmatically using the Databutton SDK

Tips:

* Use storage for files, use the database for structured data
* The file system is not persistent - always use storage or database

Storage is accessible from backend only, not frontend


---

# 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/archive/features-legacy-databutton-web-app-builder/workspace-features/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.