> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spojit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# File Store

> A place for files and folders that belongs to your workspace, shared by everything you build: uploads, workflows, Miraxa and chat attachments.

The File Store is your workspace's own storage. Open it from the navigation bar. Files and folders here belong to the workspace rather than to any one workflow, so anything put there is available to everything else you build.

Four things write into it: you, by uploading; workflows, through the [File Store node](/workflow-editor/nodes/file-store); Miraxa, when you ask it to save something; and chat, when you save an attachment out of a conversation. They all land in the same place, so a file a workflow produced on Monday is the same file you can download on Tuesday.

## What you can do

<CardGroup cols={2}>
  <Card title="Upload and organise" icon="folder-tree">
    Upload files, create folders, and move, rename or delete both.
  </Card>

  <Card title="Feed a workflow" icon="diagram-project">
    Read a stored file into a run and pass it to a connector, or save a run's output back.
  </Card>

  <Card title="Save from a conversation" icon="paperclip">
    Keep an attachment you sent to Miraxa, or something it produced, instead of losing it with the chat.
  </Card>

  <Card title="Share across workflows" icon="arrows-repeat">
    One price list or template, referenced by every workflow that needs it, rather than a copy in each.
  </Card>
</CardGroup>

## Using it from a workflow

The [File Store node](/workflow-editor/nodes/file-store) gives a workflow the same operations as the page: list, get, save, move, rename and delete, for files and folders. Files a workflow saves appear here immediately.

<Note>
  File content never passes through the workflow history. A **Get** step outputs a small content reference, and the platform swaps the real bytes back in at the point they are used. That is what lets a run move a large file without carrying it through every step.
</Note>

A common shape is a scheduled run that produces something and files it: a schedule trigger, an agent step that writes a summary, then a File Store step that saves it under a dated name.

## Limits and rules

* **Storage counts against your plan's quota.** Files saved by workflows count the same as ones you upload.
* **Directly executable file types are refused**, whether uploaded by hand or written by a workflow.
* **Name collisions** are handled per save: keep both and add a number suffix, overwrite, or fail the step. Overwrite only removes the old file once the new one is safely stored.
* **The File Store is per workspace.** It is not shared across workspaces, and nothing in it is reachable from another one.

## Related

* [File Store node](/workflow-editor/nodes/file-store) for the workflow operations and their outputs
* [Operator Mode](/platform/operator), which can read and write here while it works
* [Miraxa](/platform/ai-chat) for saving attachments out of a conversation

<Snippet file="start-free.mdx" />