How to limit true-peak to -1 dbtp
- Step 1Have your finished master ready — Export the final mix from your DAW, ideally as WAV or FLAC so the limiter works on the cleanest source. If you're chasing both loudness and peak compliance, normalize loudness first with loudness-normalizer and use this tool as the final ceiling check.
- Step 2Make sure you're on Pro — The limiter is Pro-gated; Free accounts see a 'requires a Pro subscription' message. Pro handles up to 200 MB / 120 minutes per file; Pro + Media and Developer go to 100 GB with no duration limit.
- Step 3Drop your file onto the tool — FFmpeg WebAssembly processes the audio locally. Accepted input is any audio FFmpeg can decode — MP3, WAV, FLAC, M4A/AAC, OGG, Opus. The buffer stays in your browser tab.
- Step 4Leave the ceiling at -1.0 dBTP — The dropdown defaults to -1.0 dBTP · standard — exactly the value this page is about, so there's nothing to change. If you want extra margin you can pick -1.5 or -2.0 dBTP, but -1.0 is the streaming convention.
- Step 5Pick your output format — WAV (16-bit PCM) or FLAC (lossless) for an archival -1 dBTP master; MP3 (192 kbps) or M4A/AAC (192 kbps) for a direct upload. The limiter applies before encoding, so the ceiling holds in every format.
- Step 6Download and read the reported peak — Confirm the achieved peak the tool reports sits at -1.0 dBFS (or marginally above — see the edge cases on sample-peak vs inter-sample). That's your proof the file is at the streaming ceiling, ready to upload.
What -1.0 dBTP means at each stage
How the single -1 dBTP target flows through the tool, from your dropdown choice to the verified output.
| Stage | Value | Detail |
|---|---|---|
| UI selection | -1.0 dBTP · standard | The default option; no change needed for the streaming-standard ceiling |
| Linear limit to alimiter | ≈ 0.891251 | 10^(-1/20); passed as alimiter=limit=0.891251:level=disabled |
| Filter behaviour | Look-ahead brickwall | Only samples above the ceiling are reduced; the rest pass through |
| Verification | ebur128=peak=true | Output re-measured; achieved peak reported in dBFS |
| Typical result | ≈ -1.0 dBFS | May read a touch higher due to inter-sample reconstruction — the margin is intentional |
Why platforms standardised on -1 dBTP
Loudness specs published by major platforms pair an integrated LUFS target with a true-peak ceiling. -1 dBTP is the common ceiling. (Use loudness-normalizer to hit the LUFS figures.)
| Platform | Integrated LUFS | True-peak ceiling | This tool's matching option |
|---|---|---|---|
| Spotify | -14 LUFS | -1 dBTP | -1.0 dBTP · standard |
| Apple Podcasts | -16 LUFS | -1 dBTP | -1.0 dBTP · standard |
| YouTube | -14 LUFS | -1 dBTP | -1.0 dBTP · standard |
| Amazon Music | -14 LUFS | -2 dBTP | -2.0 dBTP · Amazon |
| EBU R128 broadcast | -23 LUFS | -1 dBTP | -1.0 dBTP · standard |
Cookbook
Concrete -1 dBTP jobs. Peak figures reflect the dBFS ebur128 reports after the limiting pass.
Master at -0.3 dBFS pulled to the -1 dBTP ceiling
A master that peaks just under full scale still has no margin for codec overshoot. The default -1.0 dBTP option pulls it back to the streaming-safe ceiling in one pass.
Input: master.wav, sample peak -0.3 dBFS Ceiling: -1.0 dBTP · standard (default) Format: WAV Output: master-limited.wav ebur128 reported peak: -1.0 dBFS Ready for Spotify / Apple / YouTube upload.
Confirm a delivered master is already at -1 dBTP
Sometimes you just need to verify a file someone sent you. Run it at -1.0 dBTP: if it's already compliant, nothing audible changes and the reported peak confirms it.
Input: delivered-master.flac (claims -1 dBTP) Ceiling: -1.0 dBTP · standard Format: FLAC Output peak reported: -1.0 dBFS Limiter engaged on nothing → file confirmed at the ceiling.
Loudness-normalize to -14 LUFS, then guarantee -1 dBTP
The full Spotify recipe: normalize loudness, then pin the peak. The loudness-normalizer applies its own true-peak limit, and this pass guarantees the ceiling didn't drift.
Step 1: loudness-normalizer, preset Spotify → -14 LUFS, -1 dBTP Step 2: true-peak-limiter, ceiling -1.0 dBTP (default), WAV Result: -14 LUFS, peak confirmed -1.0 dBFS. Both loudness and ceiling locked.
Batch-style single-file limiting to -1 dBTP
Pro processes one file at a time, so for a set of tracks you run each through the same default. The consistent -1.0 dBTP ceiling means every track shares the same headroom for the platform encoder.
track01.wav → ceiling -1.0 dBTP → track01-limited.wav (-1.0 dBFS) track02.wav → ceiling -1.0 dBTP → track02-limited.wav (-1.0 dBFS) track03.wav → ceiling -1.0 dBTP → track03-limited.wav (-1.0 dBFS) Uniform ceiling across the release.
Output MP3 directly at the -1 dBTP ceiling
When you want a ready-to-upload lossy file, the limiter applies before the 192 kbps MP3 encode, so the ceiling is baked in before encoding.
Input: master.wav Ceiling: -1.0 dBTP · standard Format: MP3 (192 kbps) Output: master-limited.mp3 Peak reported: ~-1.0 dBFS Limiting applied pre-encode → ceiling survives the MP3 stage.
Edge cases and what actually happens
Reported peak reads -0.9 dBFS instead of exactly -1.0
By designalimiter enforces a sample-peak ceiling; ebur128's verification reads true-peak-style and can sit a fraction above the sample ceiling because of inter-sample reconstruction. A reading like -0.9 dBFS after a -1.0 dBTP limit is normal and exactly why -1 (not 0) is the target — the margin absorbs the difference. For a guaranteed wider gap, pick -1.5 or -2.0 dBTP.
File is already quieter than -1 dBTP
PreservedIf no peak exceeds -1.0 dBTP, the limiter doesn't engage and the audio is unchanged apart from the format re-encode. The ebur128 pass still confirms the peak. The limiter never raises level — it's a ceiling, not a maximizer. To make a quiet file louder, use volume-normalizer.
Free account
Requires ProLimiting to -1 dBTP needs Pro. Free accounts get a 'requires a Pro subscription' message. Pro handles 200 MB / 120 min per file; higher tiers go to 100 GB with no duration cap.
Want -1.2 or some other exact ceiling
Not in UIThe browser dropdown offers only -1.0, -1.5, -2.0, and -0.3 dBTP. There's no free-text ceiling field. The MCP/API schema accepts any value from -6 to 0 dB for automated callers, but this page's tool uses the four presets — and for the streaming standard, -1.0 is exactly what you want.
Expecting the tool to also set loudness to -14 LUFS
Wrong toolThis tool only sets the peak ceiling; it doesn't measure or target LUFS (the result shows peak in dBFS, loudness as not-measured). To hit -14 LUFS for Spotify, run loudness-normalizer first — its two-pass EBU R128 also applies -1 dBTP, after which this tool is a confirmation pass.
Pro file over 200 MB or 120 minutes
Limit exceededPro's per-file caps are 200 MB and 120 minutes, checked independently. A long lossless master can exceed size before duration. Convert to FLAC with wav-to-flac to reduce size, split with audio-splitter, or move to Pro + Media (100 GB, unlimited duration).
Limiting an MP3 that's already lossy
SupportedYou can limit an existing MP3, but outputting MP3 again stacks a second lossy generation. If quality matters, output WAV or FLAC from this tool. Limiting itself is fine on lossy input — alimiter just acts on whatever samples breach -1 dBTP.
Stereo file expected to stay stereo
PreservedThe limiter doesn't downmix — a stereo input stays stereo, mono stays mono, and the sample rate is preserved. If you need a channel or sample-rate change, use channel-splitter or sample-rate-converter separately.
ebur128 can't parse a peak from a malformed file
Verification errorIf the limited output is unreadable by the verification pass, the tool reports it couldn't parse a true-peak. This usually points to a corrupt or truncated source file. Re-export the master from your DAW and try again — the limiting itself completes; it's the metering that fails on bad data.
Heavily limited file sounds squashed
Source too hotIf a master is bounced well above 0 dBFS, pulling it to -1 dBTP means constant limiting, which can dull transients. That's a mixing issue, not a limiter fault — leave more headroom in the bounce, or normalize loudness first so the limiter only catches occasional peaks rather than the whole signal.
Frequently asked questions
Why -1 dBTP specifically and not 0?
Lossy codecs (MP3, AAC, Opus) reconstruct the waveform between your samples on decode, and those reconstructed inter-sample peaks can exceed 0 dBFS even when every sample sits at or below it. A -1 dBTP ceiling leaves headroom so that overshoot doesn't clip. Spotify, Apple Podcasts, and YouTube all standardised around this value.
Do I need to change any setting to hit -1 dBTP?
No — -1.0 dBTP · standard is the default option in the dropdown. Just drop your file and download. You'd only change the ceiling if you specifically wanted more margin (-1.5/-2.0 dBTP) or a hotter file (-0.3 dBTP).
How is the -1 dBTP ceiling actually applied?
The -1 dB ceiling is converted to a linear amplitude — 10^(-1/20) ≈ 0.891 — and passed to FFmpeg's alimiter as alimiter=limit=0.891251:level=disabled. alimiter is a look-ahead brickwall limiter. The output is then re-measured with ebur128=peak=true so you see the achieved peak.
Will my reported peak be exactly -1.0 dBFS?
Usually within a fraction of it. alimiter is sample-peak based and ebur128 reads true-peak-style, so the verification can read slightly above the linear ceiling. That small difference is precisely why -1 dB is the target rather than 0 — it's the safety margin doing its job.
Is limiting to -1 dBTP enough for Spotify?
It satisfies Spotify's true-peak side (-1 dBTP). Spotify also normalizes loudness toward -14 LUFS, so for full compliance run loudness-normalizer (Spotify preset) first, then this tool as the ceiling guarantee. Limiting alone handles peaks, not loudness.
Can I do -1 dBTP on a free account?
No. The limiter is Pro-only. Free accounts can't run it. Pro processes up to 200 MB / 120 minutes per file; Pro + Media and Developer go to 100 GB with no duration cap.
Does the file upload anywhere to apply the ceiling?
No. FFmpeg runs as WebAssembly in your browser, and the audio buffer stays on your machine. Only an anonymous usage counter is recorded for dashboard stats — never the audio itself.
What format should I output for a -1 dBTP master?
WAV or FLAC if you want a lossless -1 dBTP master to archive or hand off. MP3 or M4A (both 192 kbps) for a ready-to-upload file. The limiting is applied before encoding, so the ceiling holds in any output format.
Will -1 dBTP limiting reduce my loudness?
Only where peaks exceed -1 dBTP do those instants get pulled down; the overall level barely moves unless the file is constantly clipping the ceiling. If a master sounds quieter than expected after limiting, it was probably over-hot to begin with.
Can I run this on an already-mastered streaming file?
Yes — it's a common final check. Run it at -1.0 dBTP; if the file already complies the limiter changes nothing audible and the reported peak confirms it. If it was hotter than -1 dBTP, the tool brings it into spec.
How does this differ from peak normalization?
Peak normalization scales the whole file so the loudest peak hits a target — it can make quiet files louder. This limiter only pulls down peaks above the ceiling and never raises level. For scaling a quiet file up, use volume-normalizer; for a hard ceiling, use this.
What if I need a different ceiling later, like for Amazon?
Just re-run with the -2.0 dBTP · Amazon option. Each pass is independent and non-cumulative for overs already under the ceiling, so switching ceilings between platforms is safe. The four ceiling options cover the mainstream platform specs.
Privacy first
Every JAD Audio tool runs entirely in your browser via FFmpeg (WebAssembly) and RNNoise. Your audio files never leave your device — verified by zero outbound network requests during processing.