All docs

Connect storage

Add R2, S3, or agent-backed roots and verify that previews and downloads can work from the browser.

Storage roots

A storage root is a top-level location Filestor can browse. A root can point to object storage such as R2 or S3, or to a machine running the Filestor agent.

Cloud storage

  • Open Settings → Storage, or choose Add storage volume (+) beside Files in the sidebar.
  • Under Add storage, choose Cloudflare R2 or Amazon S3, then enter the bucket, endpoint, credentials, and optional prefix.
  • Use a scoped access key with only the bucket permissions Filestor needs.
  • Use the CORS check when you want browser previews and direct downloads to work.

Agent storage

  • Set up a Cloudflare Tunnel on the machine first. Every agent needs one, so its downloads skip the Filestor backend (tunnel guide).
  • In Settings → Storage, choose Local Drive Agent under Add storage, enter a name and the tunnel hostname, and generate an enrollment token.
  • Run the installer on the machine that has the files.
  • Attach an allowed path as a root after the agent shows as online.

The Linux agent guide walks through the full installer path: Install the Filestor agent on Linux.

Checks

CORS

If previews or browser downloads fail for object storage, check the root's CORS status. Agent-backed roots do not use bucket CORS.

Versioning

S3-compatible roots can expose native object version history. R2 and agent-backed roots may report versioning as unsupported. In S3, suspended versioning keeps existing versions but stops creating new ones.

Root paths keep provider prefixes such as s3://, r2://, or agent:// internally, but Explorer and the sidebar show them as normal volumes, files and folders.