Back to Help Center

Sound Library

Build a library viewers can understand quickly

SoundSlap works best when sounds are short, named clearly, priced intentionally, and paired with recognizable GIF artwork. This page covers uploading, visibility, GIF choices, and per-sound controls.

Uploads and visibility Klipy GIF artwork Naming and organization Volume and cooldowns
Uploads

Manage uploads and visibility

Uploaded sounds can stay private to your channel or be shared publicly. Treat visibility as a content decision, not just a storage option.

  1. Upload a short audio clip from the dashboard upload flow.
  2. Give it a clear name before saving. Viewers should know what will happen before they spend.
  3. Choose private for inside jokes, channel-specific memes, or anything that only makes sense in your community.
  4. Choose public only for sounds that are broadly useful, cleanly named, and safe for other streamers to discover.
  5. Save, then open My SoundSlap List and confirm the sound appears with the expected visibility toggle.

Only admins should need to know who uploaded a sound. Public viewer-facing cards should focus on the sound, price, and artwork, not uploader attribution.

GIF artwork

Choose safe Klipy GIFs

GIFs are visual hints for what a sound feels like. They should help viewers make a decision, but they should not distract from stream safety.

  1. Search Klipy by the sound name, emotion, or expected reaction.
  2. Pick GIFs that read clearly at small panel size. One obvious expression is usually better than a busy scene.
  3. Use PG or G-rated results only. Do not use sexual, hateful, violent, or shocking GIFs for public sounds.
  4. Preview the sound card after saving. Check both desktop and mobile panel sizes.
  5. Use Hide GIF if the GIF should represent the panel card but should not appear in the OBS overlay alert.

The GIF should not surprise the streamer more than the sound does. If the artwork feels risky, pick a safer reaction image.

Organization

Name sounds for fast scanning

Short names perform better because viewers can scan them quickly in the extension panel. The best names usually describe the reaction, not the file name.

  • Use one to three words when possible: Air Horn, Goal Horn, Anime Gasp.
  • Avoid file-name leftovers like underscores, version numbers, or random dates.
  • Do not rely on tiny GIF text to explain the sound.
  • Keep names different enough that viewers do not confuse two sounds with similar prices.

If a sound needs a paragraph of explanation, it is probably not a good viewer-facing alert.

Control

Tune volume and cooldowns per sound

Not every sound should hit the stream at the same intensity. Use per-sound volume and cooldowns so fun sounds stay fun instead of becoming disruptive.

  1. Start new sounds at a conservative volume and test through OBS.
  2. Lower volume for long, sharp, or high-frequency clips.
  3. Use short cooldowns for subtle reactions and longer cooldowns for loud interruptions.
  4. Pair expensive or loud sounds with stricter cooldowns.
  5. After a stream, check which sounds were overused and adjust cooldowns before the next one.

A good library gives chat power without making the broadcaster afraid to leave the panel enabled.