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

# Storage

Every workspace has one shared storage quota — a byte allowance set by its plan — covering all of its data: run artifacts, telemetry, load results, features, generated tests, assistant chat, assets, and notes. Manage it in **Settings → Storage**, under **Workspace**.

Storage is a **plan entitlement measured in bytes — not credits**. It never draws from your credit balance.

## Quota by plan

| Plan       | Included storage |
| ---------- | ---------------- |
| Free       | 1 GB             |
| Starter    | 10 GB            |
| Pro        | 100 GB           |
| Enterprise | 1 TB             |

The quota is shared across the whole workspace, so usage in one project counts against the same allowance as every other project.

## Where storage appears

| Place              | What it shows                                                                                 |
| ------------------ | --------------------------------------------------------------------------------------------- |
| Settings > Storage | Total used vs. the plan quota, a breakdown by data type, and a collapsible "By project" view. |
| Dashboard > Usage  | A live storage meter with the same per-type breakdown.                                        |

## See where storage goes

The Storage panel breaks usage down by data type — runs and traces, telemetry, load results, generation, chat, assets, and notes — and, expandable per project, shows which projects hold the most data.

For most data types you can **Clear** older data directly from its row to free space (notes and chat ask you to type-to-confirm). Features are the canonical source of your tests and cannot be cleared here.

## Set per-type retention

Set how long TestVibe keeps each data type before auto-managed cleanup removes the oldest entries. As the workspace approaches its quota, TestVibe warns you and evicts the oldest auto-managed data first.

## Going over quota

Being over the shared quota blocks new work rather than stopping what's already running:

* **Blocked**: asset uploads, visual-regression baseline writes, and new run, generation, and load-test dispatches. TestVibe shows a **Storage full** message and links back here.
* **Not blocked**: runs and generations already in progress always finish, and reviewing or deleting existing data always works.
* **Deleting frees space immediately** — clearing data from a row's **Clear** action, or deleting a run, asset, or other item, unblocks the gates within seconds so you don't have to wait for the next scheduled cleanup.

Need more room? Use **Upgrade for more storage** on the Storage panel to open **Settings → Billing**.

## Related panels

Storage is separate from credits and billing:

| Panel                    | What it covers                                        |
| ------------------------ | ----------------------------------------------------- |
| **Billing**              | Your plan, credit balance, top-ups, and purchases.    |
| **Credit Usage**         | Where this cycle's credits went, broken down by area. |
| **Storage** (this panel) | Shared byte quota and per-type retention.             |

For plan details and pricing, see [Pricing](/pricing.md) and [Plans](/pricing/plans.md).


---

# 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.testvibe.com/account-settings/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.