Alarm and siren sound effects you generate yourself

Alarms are designed to be unmistakable, which makes them the most constrained sounds in a library: they have to cut through noise, repeat indefinitely, and be identified before anyone thinks about them. That helps when prompting, because only a few features matter: the pattern, the pitch, and whether the listener is inside the building or outside it.

Listen: 10 samples from the alarms & sirens collection

Every clip shows the exact prompt that produced it. The render script reads its prompts from the same file as this page. Copy one, change a word and generate your own.

  • Fire alarm

    via audiocpp-stable-audio-3-sfx

    building fire alarm sounding, harsh repeating electronic tone echoing down a corridor, seamless loop

  • Police siren

    via audiocpp-stable-audio-3-sfx

    police siren wailing and passing the listener at speed, doppler shift through the pass, city street

  • Air raid siren

    via audiocpp-stable-audio-3-sfx

    air raid siren winding up to a long mournful wail and falling away, distant across a city, outdoor

  • Dive klaxon

    via audiocpp-stable-audio-3-sfx

    submarine dive klaxon, harsh two-tone mechanical horn repeating, enclosed metal interior, seamless loop

  • Car alarm

    via audiocpp-stable-audio-3-sfx

    car alarm going off in a quiet street at night, repeating cycle of chirps and horn blasts, echoing

  • Reversing beeper

    via audiocpp-stable-audio-3-sfx

    heavy vehicle reversing beeper, single high electronic beep repeating steadily, outdoor site, seamless loop

  • Smoke detector

    via audiocpp-stable-audio-3-sfx

    smoke detector low battery chirp, single piercing beep every thirty seconds, quiet house at night

  • Red alert

    via audiocpp-stable-audio-3-sfx

    spacecraft red alert klaxon, urgent synthetic two-tone alarm over a low warning drone, metal interior, seamless loop

  • Ambulance distant

    via audiocpp-stable-audio-3-sfx

    ambulance siren wailing several streets away, muffled and echoing between buildings, night city

  • Warning horn

    via audiocpp-stable-audio-3-sfx

    industrial warning horn blasting three times before machinery starts, huge factory reverb

Prompts that work

These models respond to physical description. Name the material, the action and the space.

  • Interior alarm

    building fire alarm sounding, harsh repeating electronic tone echoing down a corridor, seamless loop

    The corridor places it in a building. Alarms are almost always heard through a lot of hard architecture.

  • Moving siren

    police siren wailing and passing the listener at speed, doppler shift through the pass, city street

    A siren that does not move sounds parked. Asking for the pass and the doppler in one render gives you the whole event.

  • Distance and muffling

    ambulance siren wailing several streets away, muffled and echoing between buildings, night city

    "Between buildings" produces the slapping urban reflections that place a siren in a city instead of open air.

  • Mechanical, not electronic

    air raid siren winding up to a long mournful wail and falling away, distant across a city, outdoor

    "Winding up" names the spin-up of a rotating mechanical siren, which is what distinguishes it from an electronic tone.

Making alarms & sirens sounds that fit

Describe the pattern

An alarm is recognised by its rhythm more than its timbre: the two-tone European siren, the American wail, the single repeating reversing beep, the three-blast industrial warning. Describe the pattern and the model gets the character right even if the tone is approximate. Describe only the tone and you tend to get a generic alarm that matches nothing in particular.

Decide inside or outside

An alarm heard inside the building it protects is loud, hard and close, with corridor reflections. Heard from outside, it is muffled, distant and mixed with the street. These are different assets and filtering does not turn one into the other. Because the alarm itself is so repetitive, the space carries most of the information about where the scene is, which makes it the most valuable clause in the prompt.

Loop the alarm, generate the arrival separately

An alarm scene usually has three parts: the moment it starts, the sustained state, and the moment it stops or is silenced. Make the sustained state a steady seamless loop you can run under the whole scene, and make the start and the stop one-shots. A single clip with all three cannot loop or be extended, which is what makes stock alarm clips awkward.

Why generate locally

The models run on your machine, which changes the cost, the privacy and what you can automate.

Offline after download

Weights are fetched once. After that, generation, the library and the API all work with the network off. Everything lives in one SQLite file and one folder of WAVs under ~/.soundbox, and nothing is uploaded.

Your agent can use it

Soundbox runs an MCP server in the same process, with tools for generating and listing sounds. Generated files come back as absolute paths, so an agent can copy them into a project.

Licences stated up front

Every model's terms are shown before you download it, and non-commercial weights need an explicit confirmation. Soundbox is MIT. The licence of the model that made a sound governs what you may do with it.

Connect a coding agent
claude mcp add --transport http soundbox http://127.0.0.1:17494/mcp
Generate over HTTP
curl -X POST http://127.0.0.1:17494/api/generate \
  -H 'Content-Type: application/json' \
  -d '{"model":"audiocpp-stable-audio-3-sfx","prompt":"8-bit coin pickup blip","duration_s":1}'

Frequently asked questions

Are these safe to use for a real alert in an app?
For a product notification, yes; that is what the notification collection is for. For anything safety-critical, no. Real emergency and medical alarms follow standards that specify exact frequencies, patterns and levels so they cannot be confused, and a generated approximation should never stand in for a certified one. Use these for film, games and interfaces, and use the standard wherever somebody has to act on the sound.
Can I use these sounds in a commercial video or game?
It depends on the model that made them. Soundbox shows each model's licence before you download its weights. The clips on this page were rendered with Stable Audio 3.0 Small SFX, which uses the Stability AI Community License: commercial use is free below USD $1M annual revenue, and above that Stability requires an enterprise licence. Soundbox itself is MIT, but the audio is governed by the licence of the model that made it. Read that licence before you ship; this summary is not legal advice.
Does this work offline?
Yes, once the weights are on disk. Generation, the library and the HTTP API all run locally against one SQLite file and one folder of WAVs under ~/.soundbox. There is no account and no API key, and nothing is uploaded. The only step that uses the network is the initial model download.
What hardware does it need?
The clips here were rendered on a consumer NVIDIA GPU at roughly ten seconds of wall time per clip, through audio.cpp's quantised GGUF runtime, which needs little VRAM. CPU-only generation is supported, but expect minutes per clip instead of seconds: fine for a handful of sounds, slow for a whole library.
Can an agent generate these for me?
Yes. While the app is open, Soundbox runs an MCP server at http://127.0.0.1:17494/mcp with tools for generating, listing and mixing sounds. Every generated file comes back as an absolute path, so a coding agent can render the sound a scene needs and put it straight into the project. The several hundred clips across these pages were made this way.