BucketMate
Features

Connect S3-compatible storage

Add AWS S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, and other S3-compatible providers to BucketMate Web with endpoints, access keys, and CORS.

BucketMate Web connects to S3-compatible storage with an endpoint, region, access key ID, secret access key, and optional explicit bucket names.

Browser extension

Install and connect the BucketMate Proxy extension before testing a connection. BucketMate Web sends every S3 request through the extension. See Browser extension.

Supported providers

The Provider list includes:

  • Amazon S3
  • Google Cloud Storage
  • Cloudflare R2
  • Backblaze B2
  • DigitalOcean Spaces
  • Wasabi
  • Supabase Storage
  • Hetzner Object Storage
  • Tigris
  • MinIO
  • Custom S3-compatible

Use Custom S3-compatible for any other endpoint that supports S3 Signature Version 4.

Connection fields

FieldHow to use it
Connection nameOptional label shown in the sidebar. If you leave it empty, BucketMate Web names it after the provider and the current date and time.
ProviderSelect the closest provider. The provider sets the default region list.
Endpoint URLRequired for every provider except Amazon S3. If you omit https://, BucketMate Web adds it.
Use virtual-hosted styleShown for MinIO and Custom S3-compatible. Puts the bucket name in the hostname instead of the path. See Virtual-hosted style.
Access key IDProvider access key, HMAC key, application key ID, or token access key.
Secret access keyMatching secret for the access key. Use the eye icon to show or hide it.
RegionPick a preset region, or choose Custom... and type one.
Explicit bucketsOptional bucket names when credentials cannot list all buckets.
Store as encrypted valuesOptional passkey protection for the access key ID and secret access key.

General connection steps

  1. Open BucketMate Web.
  2. Make sure the extension shows Connected in Settings > Advance.
  3. Choose Add connection in the sidebar.
  4. Select the provider.
  5. Enter the endpoint URL, access key ID, secret access key, and region.
  6. Add explicit bucket names if bucket listing is not allowed.
  7. Choose whether to store credentials as encrypted values.
  8. Use Test Connection.
  9. Choose Save Connection.
  10. Expand the connection in the sidebar and select a bucket.

Test Connection lists buckets with your credentials. If you entered explicit buckets, it lists objects in the first bucket instead.

Edit or remove a connection

  • Use the settings icon next to a connection, or right-click it and choose Edit connection.
  • Right-click a connection and choose Remove connection to delete its saved credentials and cached folder data from this browser. Your buckets and files are not deleted.

Explicit bucket names

Some credentials can access objects inside a bucket but cannot list all buckets in the account. BucketMate Web supports this setup.

  1. Enter bucket names in Explicit buckets, one per line. Commas and spaces also separate names.
  2. Test the connection.
  3. Save the connection.

BucketMate Web shows only the buckets you entered.

Passkey encryption

Turn on Store as encrypted values to protect saved credentials with a passkey.

  1. Check Store as encrypted values.
  2. In Enable credential encryption, choose Create new passkey.
  3. Complete the passkey prompt with Touch ID, Face ID, Windows Hello, or a security key.
  4. Choose Save Connection.

How it works:

  • The access key ID and secret access key are encrypted with AES-GCM. The key comes from your passkey through the WebAuthn PRF extension and never leaves your device.
  • The endpoint, region, and bucket names are stored unencrypted.
  • All encrypted connections in the browser share the same passkey. To use a new passkey, select the trash icon next to the passkey name in the connection dialog.
  • When you open an encrypted connection, BucketMate Web shows Decrypt connection. Choose Decrypt and confirm with your passkey.
  • Decrypted values stay in memory until you lock the connection or reload the page. Lock connections from Settings > General > Passkey encryption.

Passkey encryption requires HTTPS or localhost and a browser and authenticator that support WebAuthn PRF. If your passkey provider does not support it, save the connection without encrypted storage.

Endpoint examples

ProviderEndpoint
AWS S3Leave empty, or use https://s3.<region>.amazonaws.com
Google Cloud Storagehttps://storage.googleapis.com
Cloudflare R2https://<account-id>.r2.cloudflarestorage.com
Backblaze B2https://s3.<region>.backblazeb2.com
DigitalOcean Spaceshttps://<region>.digitaloceanspaces.com
Wasabihttps://s3.<region>.wasabisys.com
Supabase Storagehttps://<project-ref>.storage.supabase.co/storage/v1/s3
Hetzner Object Storagehttps://<location>.your-objectstorage.com
Tigrishttps://t3.storage.dev
MinIOhttp://localhost:9000 or https://<your-minio-endpoint>

BucketMate Web uses path-style requests, such as https://<endpoint>/<bucket>/<key>, unless you turn on Use virtual-hosted style. Tigris endpoints always use virtual-hosted style.

Virtual-hosted style

S3 requests can address a bucket in two ways:

StyleRequest URL
Path-stylehttps://storage.example.com/my-bucket/photo.jpg
Virtual-hosted stylehttps://my-bucket.storage.example.com/photo.jpg

BucketMate uses path-style for custom endpoints by default. Most S3-compatible servers accept it, and it works without wildcard DNS or certificates.

Some providers accept only virtual-hosted style. They reject path-style requests with errors such as SecondLevelDomainForbidden, Please use virtual hosted style, or 403 Access denied. Alibaba Cloud OSS is one example.

To use virtual-hosted style:

  1. Select MinIO or Custom S3-compatible as the provider.
  2. Enter the endpoint without a bucket name, such as https://oss-ap-southeast-1.aliyuncs.com.
  3. Turn on Use virtual-hosted style.
  4. Test the connection.

Turn it on only when your provider requires it:

  • Your provider's DNS and TLS certificate must cover <bucket>.<endpoint host>. Some providers, such as Hetzner, issue certificates that do not cover bucket subdomains, so keep the option off for them.
  • Bucket names that contain dots may fail over HTTPS because they do not match a wildcard certificate.
  • For self-hosted MinIO, set MINIO_DOMAIN on the server first.

Copied object URLs follow the style you choose.

Troubleshooting

Extension is disconnected

Install or enable BucketMate Proxy, refresh BucketMate Web, and check Settings > Advance.

Test Connection fails

Check that the endpoint is correct, the region matches the bucket, the extension is connected, and the access key has permission for the bucket you are testing.

Buckets do not appear

If credentials cannot call ListBuckets, enter bucket names in Explicit buckets. When a connection has no buckets, BucketMate Web shows that bucket listing may be missing.

Provider rejects path-style requests

If the test fails with SecondLevelDomainForbidden or a message asking for virtual hosted style, turn on Use virtual-hosted style. See Virtual-hosted style.

Cloudflare R2 region fails

Use auto for Cloudflare R2.

Passkey setup fails

Use a browser and passkey provider that support WebAuthn PRF, or turn off Store as encrypted values.

Trial limit appears when adding a connection

The free trial allows one connection across all workspaces. Activate Pro to add more. See License and billing.