Turbo Transfer Mode
Turbo Transfer Mode is the Files.com Desktop App's high-throughput interface for uploading and downloading large files. Use it when transfer speed matters more than working with files in place through a mount.
On Windows, launch it from the system tray Files.com menu or by searching for "Files.com Desktop" in the Start menu. On macOS, launch it from the menu bar Files.com icon, or by opening the Files.com Desktop app from Applications or via Spotlight search.
The interface uses drag-and-drop, with the local file system in the left pane and Files.com content in the right pane. You can upload, download, create folders, and rename, delete, move, or copy files directly from the interface.
Transfers can be paused or canceled at any time. The transfers pane groups files into In Progress Transfers, Successful Transfers, and Failed Transfers so you can distinguish active work from files that finished or need attention.
Overwrite options are configured in Settings or Preferences.
Right-clicking a file or folder in the Files.com pane also offers Create Share Link, which builds a Share Link for it without the need to open the web app. More detail on this feature can be found on the Creating Share Links from the Desktop App page.
Network Interruptions
If your computer loses its network connection during an upload or download, the transfer can remain in In Progress Transfers while the app waits for a network operation to finish or report an error. Progress can stop changing during this time. If connectivity returns while the transfer or its automatic retries are still active, data can continue moving without a manual step.
Recovery depends on when connectivity returns and which part of the transfer was interrupted. An active upload can reuse completed parts, and an active download can retry an interrupted part.
If a download fails at the file level, its partial local file is discarded and the next file attempt starts over. A persistent interruption can exhaust the available attempts and leave files in Failed Transfers.
Automatic Retries
The Automatically retry failures? setting is available in Settings on Windows and Preferences on macOS. It defaults to On. With it enabled, the app makes up to two additional attempts for unfinished files after the initial transfer pass finishes. For a folder or batch, files that completed successfully are excluded from these retries.
These are additional file attempts, not a limit of three network requests. Each attempt can involve multiple requests, including retries of individual requests or file parts. Setting the option to Off disables the additional file attempts; individual request or part retries can still occur within an active transfer.
Automatic retries give a temporary connection problem another chance to recover. They are limited attempts, rather than a queue that restarts failed files whenever your computer reconnects. The setting does not change connection timeouts or restart files whose automatic processing has already finished.
Connection Timeouts
The Desktop App has separate limits for stages of a standard HTTPS connection. There is no single fixed timeout measured from the moment your computer loses connectivity.
| Connection Stage | Timeout |
|---|---|
| Opening a connection | 30 seconds |
| Establishing the encrypted TLS connection | 10 seconds |
| Waiting for the server's response headers after the request, including any uploaded data, finishes sending | 60 seconds |
These limits apply to individual connection stages, not the total duration of a file transfer. The response-header limit also does not cover the time spent reading downloaded data.
A connection already sending or receiving file data can take a different amount of time to report an interruption, depending on the network and the storage service. Further attempts can add to the time before the app finishes processing the file, so a stalled progress bar does not imply a particular countdown to failure.
Failed Transfers and Manual Retry
Failed Transfers shows files whose attempts reported an error, along with the reason. An entry can return to In Progress Transfers when an automatic retry gets the file moving again. Once the app finishes its available attempts without success, the file remains failed. Restoring your network connection does not automatically restart it.
To retry files after connectivity returns:
- Open Failed Transfers and select the files you want to transfer again.
- Right-click the selection and choose Retry.
- Check In Progress Transfers for the new attempts and Successful Transfers for files that finish.
Manual Retry starts the selected failed file from the beginning, for both uploads and downloads. It creates a new transfer using your retry and overwrite settings. For a folder or batch, select the failed file entries; files that already completed do not need to be transferred again. If a retry fails again, its reason remains available in Failed Transfers.
Pause and Resume Transfers
Turbo Transfer Mode supports pausing and resuming file uploads and downloads. While transfers are active, pause or resume them from the bottom right of the app. The right-click context menu on active transfers provides a Process Queue option for managing transfers.
Pausing deliberately saves transfer progress so you can continue the work later. Paused transfers remain visible in the Transfers tab, and they persist even if the app is quit and relaunched. After relaunch, click Resume Transfers to finish the remaining transfers. This differs from manually retrying a failed file, which creates a new transfer.
The recovery method determines which data is reused:
| Recovery Method | Uploads | Downloads |
|---|---|---|
| Automatic retry after a file attempt fails | Reuses completed parts while the upload remains resumable. An incomplete part is transferred again. | Starts the file over. Individual part retries within an active download can preserve the other completed parts. |
| Retry from Failed Transfers | Starts the selected failed file over. | Starts the selected failed file over. |
| Pause, then Resume Transfers | Continues using completed upload parts. | Continues from the data preserved in the partial local file. |
For folder transfers, files already completed before the pause are not transferred again. If you know you need to interrupt a large transfer, pause it while connectivity is still available so the app can save its progress for resume.
A request to sign in again follows the expired-credentials recovery process: active transfers pause and resume after you sign in. That saved-state recovery is separate from retrying a file that failed because of a network interruption.