Capme
All help articles
Your videos

Connect your own bucket

Keep recordings in an S3 bucket your company controls: which providers work, what to set on the bucket, and what Capme deletes there.

Updated September 28, 2026

Your own bucket is part of Business and Enterprise, and of the Business trial. The workspace owner sets it up under Data, in the Storage section. Where your videos live explains what changes once you use one.

Which providers work

Amazon S3, Hetzner Object Storage, Cloudflare R2, DigitalOcean Spaces. The endpoint has to use https. We check every video address against a fixed list of hosts, so another provider needs a change on our side first. Write to us if you need one.

What to enter

  • Endpoint, region and bucketFrom your provider. Leave the region on auto if your provider has no regions.
  • Path prefixThe folder Capme writes into. Each recording is saved there as a video file with a still image next to it.
  • Access key ID and secret access keyA key that may read, write and delete in that bucket. The secret is encrypted before it is stored and never shown again.
  • Public base URLOnly for a public bucket. Leave it empty and Capme signs every playback link instead.
  • Path-style addressingTurn it on for Hetzner. AWS doesn't need it.

Set the CORS policy

Browsers upload to your bucket and play from it directly, so the bucket has to allow requests from Capme. The Storage section shows the policy under Bucket CORS, with Capme's address already filled in. Copy it into your bucket's CORS settings as it is.

Keep the ETag header in the list of exposed headers. Uploads fail without it.

Test, then save

Press Test connection. Capme then tries four things in order:

  1. Reach the bucket.
  2. Write a small test file.
  3. Read it back through a signed link.
  4. Delete it again.

You can save once the test passes; if you changed the connection details, Capme runs it once more when you save. The test runs on our server, so it can't check CORS. If the test passes and uploads still fail, look at the CORS policy first.

What Capme deletes in your bucket

Capme deletes a recording's files from your bucket in one case: someone deletes that recording in Capme. If the bucket can't be reached at that moment, Capme tries again on a later night.

Capme leaves everything else alone. That includes old recordings, a take someone recorded again, and every file in the bucket after the workspace is deleted.

Let old recordings expire

If recordings should go after a while, set a lifecycle rule on the bucket. The Storage section has an example under Retention in your bucket that deletes files after 365 days. Change the number to suit you.

Capme checks every night for recordings whose file is gone and takes them out of their meetings the night after. If a lot of files disappear at once, Capme changes nothing and our team looks at it first, in case the bucket was emptied by mistake.

The workspace owner also sees files in the prefix that no recording points to. Capme only lists them. Whether they go is up to you.

Going back to Capme hosting

Pick Capme video hosting in the Storage section and save. New recordings then go to Capme. The bucket settings and the key stay saved so the videos in your bucket keep playing. Capme deletes the settings and the key when the workspace is deleted; the files stay in your bucket.

Still stuck? Write to hello@capme.app.

Related articles

Connect your own bucket | Capme