Electricity sound effects you generate yourself

Electrical sound comes in two families that are often confused. The steady kind is hum and buzz, from current doing what it should. The violent kind is arcing and sparking, from current going where it should not. Both are useful and they need different prompts. Most disappointing electrical generations describe one family in the other's words.

Listen: 10 samples from the electricity 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.

  • Arc discharge

    via audiocpp-stable-audio-3-sfx

    high voltage electrical arc discharging, violent crackling snap with an ozone hiss, close and dry

  • Tesla coil

    via audiocpp-stable-audio-3-sfx

    tesla coil firing repeatedly, rhythmic buzzing electrical discharges with a bright cracking edge, large room

  • Faulty mains

    via audiocpp-stable-audio-3-sfx

    faulty mains electrical hum, low buzzing drone with intermittent crackling and flickering, close, seamless loop

  • Fluorescent flicker

    via audiocpp-stable-audio-3-sfx

    fluorescent tube failing, buzzing starter clicking repeatedly with the tube stuttering on and off, empty room

  • Surge and trip

    via audiocpp-stable-audio-3-sfx

    electrical power surge building then a breaker tripping with a hard clunk and everything falling silent

  • Shower of sparks

    via audiocpp-stable-audio-3-sfx

    shower of electrical sparks from a severed cable, rapid crackling with sputtering bursts, industrial space

  • Taser

    via audiocpp-stable-audio-3-sfx

    taser arcing between contacts, rapid harsh electrical crackle with a rising whine, close mic, dry

  • Substation

    via audiocpp-stable-audio-3-sfx

    electrical substation humming under load, deep mains drone with a metallic resonance, outdoor, seamless loop

  • Static shock

    via audiocpp-stable-audio-3-sfx

    sharp static electricity shock, single brief snapping zap, very close mic, completely dry

  • Lightning arc

    via audiocpp-stable-audio-3-sfx

    lightning arcing to ground, tearing electrical rip into a deep concussive crack, open outdoor space

Prompts that work

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

  • Violent discharge

    high voltage electrical arc discharging, violent crackling snap with an ozone hiss, close and dry

    "Ozone hiss" is a useful cue. High voltage arcs produce a distinctive hiss alongside the crack, and naming it separates an arc from a spark.

  • Steady fault

    faulty mains electrical hum, low buzzing drone with intermittent crackling and flickering, close, seamless loop

    "Intermittent" makes it a fault instead of a working hum. The irregularity carries the story.

  • Rhythmic discharge

    tesla coil firing repeatedly, rhythmic buzzing electrical discharges with a bright cracking edge, large room

    A tesla coil discharges at an audio-rate rhythm. Asking for the rhythm stops it collapsing into undifferentiated noise.

  • Tiny and dry

    sharp static electricity shock, single brief snapping zap, very close mic, completely dry

    Static shocks are among the shortest sounds in any library. Without "very close" and "completely dry", the room swallows them.

Making electricity sounds that fit

Hum is tonal, arcing is noise

Mains hum is tonal: it sits at the supply frequency and its harmonics, which is why it can be notched out of a recording. Arcing is broadband and chaotic, closer to a crackling fire than a tone. Because they are spectrally opposite, mixing their vocabulary gives you mush: a prompt for a buzzing arc returns something halfway between that convinces as neither. Decide which family you need, then write the whole prompt in its terms.

Prompt the intermittency

A working circuit has little drama. Electrical sound gets dramatic through intermittency: the flicker, the stutter, the sputter, the moment it cuts out and comes back. Prompt the irregularity with words like "intermittent", "stuttering", "flickering" and "sputtering", and give the render enough time for several cycles. Four seconds of a fault that repeats twice reads as a fault; one second reads as a click.

Use electricity as a source for sci-fi weapons

Most energy-weapon sounds are electrical discharge, processed and pitched, so generating here and treating the result as source material often works better than prompting the laser collection directly. An arc gives the aggressive broadband texture, a tesla coil gives rhythm, and a rising hum gives the charge. Layer them and the result belongs to your project instead of sounding like a pack.

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

How do I get a convincing energy weapon out of this?
Build it in three layers, each its own render: a rising hum or whine for the charge, an arc or discharge for the shot, and a decaying crackle for the tail. Generating them separately lets you time the charge to the animation, which is the part that breaks when you use a single pre-made clip. The laser collection has finished versions; this one has the components.
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.