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

# Storage

### Buckets vs. Volumes — Choosing the Right Storage

Both Buckets and Volumes provide persistent storage, but they serve fundamentally different purposes. Use the table below to decide which is right for your use case.

|                                 | **Buckets**                                                                         | **Volumes**                                                                                        |
| ------------------------------- | ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| **Underlying protocol**         | S3 / Walrus (object storage)                                                        | Ceph, R2, or Vendor (block / file storage)                                                         |
| **How you access data**         | Via API or HTTP requests                                                            | Mounted as a local directory path inside your container (e.g., `/home/user/data`)                  |
| **Feels like**                  | A cloud drive / network file share accessed through code                            | A hard disk physically attached to your machine                                                    |
| **Best for**                    | Datasets, model weight archives, media outputs, AI workflow artifacts, static files | Active training checkpoints, databases, code, config files, anything requiring frequent read/write |
| **On-chain verification**       | ✅ Every file has a verifiable ID and tracked history on Walrus                      | ❌ Not applicable                                                                                   |
| **File size limit (UI upload)** | Max 20 MB per file, max 500 files per upload                                        | No per-file limit (block device, size set at volume creation)                                      |
| **Capacity model**              | Usage-based (pay for what you store)                                                | Pre-provisioned in GB at creation time (1–10,240 GB)                                               |
| **Typical use cases**           | Training datasets, model releases, generated images/videos/audio, log archives      | In-progress model checkpoints, fine-tuning data staging, application databases, shared code repos  |

**Rule of thumb:**

* If your workload needs to **read or write files rapidly and repeatedly** during a training or inference job → use a **Volume**.
* If you need to **store and share large files** between jobs, archive outputs, or serve data via HTTP → use a **Bucket**.


---

# 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.yottalabs.ai/products/storage.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.