
Connecting B2 to file.rocks is the same idea as S3 or R2, with a different console. You make a bucket, mint an application key, and paste five fields.
If you already have a bucket and just want cheap storage math, see the cheapest cloud object storage comparison. This post is how you hook B2 into file.rocks so you can browse and upload without living in the Backblaze dashboard.
Open Backblaze, go to B2 Cloud Storage, then Buckets.
Click Create a Bucket. Give it a name you'll recognize later.
Copy the bucket name. You'll paste it into file.rocks in a minute.

B2's master key does not work with the S3-compatible API. You must create an application key.
Go to Application Keys and click Add a New Application Key. Set:

Backblaze shows the applicationKey once. Copy keyID and applicationKey. If you lose the secret you make a new key.

Your S3-compatible endpoint looks like this:
https://s3.<region>.backblazeb2.com
It is on the bucket card in Buckets. Example from a real bucket: s3.us-east-005.backblazeb2.com, so region is us-east-005. Prefix with https://.

Go to file.rocks, sign in, and click Add a Bucket.
Choose Bring Your Own, then Backblaze B2. Paste:
Save. You should see the bucket in the list.

If you've connected S3 or R2 before, this form is the same one. The Amazon S3 guide and Cloudflare R2 guide walk those paths. B2 just swaps the endpoint and uses an application key instead of a master key.
Open Files and drop something in. If it lands, you're done. file.rocks is the UI now. Backblaze still holds the objects.

Want to compare storage prices across providers? See Cheapest cloud object storage. Don't redo the key work.