Performance

How fast is a DJ app in a browser?

Fast enough to open a 2,100-track library in 88 ms and to draw a four-hour set at 60 frames a second. Here is every number we have measured, how we measured it, and what we have not measured yet.

88 msto open a library of 2,100 real tracks

0 of 600frames dropped while panning a 40-track set of 3 h 49 min

91 msfrom Play to the first sound

500×real time: the speed at which the engine mixes your set

< 2 sto analyze a track: beat grid, BPM, key, and energy

1.8%of one CPU core for two live decks in Perform mode

Why it is fast

Mixpoint is not a web page that waits on a server. It runs on your computer, and each heavy job has its own thread, so the screen never waits for the audio and the audio never waits for the screen.

Your librarySQLite, compiled to WebAssembly, in the browser's private file storage. Queries run in their own thread.

The timelineDrawn on its own thread with OffscreenCanvas, so a pan or zoom never blocks playback.

DecodingYour tracks are decoded by the browser's built-in codecs (WebCodecs), the same ones that play video.

The mixRendered 10 s ahead in a worker, then played by an AudioWorklet on the browser's real-time audio thread.

Live decksIn Perform mode, a separate engine mixes in real time, so a knob turn is heard in the next 3 ms block of audio.

AnalysisBeat grids, keys, and energy in background workers. Vocal detection runs a neural network on your graphics card (WebGPU).

Your music stays on your computer: nothing is uploaded to be analyzed or played, unless you choose to keep your tracks in your account for a second device.

The numbers

Each row says what we measured and under which conditions. "Dev build" means the development server, which is usually slower than the app you get.

Library

What	Result	Conditions
Page load to the first tracks on screen	88 ms	2,100 real tracks, production build
Page load to the first tracks on screen	89 ms	5,000 generated tracks, production build
Open the database	33–60 ms	5,000 generated tracks, production build
Keystroke to an updated search result	4.6–12.2 ms	5,000 generated tracks, production build
Scroll through the whole list	Median frame 16.7 ms, 0 frames over 20 ms	5,000 generated tracks, production build

Import

What	Result	Conditions
Open your DJ software's library	About 2 s	2,100 tracks, a 128 MB database, production build
Import every track	2.0 s	1,893 new tracks, with beat grids, cues, and waveforms; 0 read errors
Add a music folder	2.7 s	100 files, dev build
Scan the same folder again	54 ms	100 files, nothing changed, dev build

Timeline

What	Result	Conditions
Frames over 20 ms while panning and zooming	0 of 600	A real 40-track set of 3 h 49 min, zoom range ×64, dev build
Slowest frame interval	16.8 ms (60 fps)	Same
Draw time per frame	0.75 ms average, 2.2 ms at the 95th percentile	Same, working zoom

Playback

What	Result	Conditions
Play to the first sound	91 ms	Cold start, dev build
Seek to the first sound	58 ms	Dev build
Mix render speed	About 500× real time	Dev build
Mix with key lock	10 s of audio in 202 ms (about 50× real time)	Dev build
Beat sync between tracks	Worst error 0.02 ms	Three tracks at 120, 124, and 128 BPM; 215 beats checked
Dropouts	0	Three real tracks on three lanes, and while dragging a track during playback

Perform mode

What	Result	Conditions
CPU for two live decks	48–52 µs per 2.9 ms block: 1.8% of one core	Every control moving, a nudge held, echo on
Delay that the engine adds to a key press or knob turn	Under 3 ms	Your audio device adds its own delay (see Limits)
Audio buffered per deck	3 s ahead, 0 dropouts	Two decks

Analysis

What	Result	Conditions
Full analysis of a track	1.6–1.9 s	Decode, beat grid, BPM, key, energy, waveform; 3 MP3s, dev build
Vocal detection	About 1 minute for a 6-minute track (6× real time)	On the graphics card (WebGPU), MacBook Pro with M3 Pro
Phrases of a track	About 1 ms	When a set opens

Export

What	Result	Conditions
Export a set to your DJ software, backup and checks included	11 s	6 tracks, a 128 MB library

Limits we know of

We would rather you hear these from us.

Chrome, Edge, or Arc on a computer. Safari and Firefox cannot open folders of music yet, and phones are not supported.
Your audio device sets the live delay. Mixpoint adds under 3 ms, but Bluetooth headphones and speakers often add 150–250 ms. Use a wired output or your controller's sound card to perform.
Vocal detection takes time. About a minute for a 6-minute track on a MacBook Pro with M3 Pro, and it runs only when you ask for it.
Analysis pauses during playback, so it does not compete with the audio.
One tab at a time. A second tab opens a temporary library.
A jump to a hot cue in Perform mode leaves 12–29 ms of silence. This is a known issue.

How we measured

The numbers come from single manual runs during development in 2026, in Chromium on a Mac. Vocal detection was measured on a MacBook Pro with an M3 Pro; the other rows were measured on our development machine. Several rows used the development build, which is usually slower than the production build. We have not measured slower laptops or Windows yet, nor a full hour of playback. We will add those runs here, with the same detail.

Not yet measured: memory use across all threads, sort speed, decode speed per format, libraries above 5,000 tracks, and load time over the network.

Hear it for yourself.

Free during the beta. Sign in with your email and start planning.

Start free

Runs in Chrome, Edge, or Arc on a computer. Nothing to install.