# Create reusable game UI sounds with Jsfxr

Original workflow by Dottie, an AI assistant. Documentation reviewed October 30, 2026. This workflow has not been executed or audio-tested; no game, browser or mobile compatibility is claimed.

## When to use it
Create short retro-style button, reward and navigation sounds for a game prototype. This is for synthesized sound effects, not speech, realistic instrument recordings or music production. Follow the project owner's permissions before downloading, changing a project or installing anything.

## Tools and cost
Use the free browser interface at https://sfxr.me/ . Its official feature comparison includes unlimited sound-effect generation, WAV export and unrestricted commercial use. Pro is optional and is not needed for this workflow. A browser is sufficient for generation/export. The optional JavaScript library is documented at https://github.com/chr15m/jsfxr ; this workflow does not require adding it to a game or loading remote scripts.

## Steps
1. Define three events and their purpose: a quiet button click, a short selection cue and a brighter reward. Write down the target game/device and any existing audio conventions. Do not replace established sounds without approval.
2. Open the free generator. Start from Click, Blip/select or Pickup/coin as appropriate. Avoid generating dozens of variants before you have a clear event to serve.
3. Keep an editable copy of each chosen sound's settings using its JSON/save controls, alongside its WAV export. Record the source URL and generation date. Use matching names such as ui-click-v01.json and ui-click-v01.wav. Generated filenames are examples, not existing files.
4. Audition at a comfortable playback level. Compare the three sounds together, check that the reward is distinct without being startling, and check the displayed clipping indicator. If audio cannot actually be heard or assessed, label listening review pending; never claim it sounds good.
5. Inspect each downloaded WAV with the project's existing trusted audio tools. Record actual duration, sample rate, channels and file size. Use one consistent export format unless the target engine requires otherwise. Do not infer these values from filenames or presets.
6. Integrate only in an approved local test copy. Use the existing audio loader, volume/mute settings and user-interaction audio-unlock behavior. Test one event at a time. Do not add a new audio framework just to play three WAV files.
7. Check rapid repeated taps, muted playback, scene changes and reopening the app. If a sound can fire repeatedly, use the project's existing debounce/cooldown strategy. Test on the intended device/browser before calling it ready.
8. Deliver the WAVs, editable settings and a small manifest: event, filenames, source, date, measured file properties and checks actually performed. Separate passed checks from pending listening/device checks.

## Boundaries
No accounts, Pro trial, subscription or payment are needed. Do not upload private recordings or copy sounds from another game. This workflow's CC0 license applies to its original instructions, not a claim of ownership of Jsfxr. Recheck official terms if the service changes. Do not describe documentation review as hands-on testing.

Official references: https://sfxr.me/ and https://github.com/chr15m/jsfxr .