Google Home Not Playing Music? How to Fix It
If your Google Home or Nest speaker lights up, hears you, but won't actually play music, the cause is almost always one of four things: no default music service is set, the streaming account has become unlinked, the speaker has a weak or wrong Wi-Fi connection, or a speaker group / cast session has gotten stuck. The good news is that each has a quick, repeatable fix. Work through the checks below in order — they're arranged from most common to least — and you'll usually have sound back in a few minutes.
Start here: confirm it's a music problem, not a mute problem
Before changing settings, rule out the obvious. Say "Hey Google, what's the volume?" — if the Assistant answers but nothing plays, sound output is working and the issue is the music pipeline. If the Assistant doesn't respond at all, you have a connectivity or microphone problem instead, and our guide on "Device Is Offline" errors is the better starting point.
Also try a service-specific command like "Hey Google, play jazz on Spotify." If naming the service works but a plain "play music" doesn't, your default music service isn't set — jump to the next section.
- 1Set a default music service in the Google Home app
- 2Unlink and re-link your streaming account
- 3Reboot the speaker, then the router
- 4Re-create any broken speaker group
1. Set (or reset) your default music service
When you say "play music" with no service named, Assistant routes the request to whatever you've chosen as the default. If that's never been set — or a recent app migration cleared it — the command quietly fails or plays from an unexpected source.
- Open the Google Home app and go into your account or device Settings.
- Find the Music (sometimes under "Media" or "Services") section.
- Pick your preferred provider — YouTube Music, Spotify, Apple Music, Pandora, and others are supported — and mark it as the default.
Note that some services require a paid subscription for on-demand playback on speakers; free tiers may only allow stations or be blocked entirely. If recent changes to the app left you unsure where these settings now live, our explainer on the Google Home app vs. Google Assistant migration covers what moved where.
2. Re-link the streaming account
Linked accounts can silently break after a password change, an expired subscription, or a token reset on the provider's side. The symptom is telling: Assistant says something like "Sorry, something went wrong" or starts to load but plays nothing.
- In the Google Home app, open the Music services list.
- Unlink the affected service, then link it again and sign in fresh.
- Confirm the subscription is active and paid in good standing on the provider's own app — Assistant can't fix a lapsed account.
Re-linking forces a new authorization token, which resolves the majority of "it just stopped one day" cases.
3. Rule out Wi-Fi — the most common hidden cause
Streaming is bandwidth- and latency-sensitive. A speaker that's online enough to hear you can still be too weak to stream, causing audio that stutters, cuts out after a few seconds, or never starts. Because most Google Home and Nest speakers connect over 2.4 GHz Wi-Fi, they're prone to congestion and range issues.
- Check signal at the speaker's location. Thick walls, distance from the router, and microwave/Bluetooth interference all degrade 2.4 GHz. Moving the speaker even a few feet can help.
- Reboot the router, then the speaker. Power-cycle the router first, wait for it to come fully back, then unplug the speaker for 10 seconds. Order matters — the speaker should reconnect to a healthy network.
- Avoid splitting bands badly. If your router auto-steers devices between 2.4 and 5 GHz, the speaker can land on a band it handles poorly.
For a deeper fix, see our guides on 2.4 GHz vs. 5 GHz for smart-home devices and building a stable smart-home Wi-Fi network.
4. Fix stuck casting and speaker groups
When you ask a speaker group to play, every member has to sync. If one speaker is offline or on a different network, the whole group can fail silently. Likewise, a phone that's mid-cast can "capture" playback so commands seem to do nothing.
| Symptom | Likely cause | Fix |
|---|---|---|
| Single speaker plays, group is silent | One group member offline | Remove and re-add that speaker to the group |
| Music starts on the wrong speaker | Active cast session on your phone | Stop casting from the phone's notification, then retry |
| Nothing plays anywhere | Default service or account issue | Recheck steps 1–2 above |
If a group is the culprit, delete it and rebuild it in the Google Home app. Our walkthrough on adding a device to Google Home covers re-adding members cleanly, and you can use routines and automations to trigger group playback more reliably afterward.
When to factory reset (last resort)
If nothing above works and the speaker behaves erratically across multiple services, a factory reset clears corrupted settings. Back up nothing first — there's no local data — but you will need to re-add the speaker afterward, as covered in our first-time Google Home and Nest setup guide. Reset is rarely necessary; exhaust the service, account, and Wi-Fi checks first.
Frequently asked questions
Why does "Hey Google, play music" do nothing?
Almost always because no default music service is set, or the linked service's free tier doesn't allow on-demand speaker playback. Set a default with an active paid plan, or name a specific service in your command.
Music plays for a few seconds then stops — why?
That pattern points to Wi-Fi: the speaker buffers a little audio, then loses the stream when the connection drops. Improve signal at the speaker's location and reboot the router before blaming the speaker.
Why does only one speaker in my group play?
Speaker groups require every member to be online and synced. If one is offline or on a different network, the group fails. Remove the problem speaker, confirm it's connected, and re-add it.
Do I need a smart-home hub for music to work?
No. Google Home and Nest speakers stream directly over Wi-Fi from the cloud — no separate hub is involved. If music fails, the issue is the service link or the network, not a missing hub.
