Files.com connects a Wasabi bucket to your file workflows through Wasabi's S3-compatible interface. Buckets in any Wasabi region are supported. This lets an organization retain its Wasabi storage while giving staff, partners, and applications access through Files.com.

A Mount presents the bucket's files as a Files.com folder. A Sync transfers files between the bucket and another location. Choose between access to the existing files and a separate delivered copy before setting up the workflow.

Bucket and Authentication

Select Wasabi when adding a Remote Server. Give the connection an identifiable internal name and provide the bucket and its region.

Files.com authenticates with an Access Key and Secret Key. Enter them directly or select a saved credential from the Remote Server Credential Manager. The connection requires access to the selected bucket; its remote permissions must cover the operations your workflow performs.

Transfers and Retained Versions

Eligible client uploads and downloads use Direct Routing automatically, so their contents avoid Files.com's network and Transfer Usage. Web uploads use Files.com's network. Keep clients current and account for required processing and buffering when assessing the route.

Wasabi supports object versioning. When enabled, earlier versions can remain after replacement or deletion even though Files.com's regular listing shows only current files. Use Wasabi's version and lifecycle controls to manage recovery and retained storage.

Wasabi object names are case-sensitive. Names that differ only by capitalization can collide when copied to a case-insensitive location. Object Storage Behavior explains the folder view, copy-and-delete moves, and why content can remain under old paths after a successful move.