Free Online Audio Mastering β Automatic, In-Browser
Thanks for using our free tools!
Want a heads-up when we ship new free browser tools? Drop your email β no spam, unsubscribe anytime.
Do track mastering right in your browser β free and with no registration. Drop in a finished mix, choose the platform β and the tool will bring the track to the right loudness on its own: it measures LUFS, True Peak and dynamics by the ITU-R BS.1770 standard and builds a processing chain β high-pass filter, EQ, glue compressor and true-peak limiter β for Spotify, Apple Music, YouTube, other streaming services, or CD. All online mastering runs locally: the file does not go to a server, we do not see it and do not store it. And this is not a neural network β the algorithm is deterministic, open, and predictable.
- Tool history
- How to master a track in three steps
- Targets: platforms, LUFS and True Peak
- A/B comparison: hear what really changed
- Settings for track character: Style, Density, Dynamics
- What the algorithm does: EQ, compressor, limiter
- When automatic mastering helps, and when it does not
- Private, deterministic, open
- About us
- Frequently Asked Questions
- Is the file uploaded to a server? What data do you collect?
- Is this AI mastering?
- How is this different from LANDR, eMastered or BandLab?
- Does this replace a human mastering engineer?
- What LUFS should I use for Spotify, YouTube and CD?
- Does browser mastering damage quality, phase or stereo?
- How should I mix and export before mastering? What formats are supported?
- What browsers are supported, and does it work on a phone?
Tool history
This is our internal tool. For years we used it as a script: automatically mastering mixes and songs before release. We also had our own A/B comparison program: which mix is better. We combined them here. Use it.
For us, mastering is technical work: bringing a recording up to spec for publication (Spotify, YouTube, CD β does anyone still make those? β or LP), not fixing mistakes. Everything else is solved earlier, at mixing β in the DAW, while you still have separate tracks. The mix is muddy β find the track that is making it muddy and cut the excess there. The vocal is not warm enough β warm its track. Not enough drums β raise their track. That is not mastering’s job: what comes here is an already mixed stereo mix β the separate tracks are gone, and it is too late to tweak them.
The mix lacks space β make the guitar or drums bigger; do not "widen" the record at mastering. And do not crank synthetic brightness and loudness for effect: the track flares up in the first five seconds, and after ten minutes that "improved" sound is impossible to listen to β your ears just get tired.
How to master a track in three steps
-
Add the track. Drag the file into the window (or click to choose). The best source for mastering is lossless: WAV, FLAC or ALAC, 24 bit, 44.1 kHz and up. In a couple of seconds the tool will measure loudness (LUFS), True Peak, dynamic range (LRA), sample rate, bit depth and duration β a waveform and player will appear under the metrics. A compressed lossy source (MP3, AAC/M4A, OGG) will work too, but mastering cannot bring back what the codec has already thrown away.
-
Choose the platform and sound character. Platform (Streaming, YouTube or CD), Style (Jazz, Hip-Hop, Electronic, Pop, Country, Rock, Metal), Density, Dynamics and Tempo (Slow / Normal / Fast). The algorithm will recalculate the targets itself.
-
Click Start and download the master. The top shows progress by stage (analysis β compression β limiting β check). The finished track appears below β with its own waveform, player and WAV download button.
You can change the settings and run online mastering again without reuploading the file. Each run is saved as a separate block β compare versions and download any of them.
Targets: platforms, LUFS and True Peak
Every platform has its own loudness and peak requirements. Choose the target β the rest is calculated automatically.
| Platform | LUFS | True Peak | Sample Rate |
|---|---|---|---|
Streaming |
β14 LUFS |
β1.0 dBTP |
unchanged |
YouTube |
β14 LUFS |
β1.0 dBTP |
48 kHz |
CD |
β9 LUFS |
β0.3 dBTP |
44.1 kHz, 16 bit |
Streaming β a universal preset for all music services at once: Spotify, Apple Music, YouTube Music, Amazon Music, Tidal, Deezer, SoundCloud. Preserves the source sample rate.
YouTube β for video; converts to 48 kHz, the standard for video platforms.
CD β classic 44.1 kHz / 16 bit with dithering; the target loudness is noticeably higher than streaming β a CD normalizes nothing: it plays exactly as loud as you master it.
|
Tip
|
Not sure β choose Streaming. This master will work for any platform, and most streaming services will normalize loudness to their own level anyway. |
The tool shows the loudness picture even before processing: Integrated LUFS β the perceived whole-track loudness by ITU-R BS.1770, the number streaming services compare against their normalization reference; True Peak (dBTP) β the reconstructed peaks, including inter-sample ones, which set the limiter ceiling; LRA β how much loudness moves around across the track. After mastering, the same metrics are calculated again β you see the "before/after" without the self-deception of "louder means better". For the full story behind these numbers and every service’s reference levels, see the LUFS meter page β it is also the tool to use when you only need to check loudness without processing.
A/B comparison: hear what really changed
Half the tool is honest A/B. After mastering, you can instantly switch between the original and the master (and between several master versions) at the same point in the song.
The key point is that comparison loudness is matched. So you do not hear "it got louder" (loud always seems better β that is the trap), but exactly what changed: density, clarity, balance, attack, air. This is how you check that the master opened up the track, not mangled it, and that the song stayed the way you intended.
Make several versions with different settings, compare them with each other, and download the one that sounds right.
Settings for track character: Style, Density, Dynamics
The same automatic mastering sounds different on jazz and on metal. Four switches define the character:
-
Style β starting settings for the genre: where to cut the low end, how fast compression reacts, how dense it gets. Metal and Electronic are faster and harder; Jazz and Country are softer and airier; Pop and Rock sit in the middle.
-
Density β how firmly the glue compressor holds the mix: Light (light glue), Medium, Heavy (dense leveling). You can turn it off entirely.
-
Dynamics β overall density and loudness: Dynamic (β14 LUFS, natural), Balanced (β12), Loud (β10), Very Loud (β9), Extreme (β8). As a rule, streaming services will bring anything louder than β14 back to their own level during playback β the listener’s track will not become louder. So going above β14 only makes sense for density and character, if the style needs it: Balanced and Loud are moderate, Very Loud and Extreme are already at the edge, where extra distortion starts to creep in. Not sure why you need it? Leave Dynamic, otherwise you will just overcompress the track for nothing.
-
Tempo β Slow, Normal or Fast (β 80 / 120 / 160 BPM). It controls the compressor release so it "breathes" in time with the music; the exact BPM can be entered in the Advanced block.
The starting values already account for track analysis; everything can be overridden manually in the Advanced block.
What the algorithm does: EQ, compressor, limiter
Mastering is not "make it louder". It is a careful chain of four steps.
High-pass filter (HPF). Cuts sub-bass junk below 15β50 Hz (the exact frequency depends on genre and density); it sits before the compressor so the compressor does not react to infrasound.
EQ. Five bands for final tonal polish β not "painting", but correction. If the mix is balanced, you can leave EQ alone.
| Band | Frequency | Purpose |
|---|---|---|
Low End |
80 Hz |
Weight and sub-bass if the mix sounds thin |
Warmth |
150 Hz |
Body and fullness in the lower mids |
Mud |
290 Hz |
Cuts "mud" and boominess (down only) |
Brightness |
8 kHz |
Clarity and vocal intelligibility |
Air |
12 kHz |
Air and openness in the top end |
Glue compressor. Glues the mix and adds punch. The threshold is calculated not from random peaks, but from the loudest sections of the track (95th percentile short-term LUFS) β the compressor reacts to choruses and drops, not to a single stick click. Ratio, attack, release and knee are selected from Style + Density + Dynamics; for jazz and classical, it can be turned off to preserve live dynamics.
True-peak limiter. Raises loudness to the target and keeps peaks under the ceiling: over several passes it measures the actual LUFS and adjusts gain until it lands on target within about 0.1 dB; oversampling (4Γ or 8Γ) catches inter-sample peaks that would otherwise appear after conversion to MP3/AAC. If the selected loudness is too high for this material, the limiter does not drive the track into overload for the sake of a number β it stops at the closest safe level.
When automatic mastering helps, and when it does not
Helps when you have a finished mix that needs to be brought to streaming loudness: steady level, platform standards, tidy glue, and clipping protection. For most tracks going to Spotify and YouTube, that is enough.
Also useful for checking a mix while you work. Working versions are usually quiet, and each one has its own loudness β you cannot honestly compare them with finished tracks on YouTube or Spotify, because loud always seems better. One click β and a working mix becomes a release-level mastered copy: you can put it next to a reference at equal loudness and hear what in the mix actually needs fixing.
Does not replace a human mastering engineer where artistic decisions and fixing mix problems by ear are needed β a major-label album, vinyl, soundtrack. And it does not fix the mix itself: phase problems, dirty low end, buried vocal, skewed instrument balance are fixed earlier, during mixing β in the DAW, while you still have the separate tracks. Automation will not save a bad mix; it will bring a good one up to level.
If the problem is guitar tone, first shape the cabinet sound with the cabinet IR utility, and only then master it.
Private, deterministic, open
No server upload: all mastering in the browser runs on your device β we do not see your audio, do not store it, and cannot recover it. Close the tab β and nothing is left anywhere. This is useful when the track is not out yet and you cannot send it outside before release. We collect only anonymous usage stats: which preset was chosen, loudness values before/after, processing time, file name and size β no IP address, User-Agent, cookie or fingerprint. The audio bytes themselves are not sent anywhere.
And no ChatGPT, neural networks, or "black box": the algorithm is deterministic β it measures your track, looks at the platform requirements, and calculates settings by explicit formulas. The same file with the same settings gives exactly the same result every time β unlike AI services, where a repeated run can sound different. All settings are visible and can be overridden manually in the Advanced block.
The engine is open: all the real work β loudness measurement, EQ, compression, true-peak limiting, WAV encoding β is done by FFmpeg (ffmpeg.org, license LGPL-2.1+), compiled to WebAssembly via ffmpeg.wasm (MIT, source: github.com/ffmpegwasm/ffmpeg.wasm). The waveform and player on the page are drawn by our own Canvas code β no third-party libraries. Thanks to the authors of the open projects.
About us
Darwin’s Cat is a rock band from Berlin. We make music and tools for our own work, then open them to everyone. Listen: Darwin’s Cat Β· Contact: band@darwinscat.com Β· Support: buy us a beer.
Frequently Asked Questions
Is the file uploaded to a server? What data do you collect?
No β and we collect almost nothing. Mastering runs entirely in the browser, on your device: the audio bytes do not leave your computer, we do not see your file, do not store it, and cannot recover it after you close the tab. We collect only anonymous usage stats β which preset was chosen, loudness values before/after, processing time, file name and size β with no IP, User-Agent, cookie or fingerprint, to improve defaults. The sound itself is not sent anywhere.
Is this AI mastering?
No. We do not use ChatGPT, neural networks, or any other AI. The algorithm is completely deterministic: it measures your track (loudness, dynamic range, loudest sections), looks at platform standards, and calculates settings by explicit formulas. The same file with the same settings gives exactly the same result every time. All settings are visible and can be overridden manually in the Advanced block.
How is this different from LANDR, eMastered or BandLab?
Principally, it is not a "free alternative". We take your mix and bring it to the technical parameters needed for publication: loudness, peaks, balance. The output is your track, the same sound, style and voice, just ready for release. AI services like LANDR work differently: they analyze the track, guess the genre in their own way, and apply their own interpretation β you get a version you did not make, and the character can drift beyond recognition.
So calling us a "free LANDR" is wrong: we do something else β and, if preserving your intent matters to you, we do it better. On top of that: free and no registration, the file does not go to a server, the algorithm is deterministic and transparent, and the engine is open.
Does this replace a human mastering engineer?
For most music going to streaming services, it covers the technical part: steady level, loudness standards, careful compression and true-peak limiter, with light EQ correction if you want it. Just do not confuse the stages: mixing is the balance of instruments inside the track and happens earlier, in the DAW; mastering works with the finished stereo mix as a whole.
If you are making an album for a major label, a vinyl release or a soundtrack, those need artistic decisions and problem-fixing by ear that automation will not make; a human engineer is still needed. And remember: mastering will not save a bad mix, but it will bring a good one up to level.
But for test and working mixes, there is no need to bother an engineer β just run them through our tool.
What LUFS should I use for Spotify, YouTube and CD?
The safe universal reference is β14 LUFS with a True Peak ceiling of β1 dBTP; this is the Streaming preset (Spotify and YouTube use the same reference β they normalize playback loudness). For CD β β9 LUFS / β0.3 dBTP: a CD normalizes nothing, so the target loudness is higher. Going louder than β14 for streaming only makes sense for genre density, not for loudness β the services will bring the track back to their own level anyway. The exact number is calculated from platform + Style + Dynamics and is visible right in the form.
Does browser mastering damage quality, phase or stereo?
There is nothing "browser" about it in the bad sense β processing is done by the same FFmpeg as in offline tools, at full quality. Mastering does not rebuild the stereo image and does not break phase: it applies exactly the chain you see (HPF, EQ, compressor, limiter). Any EQ, as in a DAW, slightly moves phase in the bands it touches β that is normal processing, not a defect. The tool changes sample rate only if you choose a different output Sample Rate yourself (48 kHz for YouTube, 44.1 kHz / 16 bit with dithering for CD).
How should I mix and export before mastering? What formats are supported?
The best source is lossless: WAV, AIFF, FLAC or ALAC, 24 bit, 44.1 kHz and up. Export so peaks do not clip on the master bus β leave 3+ dB of headroom. If the track comes out quiet, that is fine: the tool will measure the loudest sections and normalize it itself. Almost any audio is accepted β lossless (WAV, AIFF, FLAC, ALAC, WavPack), common (MP3, M4A, AAC, OGG, Opus) and legacy/niche (WMA, APE, AMR, MP1/MP2): everything is decoded right in your browser, the file is not uploaded β but mastering cannot bring back what a lossy codec has already thrown away. You can download the finished master as WAV, AIFF, FLAC, ALAC, AAC or MP3. The limit is about 200 MB or 15 minutes of audio: browser memory is limited.
What browsers are supported, and does it work on a phone?
Any modern desktop browser β Chrome, Firefox, Safari, Edge. On mobile it technically works, but processing is noticeably slower; for tracks longer than a minute or two, desktop is better.
Comments
Be the first to leave a comment.