Big pads, one browser tab. Tap them with your fingers, your mouse or your keyboard, hit record, and play the rhythm in real time — then stack the next sound on top while the loop keeps running. This is a drum pad, not a step grid: you perform the beat instead of drawing it.
How it works
The first hit unlocks the audio and loads the sounds. After that every pad fires the instant you touch it — finger, mouse or key. Spend a minute just playing before you record anything; the pads are the instrument, and knowing where they are is the whole skill.
Start recording and let the count-in tell you where beat one is. Play a single sound through the loop — usually the kick — and stop. One sound per pass sounds slow, but it is the fastest way to end up with something that grooves.
The loop comes back round with your first pass playing. Add the next sound over the top, then the next. When the parts are all there, quantize to pull the stray hits onto the grid — play it by feel first, fix the timing after.
What you get
Most browser drum pads are a wall of buttons that make a noise and forget it a second later. This one remembers: everything you play can go into a loop, layer by layer, and then straight into a full studio.
Large targets laid out so your hand can find them without looking, the way a hardware pad controller is. It is a different instrument from a mouse-and-checkbox sequencer, and it rewards a different thing — rhythm in your hands rather than patience with a grid.
Arm it, take the count-in, and play. What you played is what gets captured — the push and drag of a human performance included. That is the part a step grid can never give you, because a step grid can only ever be exactly on the beat.
The loop keeps running while you record onto it, so each new sound is played against the ones already there. Miss a pass? It comes round again in a couple of seconds. Nothing about this workflow punishes you for playing badly the first time.
Real-time playing is never perfectly in time, and it should not have to be. Quantize snaps the hits onto the nearest division so the loop locks, which means you can play loose and confident instead of stiff and careful.
Every pad is playable three ways, and all three take more than one hit at a time, so a kick and a clap on the same beat land together. On a phone the pads are the interface; on a laptop the keyboard is usually faster once you are recording.
One button carries whatever is currently in your loop into the full beat maker — the pattern arrives with you rather than being left behind on a tool page. That handoff is why this is a sketchpad and not a toy.
How to make a beat on a drum pad
A beat made on pads is built in layers, not written in one go. Record each of these on its own trip round the loop and listen to what you already have before you add the next thing.
Put a kick on beat one and let it be boring. The kick is the floor everything else stands on, and if it wanders the whole loop wanders with it. Play it through twice before you stop, so you can hear whether your timing settles or drifts.
The snare or clap goes on the backbeat — the beats between the kicks — and it is what makes people nod. You now have a beat. Everything after this is decoration, which is worth remembering when a loop stops working and you cannot say why.
Hi-hats are the ruler the rest of the pattern is measured against, so keep them even before you get clever. Two hits per beat gives you a rock or pop feel; four per beat pushes it toward funk and trap. Play them evenly and let the tempo do the rest.
Add exactly one thing that is not on a beat — an extra kick landing just after three, an open hat on the very last division before the loop turns over. One asymmetry is character; four is mush. Add it, listen to the whole loop, then decide whether to keep it.
Now quantize. Anything you rushed or dragged pulls onto the grid and the layers snap together. Do this last rather than first: if you quantize before all the parts are down, you spend the session chasing a metronome instead of playing.
A loop is a sketch. Open it in the beat maker and it becomes a track — the same pattern, plus bass, melody, arrangement, real-time collaboration and export. Nothing you just played gets retyped.
Search for a drum pad and you mostly land on two things: a phone app full of adverts, or a few hundred euros of hardware with a pad grid on the front. Both assume you already know that hitting pads is how you want to make music. Most people searching have never actually tried it, and there is no cheap way to find out.
This is the cheap way to find out. The pads are here, in the tab, playable in about a second. Hit a few, get a feel for where they are, and you will know within a minute whether performing a rhythm suits you better than programming one. If it does, the hardware will make a lot more sense when you eventually buy it — and if it does not, you have lost nothing.
It also removes the part of pad hardware that stops beginners dead: setup. No driver, no sample folder, no DAW to route it into. The sounds are already loaded and the record button is already there.
A step sequencer asks you a question about geometry: which of these cells should be on? A drum pad asks you a question about time: can you put this sound exactly here, right now? They produce different beats, because they engage different parts of your brain. A programmed pattern is as precise as you can be bothered to make it. A played one carries the small early-and-late variations that make a loop feel like a person rather than a grid.
That is also why the two workflows suit different people. If you can already hear the rhythm and just want it out of your head, pads are much faster than clicking. If you cannot yet hear it and need to see the shape of the bar in front of you, a grid teaches you more. Plenty of people use both: play the loop on the pads to get the feel, then open the grid to fix the one hit that is in the wrong place.
If the grid is what you actually came for, the virtual drums page is the one to open — it pairs a full kit with a step sequencer and a set of preset beats, and it is linked below. This page deliberately does not duplicate it. Pads and grids are two different instruments, and pretending otherwise would make both worse.
The instinct with a pad grid is to play the whole beat with two hands, like a drummer. On a laptop, with a keyboard and a mouse, that almost never works — you get three sounds in and the timing collapses, and it feels like the problem is you.
It is not. Multitrack recording exists precisely because playing everything at once is hard, and overdubbing is that idea shrunk down to a single bar. One sound per pass, played against everything already recorded, gets you a tighter loop than a live take would — and you can hear it improving in real time instead of hoping.
The order matters more than the speed. Kick, then backbeat, then hats, then the one detail that breaks the pattern. Each layer has something to lock to, and every pass you record is a pass you also spent listening to what is already there. Quantize at the end, once, rather than fighting for perfect timing on every take.
A drum loop is where a track starts, not where it ends. The moment yours is worth keeping, open the beat maker from the button on this page — your pattern comes with you, and there you get bass, melody, samples, arrangement and export, plus the ability to invite someone into the same session and build the rest of it together in real time.
If the next thing you need is a tune over the top, the melody maker gives you a full piano roll with MIDI and WAV export, and the virtual piano is there for finding the chords by ear first. If the thing holding you back is timing rather than ideas, the rhythm trainer drills exactly that — and a steadier internal clock shows up in your pad takes immediately.
Keep going
The full studio: your recorded loop plus bass, melody, samples, arrangement and real-time collaboration. This is where a pad sketch turns into a track.
The other half of this pair. A full drum kit with a step sequencer and preset grooves — for when you would rather program the pattern into a grid than play it on pads.
The longer walkthrough, from first kick to finished arrangement, with a sequencer built into the page so you can follow along as you read.
Write the tune that sits over your drums, generate one from a chord progression, and export it as MIDI or WAV.
A sampled grand piano in the browser for working out chords and basslines by ear before you program them.
Timing drills that build the internal clock a pad player lives on. The most direct way to make your recorded takes need less quantizing.
What the studio can do — sequencer, instruments, effects and export — if you want to see it before you open a session.
FAQ
A drum pad is a grid of large trigger pads, each one loaded with a drum sound. You hit them in real time — with a finger, a mouse or a key — and the sound fires instantly, the same way an MPC-style hardware pad controller or a drum pad machine app works. An online drum pad is simply that instrument running in a browser tab, so there is nothing to buy and nothing to install before you can play something.
A drum pad is played; a step sequencer is programmed. On a pad you perform the rhythm with your hands and whatever you play is what you get, timing and all. On a step sequencer you switch cells on and off in a grid and the machine plays it back perfectly in time. Neither is better — they suit different heads. If you would rather draw the pattern than play it, use the virtual drums page, which pairs a full kit with a step grid.
Yes. It is free, there is no account, no trial and no subscription, and the pads are playable the moment the page finishes loading.
Start recording, let the count-in run so you know where beat one is, and play your first sound all the way through the loop. Do not try to play the whole beat at once — record one sound per pass and let the loop come round again. That is how records are actually built, and it is far easier than trying to play a full kit with two hands on a laptop.
Overdubbing means adding a new sound to a loop that is already playing instead of starting the take again. Your kick keeps looping, and on the next pass you play the snare on top of it. Because you can hear the previous layer while you play the new one, the parts lock together — which is the whole reason a beat made this way feels tighter than one assembled part by part in silence.
Quantize nudges each recorded hit onto the nearest beat division, so a take that was slightly early or late snaps into the grid. It is the safety net that makes a real-time pad performance usable: play it by feel, then tighten it up afterwards rather than trying to be a metronome on the first try.
Yes. The pads are sized for fingers rather than a cursor, and they respond to more than one touch at once, so you can land two sounds on the same beat. That is the closest a browser gets to the feel of a physical drum pad machine — and it costs nothing.
Yes. Each pad is also triggered by a key, which is worth learning if you are recording: keys are faster and more accurate than dragging a mouse between pads, and you can hold two sounds down together. Key detection reads the physical key position, so the layout lands in the same place on a QWERTY and a QWERTZ keyboard.
No. Most searches for a drum pad end at a phone app or a few hundred euros of hardware. This runs in the browser, so you can find out whether you actually enjoy playing pads before you spend anything — on a laptop, a school computer or a borrowed machine.
Not from this page — it is built for playing and sketching. When a loop is worth keeping, open it in the beat maker with the button on this page: your recorded pattern travels with you into the full studio, where you can add bass, melody and arrangement, work on it with someone else in real time, and export the result.
Open the full beat maker to put bass, melody and arrangement under the beat you just played — and build the rest of the song with friends in real time.