فارسی · Components · Home
File storage
Where the pictures, videos and files people send are kept. By default they're
on the server's own disk, in /matrix/synapse/storage/media-store, which is
the right choice until that disk gets full. Pick one of these at most.
How to add any of these: Components.
S3 storage provider (recommended of the three)
Synapse only. Keeps media in S3-compatible object storage (AWS, Backblaze B2, Wasabi, Cloudflare R2, MinIO, ArvanCloud's object storage…). New files go to the local disk first and are copied to the bucket; the local copies are cleaned up now and then, and fetched back from the bucket when needed.
Settings: from your storage provider's panel, after making a bucket:
- Bucket: its name.
- Region: e.g.
eu-central-1; some providers ignore it, but it can't be empty. - Endpoint URL: e.g.
https://s3.eu-central-1.wasabisys.com. - Access key ID and Secret access key: a key allowed to read and write that bucket.
After deploy: files already on the disk stay there. The playbook doc explains moving them to the bucket. Playbook doc
S3 via Goofys
Synapse only. Mounts the bucket as if it were Synapse's media folder. Simpler than the S3 storage provider, but slower; prefer that one.
Settings: Bucket, Access key, Secret key, Region, and, for anything that isn't AWS, tick Custom endpoint and give its Endpoint URL. Playbook doc
matrix-media-repo
Replaces the homeserver's media handling with a separate service that stores each file once even when it's sent many times, and can use several storage backends. Made for big servers or several homeservers sharing media; for one small server it's more than you need.
Settings: Datastore ID: made up for you.
After deploy: read the playbook doc before turning it on for a server that already has media; moving existing files over is a separate step. Playbook doc
Running out of space before you need any of this? Manage › Disk space shows what uses the disk and can delete old media cached from other servers.