Chrome Remote Desktop

Chrome Remote Desktop is Google’s free remote access service: a small host component on a Windows, macOS or Linux computer lets you reach that machine from a browser or the Android and iOS apps, signed in with your Google account. It suits home users, small offices and IT staff who need a quick, no-cost way to get to their own PCs or help someone once. The Chrome Remote Desktop download is free and there are no paid tiers; the host software is proprietary freeware from Google.

It covers two jobs. Remote Access sets up permanent, PIN-protected access to computers registered to your account. Remote Support creates a one-time access code so another person can see and control your screen while you watch. Everything else is deliberately minimal: there is no address book beyond your Google account, no session recording and no technician console.

Chrome Remote Desktop at a glance

What it does

• Unattended access to your own Windows, macOS and Linux machines, protected by a PIN of at least six digits.
• One-time Remote Support codes: the code works once, and the person sharing is asked to confirm again every 30 minutes.
• Browser-based client, so the controlling side needs nothing installed; Android and iOS apps for phones and tablets.
• File upload and download, clipboard sync and multi-monitor selection inside the session.
• Linux hosts start a separate virtual desktop session instead of mirroring the physical console.
• Encrypted sessions with peer-to-peer connections where the network allows, relayed otherwise.
• Chrome Enterprise policies to restrict or disable it on managed computers.

How IT teams use it

Set up a headless Linux server or VM

1. Install the official 64-bit Debian package and a lightweight desktop such as Xfce on the server.
2. On your own computer, open remotedesktop.google.com/headless, sign in and authorise; the page shows a one-time command.
3. Run it over SSH as the user who will own the session (the code is unique, do not reuse it):

   DISPLAY= /opt/google/chrome-remote-desktop/start-host 
       --code="4/xxxxxxxxxxxxxxxx" 
       --redirect-url="https://remotedesktop.google.com/_/oauthredirect" 
       --name=$(hostname)

4. Enter and confirm a PIN, then check the service:

   sudo systemctl status chrome-remote-desktop@$USER

5. If the session opens to a black screen, tell it which desktop to start by creating ~/.chrome-remote-desktop-session, for example:

   exec /etc/X11/Xsession 'gnome-session --session=cinnamon'

Help a user once with an access code

1. The user opens remotedesktop.google.com/support in Chrome, installs the host component if asked and selects Generate Code.
2. They read the code to you over the phone; you enter it in the section for connecting to another computer on the same page.
3. The user confirms the request, and you get the screen. The code expires after use, so nothing permanent stays on the account.

Lock it down on company machines

1. Allow only LAN or VPN connections by setting RemoteAccessHostFirewallTraversal to 0 (Windows registry under HKLMSoftwarePoliciesGoogleChrome).
2. Require company accounts with RemoteAccessHostDomainList, so hosts can only be registered to your Google Workspace domain.
3. Set RemoteAccessHostRequireCurtain to 1 to blank the physical screen and disable local input while someone is connected.
4. On Linux the same policies go into JSON files under /etc/opt/chrome/policies/managed/.

Install and first run

Windows. Open remotedesktop.google.com/access in Chrome, choose to set up remote access and install the host package. Installing needs administrator rights; after that a host service runs in the background and updates itself.

macOS. The host installer asks for Accessibility and Screen Recording permissions in System Settings → Privacy & Security. If you skip them, the remote side sees a blank screen or cannot click. To remove the host, run “Chrome Remote Desktop Host Uninstaller”.

Linux. Google supports the 64-bit Debian package on Debian and Ubuntu. It pulls in Xvfb and the dummy X driver because it runs its own virtual session; the physical desktop is not shared by default.

Network. Outbound UDP and its replies, TCP 443 and TCP/UDP 3478 (STUN) must be allowed. Restrictive firewalls force relayed connections, which work but feel slower. Antivirus or endpoint tools sometimes need an exception for the host process.

Limitations

• A Google account is mandatory, and the service depends on Google’s infrastructure; there is no self-hosted option.
• No technician console, groups, ticketing, session recording or audit reports, so it is not a help-desk tool for teams.
• Unattended access is meant for computers registered to your own account; you cannot manage other people’s machines centrally.
• Google publishes no changelog, and version numbers differ slightly between platforms.
• Linux hosts are officially packaged for Debian-based systems only, and the virtual session behaves differently from the local desktop.
• No unattended host for Android or iOS; mobile devices act only as clients.

Chrome Remote Desktop vs alternatives

AnyDesk and TeamViewer offer address books, session recording and team management, but both are free for personal use only. RustDesk is open source and can run on your own server, which suits organisations that do not want traffic or identity tied to Google. For a self-hosted browser gateway to RDP, VNC and SSH, look at Apache Guacamole.

FAQ

Is Chrome Remote Desktop free?

Yes. There is no paid edition and no restriction on business use; you only need a Google account.

Do I need the Chrome Remote Desktop extension?

The controlling side works from the website in a browser. The computer you want to reach needs the host component, which the site prompts you to install.

Can I use Chrome Remote Desktop on iPhone or Android?

Yes, the iOS and Android apps can connect to your computers. They cannot be controlled themselves.

Chrome Remote Desktop vs TeamViewer?

Chrome Remote Desktop is simpler and free for any use. TeamViewer adds device management, session recording and enterprise features, but its free tier is personal use only.

Chrome Remote Desktop vs Windows Remote Desktop (RDP)?

RDP needs a Pro or Server edition of Windows and a reachable port or VPN. Chrome Remote Desktop works on Home editions and through NAT without port forwarding, but with fewer features.

What is the Chrome Remote Desktop host?

It is the background service on the computer being accessed. It registers the machine to your account and accepts PIN-protected connections.

How do I uninstall it?

On Windows remove “Chrome Remote Desktop” under Programs in Control Panel; on macOS run the host uninstaller, then delete the computer from your device list on the website.

Last checked against official sources: 1 October 2026 (developer website: remotedesktop.google.com). Versions and licence terms change — confirm on the developer's site before deploying in production.