I’m having trouble getting sound to work while using Chrome Remote Desktop. Video is fine, but I’m not hearing any audio from the remote computer. Does anyone know how to fix this issue? I rely on audio for my workflow, so any advice would be appreciated.
Yeah, honestly, don’t waste your afternoon digging through settings—Chrome Remote Desktop just doesn’t play ball with audio most of the time. Don’t bother blaming yourself or your speakers; the sound simply doesn’t follow the screen.
Here’s the bare-bones, no-nonsense version:
- There’s no secret switch or hidden tweak in Chrome Remote Desktop that’ll suddenly blast sound from your remote PC.
- Sure, make sure the remote machine’s volume isn’t muted—sometimes you get lucky—but that’s not where the problem lies.
- If you truly care about hearing what’s going on over there (for me, it was trying to follow a training video), you’re better off grabbing a different tool. AnyDesk and TeamViewer actually work for this.
Basically: it’s just a limitation you have to work around. Don’t be surprised if you end up setting up a half-baked workaround using your phone as a mic/mic receiver, or start Googling for the 50th time, hoping something’s changed since last month. Spoiler: it hasn’t.
Personal rant incoming:
The fact that there’s still no built-in audio support in 2024 feels like buying a new TV that shows only black-and-white channels on purpose. Come on, Google.
4 Likes
Honestly, I feel your pain—Chrome Remote Desktop audio (or lack thereof) has been a running joke for how many years? Like, did Google just decide sound is too “2022” or what? @mikeappsreviewer nailed a lot of it, but I’m gonna disagree (just a bit). Yeah, you probably won’t unearth a magic toggle, but sometimes you can squeeze out system sounds if your OS and CRD install are playing nice. I’ve had rare cases (like, blue-moon rare) where the sound kicked in AFTER a remote reboot, especially on Windows, but it goes wonky again fast.
Really, this isn’t user error; it’s Google deprioritizing audio streaming, probably for “security” (eyeroll) and “performance” (yawn) according to their official PR. What’s wild is that open-source tools like Moonlight, or Parsec for gaming (and even RDP for Windows Pro) can stream sound just fine—so it ain’t a tech limitation, just a glaring omission. If you’re stubborn, there are fringe workarounds: some folks install virtual audio cables, pipe audio to Discord, or run VLC streaming from the remote box. These are janky, not fun, and frankly not worth it unless you like pain.
It’s 2024 and the only noise CRD makes is the sound of my disappointment. Is it security? Bandwidth? Laziness? Who knows. Try other tools if audio is mission-critical. And if Chrome Remote Desktop ever surprises us with an update that brings sound, someone better email me because I think I’ll faint. Til then—enjoy the silent disco.
Honestly, this whole CRD-no-audio drama is like deja vu for anyone who’s used the tool for longer than ten minutes. Both @mikeappsreviewer and @techchizkid are right to a point: it’s mostly a dead end if you’re expecting reliable sound from Chrome Remote Desktop. But here’s the kicker—I actually did get audio a couple times (we’re talking borderline Bigfoot sighting levels of rare here), usually after toggling “Play computer sounds” in the remote Windows sound control panel, and one time after a magical combo of updating both Chrome and the “Chrome Remote Desktop Host” package. Of course, it worked just long enough for me to think I fixed it, then crapped out after a reboot. Classic.
But let’s be real: Google hasn’t made audio a priority for CRD (despite every forum thread screaming for it), probably because they lowkey want folks to pay for enterprise stuff or push Chromebooks. Security excuses are just the usual song and dance—if literally every other remote tool can do it (RDP, TeamViewer, AnyDesk, even VNC forks), it’s not witchcraft.
If you’re stuck on CRD and won’t/can’t switch, the only semi-tolerable hack I found was using an app like AudioRelay or SoundWire to stream audio as a sort of sidecar to the video. This means running an extra server app on your remote PC just to get sound—which, let’s face it, is ridiculous, but it does work if you’re desperate. Expect a little lag and wonky reliability.
Otherwise, yeah, pick another tool if audio isn’t optional for your workflow. I know that’s not the magical answer, but unless Google gets their act together (not holding my breath), you’re in workaround city for now. Kind of wild in 2024 this is still a thing, but hey—they did finally kill Internet Explorer, so maybe sound will show up by 2030.
tl;dr: No real fix, hacks are janky at best, Google knows but doesn’t care, use something else if you need sound like, yesterday. But keep an eye out—I wouldn’t be shocked if the next surprise Chrome update randomly sneaks it in… or breaks ten other things.
Straight up: Chrome Remote Desktop (CRD) audio is that one party guest who never shows up. Yes, while @techchizkid and @mikeappsreviewer hit the nail—CRD’s lack of robust audio support leaves us all scratching our heads. Some claim they saw it, like @suenodelbosque, but it’s less Bigfoot, more Schrödinger’s sound—there until you check and then it’s gone.
There is no “fix switch.” But here’s a slightly different take: if CRD’s simplicity, web-based access, and speedy screen performance are critical, and you just need to occasionally catch audio—consider using CRD for visuals and a lightweight VoIP/livestream tool (Discord call, Google Meet, even something like OBS’s NDI out) on the side. It’s awkward, but works in a pinch. Good for low-security environments or casual remote work.
Pros of Chrome Remote Desktop:
- Free and super-easy setup
- Great for quick, mostly visual tasks
- Seamless with Google accounts
Cons:
- Audio is unreliable or absent
- Lacks advanced session controls
- Extra hacks needed for sound add lag and instability
As for the competition: alternatives like TeamViewer or AnyDesk just do remote audio so much better—less tinkering, less praying. They toss in fancier features too (file transfer, chat, granular access). But they come with limits/free tier restrictions.
Ultimately, unless Google shocks us by shipping sound support soon, CRD will keep trailing behind for those who need audio. If screen sharing is greater than sound in your use case, CRD stays king; otherwise, pick your poison—“competitors” can leave you feeling less like you’re stuck in remote desktop purgatory.