Chrome Remote Desktop shares control of your computer through a temporary support code and your approval. Use its Remote Support page for hands-on help, or your meeting app's screen-sharing control when people only need to watch.
The choice matters because remote support gives access to apps and files, while presenting a tab or window lets people see what you choose. Choose based on how much access the other person needs.
In this guide
Choose between remote control and a presentation
Use Chrome Remote Desktop > Remote Support when someone needs to move the pointer, change a setting, or work in an app on your computer. This is the temporary, code-based option for helping another person.

Use Present now in Google Meet to show a document, demonstrate a website, or play a video during a call. The audience sees the selected tab, window, or screen; presenting doesn't itself hand over keyboard and mouse control.
Use Remote Access when you want ongoing access to your own computer, such as reaching a home PC while away. That setup uses a computer name and PIN, rather than the one-time support code intended for someone helping you.
Windows and Mac computers can host Chrome Remote Desktop. Linux needs its compatible host package and desktop-session setup. Follow the Linux section of the instructions rather than copying Windows installation steps.
For Mac-only alternatives, our Mac desktop sharing guide covers the built-in choices. The Chrome route is useful when the two people use different desktop operating systems.
Prepare the computer that will be controlled
Sit at the computer you want to share, open Chrome, and visit remotedesktop.google.com/support. Sign in if prompted. Under Get Support, use the download control and follow the prompts to install the Chrome Remote Desktop host.
Google's Remote Desktop instructions explain the supported platforms and the installation prompts. The host is the software that lets the other person connect to this computer. Opening the web page alone isn't enough.
Windows can request permission to install the downloaded component. A Mac can request the computer password and permissions in system settings. Finish those prompts on the computer you're sharing before generating the support code.
On current macOS, follow the installer's permission requests in System Settings > Privacy & Security. Older versions put these controls in System Preferences > Security & Privacy.
Only share with someone you trust to work in your account. A support session can expose files, email, browsing history, and open applications. Close anything private and stay at the computer while the other person works.
If installation is blocked on a managed computer, ask its IT team whether they permit Chrome Remote Desktop. An organization can restrict remote tools, and a personal browser setting won't override that policy.
Generate a code and approve the helper
Once installation is complete, return to Get Support and select Generate Code. Copy the access code and send it directly to the person you've chosen to help. Keep that page open while they connect.
On their computer, the helper opens remotedesktop.google.com/support, enters the code under Give Support, and selects Connect. They need this session's support code, rather than your Google password or an ongoing-access PIN.
Your computer then shows a request containing their email address. Check that it's the person you expect, then select Share. The remote session begins after that approval, so sending the code alone isn't the final permission step.
The code works once. If the attempt fails or the session ends, generate another code for a fresh connection. Don't keep sending an old code and expect it to become usable again.
During sharing, you'll be asked every 30 minutes whether you want to keep sharing. Keep an eye on the screen so the session doesn't end while the helper is working. That prompt is part of the temporary support session.
I'd use this temporary route for a one-off repair. It gives both people a clear start and finish without leaving the computer set up for ongoing access.
Share a tab or desktop during a Meet call
For viewing rather than control, join the Google Meet call and click Present now. Choose A tab, A window, or Your entire screen, select the item, and click Share in the selection dialog.
A tab is a good choice for a website or browser-based presentation. A window is useful for a single desktop app. Share the entire screen when the demonstration needs to move among several applications.

Choose the actual content rather than the Meet window itself. Sharing the meeting window can produce repeated views of the same call. Close unrelated windows or notifications before a full-screen presentation so they don't interrupt it.
Sharing a Chrome tab includes that tab's audio by default in Meet. For window sharing or full-screen sharing, use Also share system audio if that option appears and you need sound from the computer.
System-audio sharing needs supported software, including Windows 11 or macOS 14.2 or later and a compatible Chrome version. If that option isn't available, presenting the browser tab is the simpler way to include sound from a web video.
Ask someone watching whether they can see the content you've selected and hear any sound you need to share. Seeing a preview on your own computer doesn't tell you whether you've chosen the intended window for the audience.
Stop sharing and remove ongoing access separately
For a temporary Chrome Remote Desktop session, click Stop Sharing on the shared computer. That ends the helper's access to the session. If more work is needed later, start another support session with another code.
For Meet, use Stop presenting in the meeting or the browser's sharing control. Leaving a particular document open isn't the same as stopping its presentation, so click the stop control before opening anything private.
If you previously set up Remote Access for your own computer, that is separate from a support session. Visit the Remote Access page and disable the saved computer connection when you no longer need ongoing access.
Resolve a connection that won't start
Check both computers are online, keep the computer being shared awake, and try a fresh support code. Check that the host software finished installing and that any requested Mac permissions were granted on the computer being controlled.
For a Mac that won't share through a meeting app, the Chrome screen-sharing permission guide addresses the capture permission failure. That issue differs from a Remote Desktop code being rejected.
If installation or connection remains blocked, use Chrome Remote Desktop Help from the support page. Tell them both operating systems, the error text, and where it failed: installation, entering the code, or approving access.
The Short Version
Use Remote Support and a one-time code for temporary control. Use Meet's Present now for viewing a tab, window, or screen. Approve the expected helper, stay present during the session, and use the stop control when finished.
Checked November 13, 2026.







