Zum Hauptinhalt springen
This page is not translated yet. Deutsch is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.

Transfer Manager

concept · Reviewed 2026-07-31 · FEAT-0027 GA

The Rescale Transfer Manager (RTM) moves large datasets between your machine and Rescale Files. Use it whenever you're moving more than a few gigabytes, pulling from several jobs, or on a connection that drops.

Windows only

RTM is a native Windows application. On macOS and Linux use the Rescale CLI, which covers the same bulk-transfer ground.

Why not just use the browser​

BrowserRTM
Resumes after an interruptionNoYes
Parallel connectionsNoYes
Filter by patternNoYes, substring or regex
Preserves folder structureNo, flattensYes
Download on job completionNoYes, automatically

A browser download of a large file has no resume: an interruption at 90% means starting over.

Set up​

  1. Get an API key. In the platform, open Preferences > API and click Add API Key. You can hold several keys, and each has an expiration date: see account setup.
  2. Install. On the same page, under Rescale Transfer Manager, click Click to install and run the downloaded setup.exe.
  3. Configure on first launch. In the Get Started window, select the platform region matching your account, paste the API key, and click OK.
Select the right region

If RTM points at the wrong region, your key fails with Invalid API Key even though the key is perfectly valid. This is the most common setup problem.

RegionPlatform
United States (commercial)platform.rescale.com
Europeeu.rescale.com
Japanplatform.rescale.jp
Koreakr.rescale.com
ITARitar.rescale.com
Pick your platform to see just your values, here and across the docs:

Network access it needs​

RTM talks to both the platform and the object storage behind it. Your machine needs egress to:

  • *.rescale.com plus your region's host from the table above.
  • The object storage endpoints — *.s3.amazonaws.com and regional S3 hosts, FIPS variants such as *.s3-fips.us-east-1.amazonaws.com, *.storage.azure.com, *.storage.azure.net, *.blob.core.windows.net, and storage.googleapis.com.

A firewall blocking any of these produces TLS or connection errors rather than a clear message. See troubleshooting.

Next​