A Filebase connection makes a bucket available through Files.com's accounts, folder permissions, client apps, and file workflows. Files.com connects to Filebase over HTTPS using the bucket name and an Access Key and Secret.

Use a Mount when the bucket should remain the working location for people or applications. Use a Sync when another location needs its own delivered copy.

Connection Details

Select Filebase when adding a Remote Server. Give it an identifiable Internal name for this connection.

The Bucket is the name shown under Buckets in the Filebase portal. The Access Key and corresponding Secret are shown under Access Keys. Enter the credentials directly or select a saved credential from the Remote Server Credential Manager.

The connection's credentials determine its rights on Filebase. Files.com folder permissions separately determine which people can use a mounted bucket and which operations they may perform through Files.com.

Transfers and Object Names

Eligible client uploads and downloads use Direct Routing automatically. Directly transferred contents avoid Files.com's network and Transfer Usage. Web uploads relay through Files.com; buffering and required processing can also change how uploads are delivered.

Filebase object names are case-sensitive. Before copying or syncing to a case-insensitive destination, resolve names that differ only by capitalization to avoid overwrites or merged folders. Object Storage Behavior explains the prefix-based folder view and the consequences of renaming, replacing, or deleting objects.