Transfer Data Paths and Temporary Storage

A file's final storage location and its transfer path answer different questions. The storage location identifies where the retained copy lives. The transfer path identifies which systems receive its contents while an operation runs, including any temporary copies needed for delivery or processing.

A Remote Server Mount leaves the authoritative files on the connected storage. Reading, previewing, copying, or processing those files can still move their contents through Files.com. A Sync creates a copy at its destination.

Native and Remote Storage Transfers

For Files.com Native Storage, supported clients use temporary transfer URLs to send or receive file contents directly from the storage service. Protocol connections such as SFTP pass file contents through Files.com's transfer services. Files.com authorizes the operation in either case; the route used to carry the file does not itself grant permission.

Transfers involving a Remote Server can stream through Files.com, use a supported direct connection, or first place an upload in Files.com Native Storage. The destination, client, and configured processing determine which path applies. A description of one upload path does not establish the path for downloads, previews, copies, or background workflows.

Buffered Uploads

Buffered Uploads temporarily stores the complete file in Files.com Native Storage before delivering it to a Remote Server. This allows Files.com to accept the upload independently of the destination's speed and retry onward delivery. Completion of the user's upload confirms receipt by Files.com; it does not confirm delivery to the remote destination.

Buffering depends on the Remote Server's settings and supported behavior. Configured file processing, including GPG encryption or decryption and Malware Scanning, can also require staging before delivery. The buffering setting therefore needs to be considered alongside the folder's processing settings when evaluating temporary storage.

Agent Transfers

The Files.com Agent receives file operations within your environment. Its ordinary transfer connection relays file contents through Files.com. Optional Direct Transfers lets supported clients send file contents directly to the Agent while Files.com continues to authorize the transfer. If a direct connection is unavailable, those clients use the ordinary route.

The Agent's default parallel uploads use a temporary cache on the Agent host before assembling the destination file. This local cache is separate from Files.com Native Storage buffering. Agent Storage Requirements explains its location, cleanup, and capacity requirements.

Geographic Requirements

The selected storage region does not, by itself, describe every connection or temporary processing location. Global Acceleration affects how users connect, and Remote Server and Agent settings affect other parts of the path. Regional Storage, Access, and Transmission explains the controls that apply to geographic requirements.

Copies Created for a Purpose

Temporary processing, retained copies, and completed deliveries have different lifetimes. A buffer exists to finish onward delivery. A snapshot exists to preserve a version for sharing. A quarantine copy exists to keep a flagged upload separate from the intended destination. Review the feature that creates the copy when establishing retention and geographic requirements.

Snapshots and quarantined files use the site's default storage region. They do not inherit another region from the original folder, and a separate regional-storage setting is not available for those copies. Disabling snapshot-based Share Links prevents new links of that type; it does not remove existing snapshots or revoke existing links.

Online document editing can require temporary processing in the United States during the editing session. Activity logs are also stored in the United States; some specialized logs, including AS2 message logs, can include payload contents. A review limited to a folder's retained storage region would omit those uses.

AI features can send prompts, file contents, and tool results to the providers used to perform the requested work. Connections to other services can likewise deliver copies outside Files.com. Include the operations you enable, their recipients, and their retention settings when deciding whether a workflow meets your requirements.

Access After Delivery

Files.com permissions authorize operations within Files.com. Once a file is delivered to another system or downloaded by a recipient, that copy is governed by the destination's controls. Revoking a Files.com account, Share Link, or connection prevents the applicable future access; it cannot retrieve completed downloads or remove independently retained copies.

For a workflow that needs a fixed recipient list or limited retention, configure the destination and delivery process accordingly. For a workflow that must keep content encrypted after it leaves Files.com, consider file encryption and key ownership alongside transfer protection.