Workflow · Mastering
A master can sound right on your monitors and still arrive wrong. Specula shows the gain each streaming service will apply to the file, alongside the true peak, loudness range, stereo width, and phase behind that number. When the readings look close, audition the master the way Spotify or Apple Music will actually play it.
Sounds right, fails at delivery
The master is finished. Whether it survives Spotify, Apple Music, and the rest is a separate question, one your DAW doesn't answer.
Three things go wrong between "done" and "uploaded," and none of them are audible on a quiet pass through your monitors. The integrated LUFS overshoots and Spotify turns the track down. The master is quieter than reference and Apple Music dims it, or leaves it exactly where it is, depending on the platform. And a "stereo" file is secretly mono on the verses or out of phase in the bridge, so it collapses on a phone speaker. Each of these is a number the file already contains. Specula reads them out before the file goes anywhere.
The delivery check
Open the master, read the platform rows, audition at the target, export the PDF.
target − source LUFS, with a 5 ms lookahead true-peak limiter at the target's dBTP ceiling (enforced on the 4× oversampled inter-sample peak, not just the sample magnitude). Hit play and hear the master the way the platform will play it. The loaded buffer is never modified; release the toggle to restore unity gain.dBTP ceiling as the only editable field. Review, click Apply, and export: the whole file is shifted by one uniform gain, then a two-pass true-peak limiter holds the ceiling. It lands on the 16-level undo stack and writes a new file. When the level is already where you want it and only the peaks breach the ceiling, the row's Limit TP button clears the overage in one click while the loudness stays put, the same flow as Normalize but for inter-sample peaks only. And because Normalize and Limit TP both respect a time selection, a single hot passage can be tamed on its own while the rest of the master stays as rendered. Only the ACX RMS target stays compliance-only with no Normalize button, since a gain can't satisfy its noise-floor requirement. More in the guide.Not every platform boosts
The truth about quiet masters. Apple Music's Sound Check, YouTube, and Tidal only turn loud tracks down; they leave a quieter-than-reference track exactly where it is. So a master at −18 LUFS doesn't get pushed up to Apple Music's −16 reference, it plays at −18. On those three platforms Specula shows a quiet master as "as-is" in green.
The platforms that do boost. Spotify (in its default mode), Amazon Music, Deezer, and SoundCloud raise quiet tracks peak-limited to reach their reference, so for those rows the +X dB number is real and Specula shows it unchanged. The distinction matters because it changes what you do next: a master that reads "as-is" on Apple Music but "+3 dB" on Spotify is being treated as two different deliverables by two services, and only one of them is touching your level.
The Music catalog covers Spotify (−14 LUFS), Apple Music (−16), YouTube (−14), Tidal (−14), Amazon Music (−14, −2 dBTP ceiling), Deezer (−15), SoundCloud (−14), and the vendor-neutral AES TD1008 (−18). Each row's subtitle states whether it's symmetric or "turns down only," so the behaviour is on the row, not in your head. The live panel updates as the file plays; the full catalog with references, tolerances, and true-peak ceilings is in the user guide.
On screen
Before the master ships
Nothing on this page masters the track for you. What Specula gives you is the state of the finished master: the exact gain each platform will apply, whether the true peak clears the ceiling, whether the stereo image holds up in mono, and a way to hear all of it before the first service touches the file.