> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/files-and-storage/upload-and-manage-files.md).

# Upload and manage files

Access your storages and easily upload files using Jet

Use the Data Editor to access files in Jet Admin Storage or a connected storage provider.

## Before you start

Use [Jet Admin Storage](/user-guide/files-and-storage/jet-admin-storage.md), or [connect an external provider](/user-guide/files-and-storage/connect-external-storage.md). Some providers require additional setup before Jet Admin can access their files; follow the provider's connection guide.

## Upload a file

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FwQklYQgbnxbmPjoFTEVS%2FS28a-storage-before-upload.jpg?alt=media" alt="Empty storage folder with Upload File control"><figcaption><p>Before uploading, open the intended storage and select Upload File. This is the empty-folder state.</p></figcaption></figure>

1. Open the **Data Editor** and find the storages section.
2. Select the storage where you want to upload the file.
3. Select **Upload File** and choose a file.
4. Check that the uploaded file appears in the selected storage.

For Jet Admin Storage, you can also select **New Folder** to organize files. See [Jet Admin Storage](/user-guide/files-and-storage/jet-admin-storage.md) for the walkthrough.

## Let app users upload files

For the Classic App Builder, use a File Picker with **Save to Storage** as its output format. Follow [Configure resource storage and app uploads](/user-guide/files-and-storage/configure-resource-storage.md) to select the destination storage.

## Verify the upload

Open the uploaded file from the selected storage and confirm its name and contents. For an app upload, reload the app and check that the saved file remains accessible with the intended user permissions.

If the upload fails, check the destination storage configuration, the provider's access permissions, and any returned error. If a file uploads but does not appear in the app, check the value saved by the form and the component using it.

## Storage walkthrough

{% embed url="<https://www.youtube.com/watch?v=FtR0a40ufRU&list=PLSkzi9eq0vBnUGMnwXrRRVo9TXUjZ7uSj&index=20&ab_channel=JetAdmin>" %}

![Storage File Viewer displaying files and folders](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MW-6hpo34t5teVdGCcb%2F-MW-8SxZZWejzGZUrxw_%2FGIF197.gif?alt=media\&token=238f7147-d861-48b5-afc6-cdf3d526c1fe)


---

# 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.jetadmin.io/user-guide/files-and-storage/upload-and-manage-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.
