How local audio processing works

When you open AudioDock, your browser downloads the application code once, exactly the way it would load any website. After that, the heavy lifting happens on your own device rather than on a remote server. There is no per-file round trip to the cloud.

For most tasks — trimming, fades, volume changes, normalization, reversing, merging, sample-rate and channel changes — AudioDock uses the browser's built-in Web Audio API. For conversions that require a real codec, such as encoding an MP3 or OGG or extracting the audio track from a video, it uses ffmpeg compiled to WebAssembly: the same trusted engine that desktop tools rely on, running inside your tab.

Everything described here happens inside your browser tab. AudioDock loads the page once, then does all of the audio math locally using the Web Audio API. Your file is opened with the File API, decoded into memory, processed, and offered back to you as a download. No part of it is sent to a server — you can confirm this yourself by opening your browser devtools, switching to the Network tab, and watching it stay empty while you work.

Because everything runs locally, two things follow. First, performance depends on your device — a faster machine processes large files more quickly, and very large files use more memory while they are open. Second, and more importantly, your audio is never transmitted anywhere. The trade-off is almost always worth it: a little of your device's effort in exchange for genuine privacy and no waiting on uploads.