AudioMass, a browser-based audio editor that weighs roughly 65 KB and runs entirely client-side, now ships a multitrack mode. The update lets users layer multiple audio tracks, drag clips on a timeline, crossfade overlaps, record onto armed channels, and bounce a final mix to a single file, all without installing software or creating an account. The project drew attention on Hacker News in late May 2026. The question worth asking is whether a tool this small can absorb the casual end of Audacity’s user base, or whether browser memory constraints keep it a curiosity.
What AudioMass actually is
AudioMass is a free, open-source audio editor built by pkalogiros on GitHub. It runs in any modern browser with no server-side processing. The build pipeline concatenates plain JavaScript files, including wavesurfer.js, multitrack.js, and engine.js, with no compiled WASM module or framework layer visible in the repository. This is worth noting because the natural assumption for “browser-based audio” is that it relies on WebAssembly for performance. AudioMass does not appear to. It leans on the browser’s native WebAudio APIs and a waveform visualization library, keeping the download small enough to load on a constrained network connection.
The editor supports import and export in WAV, MP3, and OGG formats, with real-time effects covering EQ, reverb, pitch shift, compression, and gain adjustments, according to Tiorai’s tool listing. For a tool with no install step and a roughly 65 KB footprint per Building Beats, the feature list is surprisingly coherent. It is not trying to be a full DAW. It is trying to be the thing you open when Audacity is not available.
How the multitrack mode works
The new multitrack mode adds the ability to layer multiple audio tracks on a shared timeline. Users can drag clips to reposition them, set crossfades where clips overlap, arm a channel for live recording directly in the browser, and bounce the finished mix down to a single file for export. The workflow mirrors what you would find in a stripped-down version of GarageBand: a timeline view, per-track controls, and a render step at the end.
This moves the tool beyond its original single-track editing mode, which was useful for trimming and normalizing a podcast episode but could not handle multi-mic recordings or layered music production. Multitrack editing is the feature that separates “audio utility” from “audio editor” in most users’ mental models.
Who benefits: locked-down devices and zero-install workflows
The clearest use case for AudioMass is the machine you cannot install software on. School Chromebooks, corporate IT-managed laptops, library terminals, and shared workstations where the user lacks admin rights all share the same constraint: you cannot run Audacity, Reaper, or any other native audio editor because you cannot install anything. A browser-based tool that requires no account and no installation bypasses that constraint entirely.
Podcasters recording on a locked-down work laptop, students editing interviews for a journalism class on a school-issued Chromebook, and community radio volunteers using a shared machine all fall into this category. For them, AudioMass is not competing with Audacity on features. It is competing with “no tool at all.”
The zero-install property also matters for privacy-sensitive workflows. Because AudioMass processes everything client-side and does not upload audio to a server, nothing leaves the machine. For reporters working with confidential interview recordings or musicians who do not want stems in someone else’s cloud storage, this is a genuine advantage over browser-based tools like Soundtrap that require accounts and server-side processing.
Where browser audio hits the wall
The limitations are real and well-documented. Tiorai’s listing identifies three: no offline or desktop version, limited advanced features compared to professional tools, and browser memory constraints that cap project size.
The memory constraint is the structural one. Browsers allocate a fixed amount of RAM to each tab, and audio work is memory-intensive. A multitrack project with dozens of clips and high-resolution source files will hit that ceiling before an equivalent project in Audacity, which can address system memory directly. The exact limit varies by browser and OS, but the ceiling is lower than what a native application faces, and there is no workaround within a browser tab.
The absence of an offline mode means the tool is unavailable entirely when there is no internet connection, even though all processing happens locally. The initial page load still requires network access. For users on unreliable connections, this is a practical gap.
And the feature gap with native DAWs is wide. AudioMass does not appear to support MIDI, VST plugins, automation envelopes, or non-destructive editing at the level that even Audacity provides. These are not missing features waiting to be added. Some of them are architecturally difficult to deliver in a browser environment without WASM compilation, which AudioMass does not use.
Can plain JS eat Audacity’s casual user base?
The competitive question is not whether AudioMass replaces Audacity for serious mixing work. It will not. The question is whether it replaces Audacity for the subset of users who open the program once a month to trim a clip, normalize levels, or layer two voice tracks for a rough cut.
For those users, the friction calculation is telling. Audacity requires a download, an install, and periodic updates. AudioMass requires a URL. On a machine where the user has admin rights and a stable workflow, Audacity wins on features and reliability. On a machine where the user does not have admin rights, or where the task is simple enough that firing up a full DAW feels like overkill, AudioMass has a real opening.
The catch is that “real opening” does not equal “market shift.” The browser audio space has seen tools like this before. Most stall when they hit the feature ceiling that native code does not have. AudioMass’s advantage is its simplicity and its refusal to pretend it is something it is not. It is a small, free tool that does a subset of audio editing well enough for casual use, in environments where the alternatives are nonexistent.
Whether that is enough to sustain a project long-term depends on how many users exist in that specific niche: technically constrained, casually productive, and unwilling or unable to install native software. That niche is real. It is also smaller than the enthusiastic HN thread makes it look.
Frequently Asked Questions
Does AudioMass save multitrack sessions, or is work lost when the tab closes?
The research sources document import and bounce-to-file export (WAV, MP3, OGG) but do not mention a project save format or session persistence. Closing the tab before bouncing the mix likely discards the multitrack session entirely. Audacity’s .aup3 project files preserve individual tracks, clips, and edit history across sessions, a workflow advantage the body does not address.
How does the HN response compare to typical open-source audio tool launches?
The AudioMass multitrack thread collected 404 points and 87 comments on Hacker News. Most open-source audio tool announcements on HN generate well under 100 points. That engagement signals real interest among developers and audio hobbyists, but the broader coverage landscape is thin: external listings are short tool-directory entries on sites like Building Beats and Tiorai, not hands-on reviews.
What’s the realistic track limit on a 4 GB Chromebook?
School-issued Chromebooks typically allocate under 2 GB of RAM to the entire browser process, shared across all open tabs. A stereo WAV at 44.1 kHz and 16-bit consumes roughly 10 MB per minute of raw audio. A project with five 5-minute WAV tracks approaches 250 MB before the editor’s own overhead. On a Chromebook, that leaves thin headroom for the browser, other tabs, and the OS. Three to four tracks of compressed-source audio is a practical ceiling for stable operation.
Could AudioMass add VST plugin support in its current architecture?
VST plugins are compiled native binaries (.dll, .so, .dylib) that require a host capable of loading shared libraries. A browser tab cannot load native shared libraries for security reasons. The only path to VST compatibility would involve WebAssembly compilation of a VST host, which AudioMass’s plain-JavaScript, no-WASM architecture explicitly avoids. The WebAudio API’s AudioWorklet interface could replicate simple effects in JavaScript, but supporting the VST ecosystem would require a fundamental architecture change.