A Backblaze B2 connection makes a bucket available through Files.com's apps, protocols, permissions, and workflows. Files.com connects through Backblaze's S3-compatible interface using an Access Key and Secret Key.

Backblaze retains previous file versions by default. Removing a file from the current Files.com view therefore does not necessarily remove every stored version or stop its storage charges. Include Backblaze lifecycle rules in the connection's recovery and retention plan.

Bucket and Credentials

Select Backblaze B2 Cloud Storage when adding a Remote Server. Give it an identifiable Internal name for this connection and select the bucket the workflow will use.

Use credentials created for Backblaze's S3-compatible API. Enter the Access Key and Secret Key directly or select them from the Remote Server Credential Manager. Grant the key the access required for the work: reading a source, writing deliveries, and replacing or deleting files are different operations.

After connecting, use Browse to inspect the bucket. A Mount exposes the remote contents as a Files.com folder; a Sync transfers a separate copy to its destination.

Transfers and Recovery

Eligible client uploads and downloads use Direct Routing automatically. Those directly transferred contents avoid Files.com's network and Transfer Usage. Web uploads relay through Files.com; required processing and buffering can also change the upload path.

B2 object names are case-sensitive. When another storage location treats capitalization as equivalent, names that are distinct in B2 can overwrite one another or merge into the same folder. Review case sensitivity before a transfer between those systems.

Files.com's regular listing shows current files. Use Backblaze's tools to inspect retained versions and its lifecycle rules to control how long they remain. Object Storage Behavior explains how folder markers, deletions, replacements, and copy-and-delete moves affect that stored content.