— Free tool
Drum Synthesiser
Design drum one-shots from first principles — no samples. Shape a kick's thump with a pitch envelope, rattle a snare's wires, choke an open hat, then export the kit as WAVs that drop straight onto a drum rack. Nothing installs, nothing uploads.
Boomy sine kick with a long sub tail, tonal snare, metallic hats — the classic analogue voice-circuit palette.
Hit low on a pad for a hard hit, high for a ghost note. Keys A–J play; hold Shift for soft. Closed hat chokes the open hat.
Kick
A sine wave whose pitch falls fast — the sweep is the thump, the tail is the boom.
One-shot
Export
Keys A S D F G H J play the pads · Shift for a soft hit · Esc stops everything
Drum Synthesiser
Audio starts on your first interaction — a browser autoplay rule. Everything runs on your device; nothing is uploaded.
— A kit designer that teaches synthesis
An 808 kick generator, explained as it goes
Every kick drum synthesiser is the same trick: a sine wave whose pitch falls fast. The sweep is the thump, the tail is the boom — and here that trick is a knob you can hold while you listen. Flip on 808 mode and the tail stretches into a long two-stage sub; add click for the beater, drive for warmth, and you have gone from house thump to sub-bassline kick without touching a sample. The other five voices work the same way: each panel carries a one-line note saying how the sound is made, and the Fundamentals kit sets every voice so its trick is unmissable.
A free drum kit designer with honest exports
The export panel writes plain WAV files — 44.1 or 48 kHz, 16- or 24-bit — tail-trimmed, fade-protected against clicks, peak-normalised, and named so a sampler sorts them sensibly: boogie-kick-808-style-f1.wav. Download a single one-shot or the whole kit as a ZIP of seven files, closed and open hat both. Eight factory kits cover the classics — 808-style boom, 909-style punch, techno, house, trap, jungle, lo-fi — each described by what it does, and any kit you make is a URL: the seeded noise means whoever opens your link hears exactly what you built.
It talks to the rest of the suite
Need a rhythm to audition against? The Euclidean Rhythm Sequencer → generates patterns with the same family of voices, the Chord Progression Generator → writes what goes over the top, and when the track is finished the LUFS Checker → tells you the truth about the master.
— FAQ
How are the drums synthesised?
Each voice is a classic analogue recipe built with the Web Audio API, not a sample: the kick is a sine wave with a fast exponential pitch drop, the snare layers two sine partials with filtered noise, the hi-hat sums six square waves at inharmonic ratios through tight filters, the clap staggers several noise bursts a few milliseconds apart, the perc sweeps a single pitched wave from tom to zap, and the cowbell is two detuned squares into a resonant bandpass. Every voice carries a one-line note in the panel explaining exactly this.
Does my audio leave the device?
No. Synthesis, audition and WAV encoding all happen in your browser; saved kits live in your browser storage, and a shared kit is encoded entirely inside the URL itself — around seventy characters. No upload, no account, no server in the audio path.
What exactly do I download?
WAV one-shots at your choice of 44.1 or 48 kHz and 16- or 24-bit (48 kHz/24-bit by default), tail-trimmed with a short fade so they never click on retrigger, peak-normalised to −0.3 dBFS (or −6 dBFS if you want headroom), and named predictably — boogie-kick-808-style-f1.wav. The kit download is a ZIP of all seven one-shots, closed and open hat included, ready to drop on a drum rack or a hardware sampler.
Why does a shared kit sound identical for whoever opens it?
Everything that involves randomness — the noise in the snare, hats, clap and kick click — comes from a seeded generator, and the seed travels inside the shared URL. Same settings, same seed, same sound: the link is the kit.
Can I use the sounds commercially?
Yes. The sounds are ordinary synthesis you shaped yourself; the tool claims no rights over anything you export.
Why does it ask me to enable audio first?
Browsers block pages from making sound until you interact with them — a sensible autoplay rule. One click creates the audio engine inside that gesture; exports work even before it, because they render offline.
Found this useful? Help keep boog.ie free.
Buy the tools a coffee