Car sound effects you generate yourself

Car audio has two parts: what the car does, and where you are standing when it does it. The same engine heard from the pavement, the driver's seat or a hundred metres down the road gives you three different assets, and choosing the perspective is most of the work. These prompts name it every time, because library clips rarely say which one you are getting.

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

  • Start and idle

    via audiocpp-stable-audio-3-sfx

    petrol car engine starting from cold, starter motor cranking then catching and settling into a rough idle, exterior close

  • Door close

    via audiocpp-stable-audio-3-sfx

    car door closing solidly, dense thunk with a rubber seal compressing and a latch click, exterior, street

  • Tyre skid

    via audiocpp-stable-audio-3-sfx

    car braking hard on dry tarmac, tyres screeching and locking into a stop, outdoor street, wide

  • Horn

    via audiocpp-stable-audio-3-sfx

    car horn blasted once in city traffic, dual-tone honk with a street reverb tail, outdoor

  • Fast pass-by

    via audiocpp-stable-audio-3-sfx

    car passing the listener at speed on a wet road, doppler engine and tyre roar sweeping past, roadside

  • Interior driving

    via audiocpp-stable-audio-3-sfx

    interior of a car driving at motorway speed, muffled engine drone with tyre roar and wind, seamless loop

  • Rev and shift

    via audiocpp-stable-audio-3-sfx

    sports car revving hard and shifting up through two gears, throaty exhaust bark, exterior close

  • Indicator

    via audiocpp-stable-audio-3-sfx

    car indicator relay ticking steadily, dry mechanical clicks, interior close mic, seamless loop

  • Crash

    via audiocpp-stable-audio-3-sfx

    car crashing head-on into a barrier, huge metal impact with glass shattering and debris scattering, street

  • Failing to start

    via audiocpp-stable-audio-3-sfx

    car engine failing to start, starter motor cranking repeatedly and dying, battery weakening, exterior close

Prompts that work

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

  • Cold start

    petrol car engine starting from cold, starter motor cranking then catching and settling into a rough idle, exterior close

    Describing the three stages (crank, catch, settle) gets you a complete event instead of an engine that is already running.

  • Perspective as a control

    interior of a car driving at motorway speed, muffled engine drone with tyre roar and wind, seamless loop

    "Interior" and "muffled" together put the listener inside the cabin. Without them the model renders the exterior every time.

  • Pass-by

    car passing the listener at speed on a wet road, doppler engine and tyre roar sweeping past, roadside

    The road surface changes the tyre noise more than the speed does: wet tarmac hisses, dry tarmac roars, gravel crunches.

  • Door weight

    car door closing solidly, dense thunk with a rubber seal compressing and a latch click, exterior, street

    The rubber seal makes a modern car door sound expensive. Leave it out and you get a tinny older one.

Making cars sounds that fit

Decide where the microphone is first

Interior, exterior close and exterior distant are three different assets, and EQ does not convincingly turn one into another. The cabin is a small sealed space that removes the top end and adds its own resonance; distance removes the transients more than the treble. Write the perspective into every vehicle prompt. A missing perspective is the most common reason a car sound will not sit in a scene.

Engine and tyres are separate layers

Most driving audio is two independent layers. The engine tells you what the driver is doing (idling, accelerating, labouring, shifting) and the tyres tell you what the road is. You can specify them separately: "revving hard" plus "on a wet road" gives you an aggressive car in the rain, a combination no single library clip is likely to have.

Add the small mechanical details

Indicator relays, seatbelt reels, handbrake ratchets, key fobs and latch clicks are small and instantly recognisable, and each costs one short render. A scene built from these plus one interior bed sounds more real than a single long drive-by, and gives you events to cut on. The indicator loop here is meant to sit under dialogue and mark time.

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

Can I get a specific make and model of engine?
Not reliably. These models respond well to descriptions of behaviour and character ("throaty exhaust bark", "rough idle", "high-revving four cylinder", "heavy diesel clatter") and poorly to brand names, which have no consistent acoustic meaning in the training captions. Describe how the engine behaves.
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.