Skip to documentation
quickS3.comOpen app
Browse documentation
Reference

Supported providers

Setup inputs and verified capabilities across all eight storage providers, including which ones support multipart uploads and bucket creation.

OwnerAdminMember

All eight providers support listing, browsing, direct single-part upload, preview, download, delete, and CORS inspection and update, wherever the stored provider credential permits.

Provider API and endpoint input Multipart Create storage in quickS3 Creation permission or limitation
AWS S3 S3; region and endpoint Yes Yes s3:CreateBucket
Azure Blob Storage Azure Blob; endpoint from account name No Container Storage account key with container write access
Backblaze B2 S3-compatible; paste regional endpoint Yes Yes Application key with writeBuckets
Cloudflare R2 S3-compatible; endpoint from account ID and jurisdiction Yes Yes R2 Admin Read & Write token
DigitalOcean Spaces S3-compatible; endpoint from region Yes Yes Key with access to all Spaces, not a per-Space limited key
Google Cloud Storage XML/S3 interoperability; endpoint and HMAC keys Yes No Create in Google Cloud, then refresh
MinIO S3-compatible; paste reachable HTTPS endpoint Yes Yes Provider-equivalent create permission
Wasabi S3-compatible; endpoint from region Yes Yes Provider-equivalent create permission

“Yes” for multipart means the browser implementation is verified for that provider and engages automatically at 256 MiB. It never overrides the connection’s configured cap or the provider’s own object-size, part, quota, and rate limits.

Choosing between similar providers

Decide on the things quickS3 does not change: where the data must live, provider account controls, egress and request pricing, recovery features, and whether the browser can reach the endpoint at all. quickS3 makes the file workflow identical; it does not make durability, versioning, retention, or billing equivalent.

For private or self-hosted MinIO, remember the endpoint must be reachable by quickS3’s Cloudflare Worker for metadata and signing. A hostname that only resolves on your laptop will not work in hosted quickS3.