Connect Wasabi with Blob0

Connect Blob0 to an existing Wasabi bucket with its region-specific S3 service URL and scoped access keys. Test listing access, save the profile, and check retention or Object Lock before changing protected objects.

Use this guide for an existing Wasabi bucket. The region, S3 service URL and access-key policy must match that bucket; Blob0 manages objects through the S3 API, not the Wasabi Console.

Download and installation guide

Before you connect

Have an existing Wasabi bucket, its region-specific S3 service URL, and a key pair scoped to the bucket and the actions you need. The key must be allowed to list the bucket root for Test connection.
Leave the optional Public / custom domain field blank unless a direct-link domain has already been configured. See Provider configuration notes below for region and retention details.

Provider configuration notes

Use the region and service URL shown for your bucket. For example, us-east-1 uses https://s3.us-east-1.wasabisys.com; the preset’s us-east-1 value is a starting point, not a match for every bucket.

Match the bucket region and S3 service URL: Copy the region and service URL for the bucket. The us-east-1 example is https://s3.us-east-1.wasabisys.com; replace it when the bucket is elsewhere. https://console.wasabisys.com is a Wasabi Console address, not the object endpoint.
Use scoped Access Key and Secret Key credentials: Enter the Access Key ID and Secret Access Key issued for your Wasabi account. Scope the key policy to the bucket and object actions needed for your workflow. Blob0 stores storage credentials in the macOS Keychain.
Check retention before replacing or deleting: If an overwrite or delete is denied, check the key permissions and the bucket’s retention or Object Lock settings. Blob0 does not request a retention bypass; active retention and compliance rules can restrict object operations.

Use the S3 service endpoint from the Wasabi region documentation. Do not enter the Console URL in the endpoint field.

Provider-specific limits

Blob0 is an independent Mac S3 object client for Wasabi storage, not a Wasabi Explorer installer or an account-management tool. Manage account settings and bucket policies in Wasabi’s own management tools.
Object operations remain subject to the access key policy and bucket retention or Object Lock rules. Blob0 will not bypass an active preservation policy.
A presigned GET URL is temporary access to an object, not a transfer of the account’s credentials or a Wasabi account-management action.

Fill in the Blob0 connection form

On first launch, use the connection form. To add another bucket later, open Settings → Connections → Add connection. Choose Wasabi under Provider and enter the service URL and Region for the same bucket. Do not use the Wasabi Console URL as an S3 endpoint.

Fill in the Blob0 connection form
App field	What to enter
Provider	Wasabi
Connection name	A local label, such as Wasabi projects. It does not rename the bucket.
S3 API endpoint	The service URL for the bucket’s region. Example: https://s3.us-east-1.wasabisys.com.
Bucket	The exact existing bucket name, without a URL or folder prefix.
Region	The bucket’s actual region, such as us-east-1 for the example endpoint above.
Access Key ID	The Access Key ID issued for this Wasabi account and bucket policy.
Secret Access Key	The matching Secret Access Key. Enter it only in Blob0; it is stored in macOS Keychain.
Public / custom domain	Optional. Leave blank for private access; this field does not authenticate the S3 connection.

Blob0 connection form with fictional settings: Connect Wasabi with Blob0 — Real application interface with fictional settings; no usable credentials are shown.

Test and save the connection

Test connection
Select Test connection. Blob0 lists the selected bucket at its root and may show 0 items for an empty bucket. A successful result confirms only that this listing request succeeded; it does not prove access to object contents or permission to upload, overwrite, or delete.
A successful bucket listing does not confirm access to object contents or upload and delete permission. Retention and Object Lock can also prevent overwrites or deletion even when the key has the related S3 permission.
Add connection
After the test succeeds, select Add connection to save the profile and connect. Blob0 stores access keys in the macOS Keychain; the profile keeps non-sensitive connection details.

Optional: verify an authorized transfer

Only if the bucket owner has authorized write testing, upload a tiny temporary file under a new test name, download it and compare its contents, then delete that exact test object. Check the bucket policy and retention rules first; never use an existing object as the test file.

Troubleshooting

AccessDenied: Confirm the key can list the bucket root and that its policy covers the selected bucket. Check retention or Object Lock if a protected object cannot be overwritten or deleted.
Wrong region or redirect: Use the Wasabi S3 service URL and Region assigned to this bucket. The us-east-1 URL is not a universal endpoint.
Console URL entered as endpoint: Replace the Console URL with the S3 service URL for the bucket’s region. The Console manages the account; the service URL handles object API requests.
SignatureDoesNotMatch: Verify the Access Key ID and Secret Access Key are a matching pair, then check the endpoint, Region and Mac clock.
Overwrite or delete is denied: Check the access-key policy and the bucket’s retention or Object Lock mode and expiry. Blob0 does not bypass an active preservation rule.

Continue with Blob0

See product workflows Share a file with a presigned URL Download and installation guide Browse all storage guides