Skip to main content

Connect to your desktop

how-to · Reviewed 2026-07-30 · FEAT-0035 GA

Two ways in: the browser, which needs no setup, and the native client, which is faster. Start with the browser and switch to the client if the session feels slow.

Which to use​

In-browserNative client
SetupNoneInstall client, port 8443 must be open
LatencyUnder 100 ms typicalUnder 50 ms achievable
Image qualityLowerHigher
Multi-monitorLimitedGood
Network pathVia the Rescale platformDirect to the workstation

The performance difference comes from that last row. The browser routes through the platform; the client connects straight to the machine. The gap is widest when you and the workstation are close together but the platform isn't. A user in India on the EU platform running a workstation in India is sending browser traffic via Germany.

Connect in the browser​

Click Connect. It appears once the OS is installed and the runtime setup is done.

Classic UIConnect appears when the desktop is ready.

The desktop opens in a new tab. Closing the tab does not stop the workstation. It keeps running, and billing continues, until you suspend or stop it.

Connect with the native client​

You need TCP port 8443 open to the workstation. If your network blocks it, this method won't work and you'll need the browser.

  1. Open the dropdown next to Connect and choose Connect to Local Client.
  2. Download the DCV client for your operating system.
  3. Click Download File to get the session file.
  4. Click Generate Password.
  5. Open the session file and enter the password. It is case-sensitive.
Classic UI
Classic UI

Turn on QUIC for lower latency​

QUIC runs the display stream over UDP instead of TCP, cutting round-trip time and raising frame rate. It's only available in the native client: never in the browser.

  1. In the client, before connecting, open Connection Settings.
  2. On the Protocol tab, set the transport to Automatic or QUIC / UDP.

Automatic is the safer choice. It uses QUIC when available and falls back to TCP when not.

To confirm it's active in a live session, open Settings → Streaming Mode; the Protocol section reads QUIC / UDP.

Ports​

MethodPath
In-browserClient → 443/tcp → Platform → Workstation
Native clientClient → 8443/tcp → Workstation
Native client (QUIC)Client → 8443/udp → Workstation

If you can't connect​

Workstations are closed to inbound traffic by default. Access from your IP has to be allowed explicitly.

Add your IP range under Preferences → Job Settings, in the Access Restriction (CIDR) section. Enter comma-separated CIDR rules (x.x.x.x/32,y.y.y.y/32). The setting applies to both public and private IPs.

Changing your IP updates running workstations

If you move location and your IP changes, add the new CIDR rule. It automatically updates the ingress rules on everything you already have running. You don't need to relaunch.

Other things to check:

  • Port 8443 blocked — corporate networks often block it. Use the browser instead.
  • Password rejected — it's case-sensitive, and a new one is generated each time you click Generate Password. Use the most recent.
  • Session was working, now frozen — the workstation may be overloaded or unresponsive. See recovery.

Trading quality for responsiveness​

Both clients expose a streaming mode that prioritizes responsiveness over image quality. Worth switching when you're rotating a large model and care more about smooth motion than a crisp still. The native client also shows live latency diagnostics.