Skip to content
Any machine · no installer

Make music on any machine
No installer, no admin rights

A large share of the people who want to make music cannot install software on the computer they actually have. School laptops, work machines, Chromebooks, borrowed desktops, an old PC that will never survive a four-gigabyte installer. Music production without downloading is not a lesser version of the real thing - it is a different set of trade-offs, and for these machines it is the only set that works.

0 INSTALLERS 0 ADMIN RIGHTS 0 LICENCE FILES 20+ INSTRUMENTS 4 BROWSERS 7 DAYS FREE
Playable · proof, not a claim

Eight drum voices on whatever machine this is

Hit DEMO GROOVE, then play over it with the mouse or the letters on the pads. Nothing was downloaded, nothing was installed, and no permission dialog appeared. Whatever restrictions this computer has, they did not apply - which is the entire argument of this page, delivered before the argument.

The constraint, by machine

Five situations where the installer is the problem

None of these are edge cases. Together they are most of the people who never start.

Inbound paths stopped dead at a rigid policy perimeter around a machine, with one thin path getting through a narrow opening

The machine is not yours to modify

School and work laptops are locked by policy: no installs, no admin password, sometimes no writeable folders outside the profile. A browser is always allowed, because the machine would be useless otherwise. That is the loophole, and it is a legitimate one.

A solid block that cannot fit its receiving slot beside a flat plane sliding cleanly into a matching opening, illustrating installers versus the browser

ChromeOS cannot run the installer at all

It is not a restriction, it is an architecture. Chromebooks are the cheapest machines in most schools and among the most common first laptops, and no desktop DAW runs on one. The browser is not a workaround here; it is the platform.

A nearly full capacity bar above a much longer stack of layers overflowing far past it, illustrating a DAW install on an old machine

The machine is old and slow

Four gigabytes of RAM, a spinning disk, an integrated GPU. A modern DAW installation is several gigabytes before you add a sample library, and the plugin scan alone will test your patience daily. A tab starts in seconds.

Four different devices each receiving the same payload from one floating ring above them, illustrating work that lives in an account rather than a machine

The machine changes every day

Library computers, a shared family desktop, a friend's laptop, a different room each period. Anything installed lives on one machine; anything in an account follows the person.

A long track broken into many sequential stages above a single short unbroken run to the same result, illustrating time-to-first-sound

You want to start now, not tonight

The gap between deciding to try music production and hearing your first sound is where most people quit. Downloading, installing, registering, scanning and configuring is an hour. Opening a tab is not.

Honest accounting

What you gain and what you actually give up

Both columns are real. Read the right-hand one properly before deciding.

No-install studio Installed DAW
Time to first sound Seconds An hour, on a good day
Admin rights needed None Yes
Runs on ChromeOS Yes No
Disk space used None Several gigabytes, more with libraries
Same session on another machine Log in Copy files and hope
Works with no connection No Yes
Third-party plugins No Yes
Tracking live players at low buffer No Yes
Survives the platform shutting down Export early and often The files are yours
Getting started on a restricted machine

Five things worth doing in the first session

Use headphones, not the built-in speaker

Laptop speakers cannot reproduce anything below about 150 Hz, which means you cannot hear your own bass. Any wired headphones are a bigger upgrade than any plugin.

Check the browser first

Chrome or Edge for the most complete Web Audio and Web MIDI support. Firefox is fine for audio. Safari runs the instruments but its MIDI support varies by version.

Close the other thirty tabs

Audio runs on its own thread, but memory pressure is shared. On a machine with four gigabytes of RAM, a dozen open tabs is the difference between smooth and stuttering.

Export something on day one

Learn where the export button is before you need it. Anything that matters should exist as a WAV or a MIDI file outside the platform, whichever platform you use.

Plug in a controller if you have one

Class-compliant USB and Bluetooth controllers need no driver, which means they also need no admin rights. On a locked machine this is often the only hardware you can add at all.

Deep links

What runs with nothing installed

All 20+ of them, on the same engine. These four are a reasonable place to start.

Why this constraint is more common than the industry admits

Music software marketing assumes a machine you own and control, running Windows or macOS, with enough disk for a library and enough authority to install a driver. An enormous number of people who want to make music have none of that. They have a school-issued Chromebook, or a work laptop with a locked policy, or a six-year-old desktop shared with a family. The tools built for the assumed machine simply do not run for them, and the usual advice - "just get a free DAW" - misses the point completely, because free is not the obstacle. Permission is.

The browser is not a compromise here, it is the platform

On a Chromebook there is no desktop DAW to compromise against. The Web Audio API is the audio engine, and it is a real one: oscillators, filters, convolution reverb and dynamics running in native code, scheduled sample-accurately. The instruments are not scaled-down versions of desktop products, they were built for this. What that actually feels like is covered on the Chromebook page, and the engineering on the browser-based DAW page.

The one thing to be careful about

Nothing in a browser works offline, and nothing hosted by someone else is permanently yours. Export stems and MIDI at every milestone - not because this platform is going anywhere, but because that is the only habit that makes any hosted tool safe to depend on. It costs thirty seconds and it is the single most useful thing in this article.

Questions

Frequently asked

Can you make music without downloading software?

Yes. Browser-based studios run entirely on the Web Audio API with nothing installed - real synthesis, sequencing, sampling and effects. The limits are offline work and third-party plugins, not sound quality.

Do I need admin rights?

No. Nothing is installed, so there is nothing to authorise. This is what makes browser studios work on school and corporate machines where every desktop DAW is blocked by policy.

Will it run on an old laptop?

Usually, yes. Audio processing runs in the browser's native audio code rather than in JavaScript, so the cost is comparable to a desktop instrument doing the same job. Voice count and effect stacking are what add up - the low-end PC page covers how to spend an old machine wisely.

Does it work on a Chromebook?

Yes, and for Chromebooks it is the only category that works at all, since ChromeOS cannot run desktop DAW installers.

What happens without an internet connection?

The apps do not load. If you regularly work offline, an installed DAW is the correct choice and no browser tool substitutes for one.

Can I get my work off the platform?

Yes - WAV audio and MIDI both export and both open anywhere. Do it at every milestone rather than at the end; that habit is what makes any hosted tool safe to rely on.

Ready when you are

The machine you already have is enough

All 20+ apps, no installer, no admin rights, seven days free with everything unlocked and no card required.

Already subscribed? Launch DrumPad →