· 7 min read
Free online DAWs: what a browser can actually do now
Browser music software went from toy to usable when the Web Audio clock stopped being a timer. What that changed, what it still cannot do, and how to pick one.
"Online DAW" covered a lot of bad software for about a decade, and the reputation has outlived the problem. Here is what actually changed, so you can tell which limitations are real and which are quotes from 2014.
The problem that made them toys
Timing. Not sound quality — browsers have played back audio cleanly for a very long time. The trouble was that early browser music tools scheduled notes with the same timers that animate a dropdown, and those timers are allowed to be late. They are late by a few milliseconds under load, more if you switch tabs, and a drum pattern is exactly the thing where a few milliseconds is audible as sloppiness.
The fix is to schedule against the audio hardware's own clock rather than the page's, queueing notes slightly ahead of when they are needed. Every serious browser music tool does this now. It is the single line between a browser instrument that sounds professional and one that sounds like a website.
What a browser does well now
- Synthesis. Oscillators, filters and envelopes run natively and cost almost nothing, which is why synth-based tools feel snappier online than sample-based ones.
- Step sequencing and piano-roll editing. This is ordinary interface work and browsers have been good at it for years.
- Sample playback, once loaded. The catch is in those last two words.
- Rendering a finished mix offline, faster than real time.
What is still genuinely harder
- Large sample libraries. A multi-gigabyte orchestral library is not going over a connection before you lose patience, and this is not going to change.
- Plugins. Your VST collection does not run in a tab, and no amount of progress makes it.
- Low-latency live recording. Getting a microphone in, monitored, with round-trip latency low enough to play to, is the weakest area and depends heavily on the machine.
- Very large projects. Sixty tracks with heavy processing is still a desktop job.
Notice that the honest list of weaknesses is about scale and about hardware in and out. None of it touches making an eight-bar loop from synthesised sounds, which is why that is the shape most browser tools have converged on.
How to pick one
The useful question is not which has the most features, it is which of these three things you are doing:
| You want to | Look for | Accept that |
|---|---|---|
| Sketch an idea in ten minutes | A tool that opens with sounds already loaded | It will not finish the track |
| Produce a full track | Cloud projects, stems, collaboration | You will fight the browser at some point |
| Learn by doing | A small kit and hard constraints | Fewer options is the feature |
The third row is the one nobody markets, and it is the one most beginners actually need. A tool with two hundred instruments teaches you to browse instruments. A tool with twelve teaches you to write parts, because there is nothing else to do.
The constraint version
GrooveArena's studio is deliberately at the far end of that: seven drum voices, five melodic ones, eight bars, and a tempo it rolls for you. There is nothing to load and nothing to choose before you start, which means the first sound happens within seconds of the page opening.
It exists because it is also a multiplayer round — everybody gets the same tempo and the same four minutes — and a contest cannot be fair if one player brought a better sample pack. The side effect is that it is a good place to practise writing rather than shopping.
Four minutes is shorter than it sounds.
Play a round