Soundpacks

Soundpacks & Custom Notification Sounds

WebSpeak3 plays a short sound for certain events — connecting, someone joining or leaving your channel, receiving a message, or getting poked. You can replace any of these with your own audio, either one file at a time or all at once via a soundpack.

Where to find it

Open Options → Sounds.

• Enable sounds — turns all notification sounds on/off.
• Volume — overall volume for notification sounds (separate from voice/playback volume).
• Per event (Connect, Disconnect, Join, Leave, Message, Poke) you can:
  • enable/disable that specific sound
  • Test it
  • Upload your own file for just that event
  • Reset back to the default sound (only shown once you've uploaded a custom one)

Uploading a single sound

Click Upload next to the event you want to change and pick an audio file. Supported formats: .wav, .mp3, .ogg, .m4a.

Importing a whole soundpack

Click Import soundpack (.ts3soundpack) at the top of the Sounds screen, and select a .ts3soundpack or .zip file.

WebSpeak3 reads the audio files inside the archive and matches them to events by filename — it looks for TeamSpeak's usual internal names (e.g. a file with "userenteredchannel" or "enter" in its name is matched to Join; "gotpoked" or "poke" to Poke). This means most real .ts3soundpack files, and simple zips of appropriately-named audio files, work out of the box.

After import you'll see how many events were matched and how many files in the archive couldn't be matched to any event (their names didn't contain a recognized keyword) — those are simply skipped, nothing is imported for them.

If a soundpack matches an event you'd already customized, it overwrites that custom sound.

Where custom sounds are stored

Uploaded/imported sounds are stored locally in your browser, per event — not tied to a specific design or server. They persist across sessions until you hit Reset for that event or clear your browser's site data.

Troubleshooting

• Nothing plays for an event. Check that sounds are enabled overall, and that the specific event's checkbox is enabled.
• My soundpack imported but some events are missing. The archive's filenames didn't contain a keyword WebSpeak3 recognizes for that event. Upload the individual file directly for that event instead (via Upload) — you don't need to rename anything inside the zip.
• A .ts3soundpack from the official TeamSpeak client didn't fully match. TeamSpeak's internal event names vary between client versions and aren't documented in a stable format, so matching is best-effort by keyword. Uploading the specific files you care about individually is the reliable fallback.