Skip to main content
The storage list shows all files and folders stored in your project, organized by folders.

File Upload

Store user-uploaded files in the cloud

File Download

Download files individually or as ZIP bundles

Persistent Storage

Files remain accessible across sessions and devices

​
File & Folder List

The storage list displays items in a table view with the following columns:

Name

File or folder name

Size

File size (folders show –)

Type

File type/extension (folders show –)

Last Modified

Timestamp in user’s local timezone (folders show –)
Clicking a folder opens its contents. All timestamps are displayed in the user’s local timezone.

​
Downloading Files

You can download files directly from the storage list.
1

Select Files

Choose one or more files from the storage list by clicking on them.
2

Click Download

Click the Download button to start the download process.
3

Wait for Preparation

For multiple files, a loading state is shown during packaging.
4

Download Starts

Downloads start automatically once preparation is complete.

Single File Download

Select one file and click Download.Behavior:
  • The file downloads directly
  • No additional packaging required
For large downloads with many files, the preparation step may take a few moments. The download will begin automatically once the ZIP is ready.

​
Refreshing Storage

1

Locate Refresh Icon

Find the refresh icon at the top of the storage list.
2

Click to Refresh

Click the refresh icon to reload the file list.
3

View Latest State

The storage list updates to show the most recent files and folders.
Use refresh to see newly uploaded files or verify storage changes made by your application.

​
Storage Limitations

In YouBase, certain features are intentionally limited:

Upload & Download

File upload and download are supported

File Preview

File preview is not supported

File Deletion

File deletion is not supported

Agent Modification

Agents cannot directly modify storage contents
These limitations are intentional to reduce risk and complexity in early versions.

​
When to Use Storage

Storage is recommended when your project needs:

User Uploads

User-uploaded files (images, documents, attachments)

Generated Assets

Generated assets or exports

Media & Documents

Media or documents associated with records

Multi-file Downloads

Bundled downloads for offline work
If your project does not handle files, Storage can be ignored and enabled later when needed.

​
Common Use Cases

Below are common scenarios where Storage is useful. Use these examples to decide whether your project needs file upload and download capabilities.
ScenarioUsers need to upload files as part of your product experience.Examples
  • Profile photos / avatars
  • Resume or document uploads
  • Attachments submitted with forms
What Storage provides
  • A safe place to store uploaded files
  • Download access when you need to retrieve files later
  • A reliable file layer for real user workflows
ScenarioYour project generates files that users should be able to download.Examples
  • AI-generated reports (PDFs)
  • Exported summaries or results
  • Generated images or documents
What Storage provides
  • A place to store generated assets
  • Simple download flows (single file or ZIP)
  • A stable way to deliver outputs to users
(Often used together with Functions)
ScenarioEach item in your database should have related files.Examples
  • A product catalog where each product has images
  • A content library with attachments
  • A CRM where each customer record stores documents
What Storage provides
  • File storage that can be associated with database records
  • A simple way to manage assets across your app
(Often used together with Database)
ScenarioUsers need to download multiple files at once.Examples
  • Downloading a set of generated assets
  • Exporting a collection of attachments for review
  • Collecting files for offline work
What Storage provides
  • Download multiple files or folders as a ZIP archive
  • Automatic preparation and download once ready
ScenarioFiles should remain accessible after refresh, logout, or on another device.Examples
  • A workspace where users revisit uploaded documents later
  • A tool that stores ongoing project assets
  • Returning users downloading previously generated outputs
What Storage provides
  • Persistent, cloud-hosted file storage
  • Consistent access across sessions and environments

​
When you might not need Storage

You may not need Storage if your project:
  • Doesn’t accept uploads
  • Doesn’t generate downloadable files
  • Doesn’t attach media/documents to stored records
Storage can be enabled later when your project expands into file-based workflows.