Frequently Asked Questions

Yes, entirely. No account, no trial, no paid tier. Processing happens on your device, so there are no server costs to recover.

No. Your browser reads the file into memory and processes it locally through the Web Audio API. Nothing is transmitted to us or to anyone else, and nothing persists after you close the tab.

Whatever your browser can decode — typically MP3, WAV, OGG, FLAC, M4A, and the audio tracks of MP4 and WebM. Support varies slightly between browsers, and the tool reports clearly when a file cannot be decoded.

Up to 600% on most tools and 800% on the amplifier, which is roughly +15.6 dB and +18 dB. How much of that is usable depends on the file — a quiet recording takes the full range, an already-loud master hits the limiter early.

It depends on whether the audio is encrypted. Unprotected streams — YouTube, Twitch, SoundCloud — can be captured and amplified in Chrome or Edge on desktop. Anything delivered through DRM, which includes Netflix and the Spotify web player, is sealed off from browser audio processing and returns silence.

File boosting works in mobile browsers. Tab audio capture does not — the underlying API is desktop-only.

Not currently. The tools process audio in real time for playback. Offline rendering to a downloadable file is a planned addition.

Within the headroom a file already has, the change is a simple multiplication and you would struggle to tell it apart from the original played louder. Push past that and the compressor and soft-clipper start reshaping peaks, which costs dynamic range. The headroom meter is there so you can see exactly where that line falls for your file.

Under normal use, yes. Sustained heavy distortion at high volume can stress drivers over time. The more significant risk is to your hearing — see the note on every tool page.

No cookies are set and no analytics profile is built. The privacy policy sets out the full detail, including the server logs our host keeps.