Backblaze B2 client for Mac
Use Blob0 on Mac as an S3-compatible object client for an existing Backblaze B2 bucket—not Backblaze Computer Backup. Match the bucket’s regional endpoint, region, and application-key capabilities.
Connect Blob0 to an existing B2 bucket through Backblaze’s S3-compatible endpoint. Use an application key you created for S3 access; the automatically created master app key is not supported. Blob0 is for bucket object work, not computer backups.
macOS 11.0+ · one universal app for Apple silicon and Intel Macs
Try every Blob0 feature for 30 days. No Blob0 account or payment details are required to start.
Connect an existing Backblaze B2 bucket
Copy the regional S3 endpoint and region from the bucket details in B2. For example, a bucket in us-west-004 uses https://s3.us-west-004.backblazeb2.com; use the values shown for your own bucket.
Match the bucket’s regional endpoint
Use the endpoint and region from this B2 bucket’s details. The us-west-004 example is https://s3.us-west-004.backblazeb2.com; do not reuse it for buckets in other regions. Enter the bucket name separately.
Create an S3-compatible application key
Create an application key manually. Map its keyID to Access Key ID and its applicationKey to Secret Access Key. Backblaze’s automatically created master app key cannot authenticate to the S3-compatible API.
Grant only the needed B2 capabilities
listFiles lists objects, readFiles reads and downloads, and writeFiles uploads; B2 maps Copy Object to both readFiles and writeFiles, so rename or move workflows may need both. Delete by name requires writeFiles and deleting a specific version requires deleteFiles; Backblaze generally recommends both for Delete Object workflows. Blob0 deletes by object key without a version ID, so it does not delete a selected historical version.
Keep bucket discovery scoped
Backblaze recommends enabling listAllBucketNames for bucket-restricted application keys when SDKs or integrations call ListBuckets. It exposes bucket names, not object access to other buckets. Blob0 asks for a specific bucket and does not show every bucket in the account; if region probing or permissions fail, check Backblaze’s capability map for ListBuckets and HeadBucket.
B2 application-key capabilities are not a promise of full AWS IAM or ACL compatibility. Blob0 works with the S3-compatible object operations supported by B2 and the key you provide.
Backblaze B2 S3-compatible application keysBackblaze B2 S3-compatible API detailsWork with B2 objects from your Mac
Use the B2 S3-compatible connection for everyday object tasks in the bucket you selected.
Review an export
Browse a prefix, filter listed objects, preview a supported file, and download the selected export to your Mac.
Upload a revised package
Upload a replacement asset package and follow transfer progress. Rename or move objects inside the same connected bucket when you need to reorganize keys.
Share a temporary download
Choose Share… → Presigned on an object to create a time-limited GET link for a recipient who can reach the B2 endpoint.
Know the Backblaze B2 client boundaries
- Blob0 is an S3-compatible object client, not Backblaze Computer Backup and not an AWS account console. B2 documents a defined S3-compatible API surface; do not assume every AWS IAM or ACL feature applies.
- A B2 S3 delete by object name adds a delete marker. Blob0 sends the object key without a version ID, so deleting from the current list does not remove a selected historical version or clear version history; manage versions and lifecycle rules in B2.
- Blob0 connects to the bucket you specify; it does not list or administer every bucket in the Backblaze account.
Install Blob0 and connect a B2 bucket
Prepare the bucket’s endpoint and region, create a suitable application key, then download Blob0 and follow the macOS installation steps. The connection form uses the exact bucket and key pair you provide.