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

# Overview

What Fovus Storage is, how it's organized, and how to access it from the browser, CLI, workstation, or your local machine.

**Fovus Storage** is the cloud file storage that persists across all your jobs and workstations. Upload your data once — every job task, workstation, and pipeline run can access the same files without copying them between compute nodes.

## The Storage page

Open the Storage page from the top navigation bar at [app.fovus.co](https://app.fovus.co). The page has three main areas: the sidebar, the file table, and the storage usage widget.

![The Storage page with the Storage link highlighted in the top navigation bar and My files selected in the sidebar.](https://2108897467-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhGluyldqdG6yHzilfIdu%2Fuploads%2Fgit-blob-07b5bf08f6719fc75797bd5a45f2e5e3c1fd8069%2Fupload-files-storage-page-overview.png?alt=media)

## Storage sections

The sidebar lists five sections, each serving a different purpose:

| Section                   | Contents                                                                              | Write access                                            |
| ------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| **My files**              | Files and folders you upload directly — your personal working area                    | Yes                                                     |
| **Job files**             | Output files and artifacts organized by Job ID, created automatically during job runs | Read-only                                               |
| **Pipeline files**        | Files associated with pipeline runs, organized by pipeline                            | Read and write (browser upload not supported — use CLI) |
| **Shared with workspace** | Files and folders any workspace member has shared with the whole team                 | Read-only                                               |
| **Shared with me**        | Files explicitly shared with you by another workspace member                          | Read-only                                               |

### Storage usage

The **Storage used** widget in the sidebar shows two figures:

* **You** — storage consumed by files in your **My files** section.
* **Workspace** — total storage consumed across all workspace members.

Click **Usage by user** to see a breakdown by individual workspace member.

## How storage relates to jobs

When you submit a job, Fovus mounts storage on each compute node so tasks can read shared data at runtime. Two mechanisms connect your Storage files to your jobs:

* **Task inputs** — files in your job folder that are uploaded with the job and placed in each task's working directory.
* **Remote inputs for all tasks** — files already in Fovus Storage that are copied into every task's working directory at startup. Use this for large shared datasets or libraries that are too big to include in the job folder. See [Share storage files with job tasks](/docs/storage/shared-storage-for-tasks.md).

When tasks finish, output files are synced back to **Job files** in Fovus Storage automatically. Those outputs stay available under `/fovus-storage/jobs/<job-id>/` on later job compute nodes and on Fovus Workstations — so you can reuse results from a previous run without downloading them first.

{% hint style="warning" %}
Job files are **read-only**. If you need to edit or process them, copy the files into your working directory (or another writable location) first.
{% endhint %}

## How to access Fovus Storage

| Method                | Where                                                      | Best for                                            |
| --------------------- | ---------------------------------------------------------- | --------------------------------------------------- |
| **Browser**           | [app.fovus.co/folders](https://app.fovus.co/folders)       | Uploading to **My files**, browsing, downloading    |
| **Fovus CLI**         | Terminal on any machine                                    | Scripted uploads, pipeline file management          |
| **Fovus Workstation** | `/fovus-storage/` on the workstation filesystem            | Accessing files during interactive compute sessions |
| **Local mount**       | `/fovus-storage/` (Linux) or `M:\fovus-storage\` (Windows) | Editing files directly without downloading them     |

## File paths on mounted storage

When Fovus Storage is mounted — on a workstation or locally via the CLI — it appears as a directory with the following structure:

```
/fovus-storage/
├── files/      ← My files (read and write)
├── jobs/       ← Job files (read-only)
└── pipelines/  ← Pipeline files (read and write)
```

Files in `/fovus-storage/files/` correspond to **My files** in the web UI. Files in `/fovus-storage/jobs/` correspond to **Job files** and are read-only — you can read and copy them, but cannot modify or delete them through the mount. The same mount is available on job compute nodes and Fovus Workstations.

{% hint style="warning" %}
Do not use `/fovus-storage/` as an active working directory for compute jobs. The NFS mount is optimized for sequential and random reads, not as a high-throughput scratch disk. Keep intermediate files on local SSD and transfer results to Fovus Storage when your computation is complete.
{% endhint %}


---

# 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://help.fovus.co/docs/storage/storage-overview.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.