Configuring Backblaze B2 with quickS3
Connect Backblaze B2 to quickS3 for secure team access to S3-compatible storage. Set up buckets, CORS, and browser uploads in minutes.
Backblaze B2 is a common pick for teams that want to cut storage costs but still trust their data to be there. Because it speaks the S3 API, connecting it to quickS3 takes a few minutes and gives your team scoped, role-based access to B2 buckets.
Why Backblaze B2?
The short version: it’s cheap. B2 storage and egress both run well below AWS S3, there’s no minimum fee so you only pay for what you use, and Backblaze quotes eleven nines of durability. And since it’s S3-compatible, it slots into the tools and workflows you already have.
Step 1: Create a B2 bucket
- Log in to your Backblaze account
- Go to “Buckets” in the sidebar
- Click “Create a Bucket”
- Pick a unique bucket name and your settings
Step 2: Generate application keys
B2 uses application keys rather than the access keys you’d use with AWS S3:
- Go to “App Keys” in the B2 dashboard
- Click “Add a New Application Key”
- Set the permissions:
- Name: something like “quickS3 access”
- Allow access to Bucket(s): select your bucket
- Type of Access: “Read and Write” for full access
- Copy the keyID and applicationKey now. You won’t see the key again.
Step 3: Connect to quickS3
- In quickS3, go to Storage Providers and click Add Provider.
- Select Backblaze B2.
- Fill in the form:
- Endpoint is your B2 S3-compatible endpoint (e.g.
https://s3.us-west-004.backblazeb2.com). Use the endpoint for the region where your bucket lives. - Bucket scopes (optional): leave this blank to let quickS3 list every bucket the key can reach, or enter a comma-separated list of bucket names.
- Key ID and Application key come from Step 2.
- Endpoint is your B2 S3-compatible endpoint (e.g.
- Leave Allow quickS3 to update bucket CORS settings (recommended) on. When you save or test the connection, quickS3 adds the quicks3.com origin to your B2 bucket’s CORS policy so browser uploads work.
quickS3 talks to the B2 S3-compatible API, so you don’t need to touch CORS by hand unless you turn off auto-update.
Cost comparison
Here’s roughly what a month of 1 TB storage plus 1 TB egress costs:
| Provider | Storage | Egress | Total |
|---|---|---|---|
| AWS S3 | ~$23 | ~$90 | ~$113 |
| Backblaze B2 | ~$6 | ~$10 | ~$16 |
Prices as of 2025 and subject to change
The B2 S3-compatible API
quickS3 connects through B2’s S3-compatible endpoint, e.g. s3.us-west-000.backblazeb2.com.
If something isn’t working, check that:
- Your bucket name has no uppercase letters or special characters
- Your application key has the right permissions and bucket access
- You’re using the correct endpoint URL for your bucket’s region
Lifecycle rules
B2 supports lifecycle rules much like S3 does, so you can auto-delete files after a set time, move them to cold storage, or turn on automatic versioning. Set these up in the B2 dashboard and quickS3 will respect them.
Looking to cut your storage costs? Sign up for quickS3 and connect your B2 bucket.
Read next
Configuring Cloudflare R2 with quickS3
Cloudflare R2 is S3-compatible object storage with simple pricing. Create an R2 token, connect it to quickS3, and use auto CORS so browser uploads work.
Getting Started with AWS S3 and quickS3
Connect AWS S3 to quickS3 for secure team file access without IAM complexity. Configure buckets, roles, and browser uploads in minutes.
Using Wasabi with quickS3 for Cost-Effective Storage
Wasabi offers no egress fees and flat-rate pricing. Connect Wasabi to quickS3 for secure team access, browser uploads, and predictable storage costs.