Run these from an operator’s chat, a command block, or a function file. Execute is simplified here — chain the rows in the order you want them to run.

How to Use the Stopsound Command Generator

  1. Open the Stopsound tab.
  2. Enter the target (whose sounds should stop), e.g. @a or a player name.
  3. Optionally pick a sound source category (music, hostile, record, etc.) to only stop sounds in that category, or leave it as (all).
  4. Optionally enter a specific sound ID, e.g. minecraft:music.overworld.forest, to only stop that one sound.
  5. Copy the generated /stopsound command into a command block, function, or an operator’s chat.

Command Syntax Reference

/stopsound <targets> [<source>|*] [<sound>]

With just a target, /stopsound <targets> stops every currently-playing sound for that target across all source categories – the blunt, stop-everything form. Adding a source narrows it to only sounds in that category (e.g. music stops background music without touching mob or block sounds). Adding a specific sound narrows further to just that one sound event; when you specify a sound but want to match it regardless of category, the source slot takes a literal * wildcard instead of a real category name.

Frequently Asked Questions

What happens if I leave both source and sound blank?

Every sound currently playing for that target stops immediately, regardless of category or which specific sound it is – this is the broadest, simplest form and is commonly used to instantly cut background music or ambient loops when a player changes area or a cutscene-style sequence needs silence.

Do I need the * wildcard, or can I just pick a source category with a sound?

If you know the sound’s category, you can specify both a real source and a sound together to be precise. The * wildcard is specifically for when you want to stop one exact sound ID no matter which category it happens to be filed under, without having to know or guess that category first.

Does /stopsound stop a sound permanently, or can it play again later?

It only stops whatever instance is currently playing – it doesn’t block the sound from being triggered again. If the same sound event fires again afterward (a new /playsound command, a jukebox restarting, ambient ocean sounds looping back), it plays normally; /stopsound has no lasting mute effect.

Can I stop a sound for just one player without affecting everyone else?

Yes – the targets argument accepts any selector, so a specific player name or a selector like @p stops sounds only for that one listener, leaving the sound still playing normally for anyone else in the world.

Why would I stop by source category instead of by exact sound ID?

Stopping by category is useful when you don’t know or care which exact sound is currently playing – e.g. stopping source music silences whatever background track happens to be active without you needing to track which of several possible tracks it is, which is more robust than hardcoding one specific sound ID that might not be the one actually playing.

Related Tools