Mastering in Sound Forge Pro: chain, loudness and honest metering
Sound Forge earned its keep as a stereo mastering editor, and the chain hasn't changed in spirit: cleanup → EQ → dynamics → limiting → measure → dither → export. The part most people skip is measuring — which is why the Statistics guide sits right next to the chain guides. Master to a LUFS target you actually verified, not to how loud it feels on your monitors at midnight.
Sound Forge Pro Mastering Workflow
| Step | Use this when | Guide |
|---|---|---|
| Chain | You need the full mastering order: cleanup, EQ, dynamics, limiting, LUFS, dither and export. | Sound Forge Pro for Mastering |
| Quick | You want to master one track without reading the full chain guide. | How to Master a Track in Sound Forge Pro |
| EQ | You need Paragraphic EQ, filter types, Q settings and corrective EQ moves. | How to Use the Equalizer in Sound Forge Pro |
| Tools | You want to build and save a repeatable mastering chain. | How to Use the Plug-In Chainer |
| Verify | You need LUFS, true peak, RMS and loudness range before delivery. | Sound Forge Pro Statistics |
| Space | Special-case mastering or restoration work: reverb tails, ambience, Acoustic Mirror, room matching. | How to Add Reverb in Sound Forge Pro |
| Fix | VST plugins are missing, blacklisted or not scanning. | Sound Forge Pro VST Plugins Not Showing |
What Each Mastering Guide Covers
- Full mastering guide: the complete chain from pre-checks to final export.
- Master one track: a faster workflow for a single stereo file.
- Equalizer: corrective and tonal EQ before compression or limiting.
- Plug-In Chainer: how to build, preview and save a repeatable chain.
- Statistics: LUFS, true peak, RMS, LRA and final verification.
- Reverb: space, tails and Acoustic Mirror when the master needs ambience — a special case, not a required chain step.
- VST fixes: scan paths, VST2/VST3 mismatch and missing mastering plugins.
What LUFS should I master to?
For Spotify-style music streaming, -14 LUFS integrated with peaks below -1 dBTP is a safe practical baseline, and Spotify itself normalizes playback around -14 LUFS. Treat it as a verification target, not a law: dense rock, electronic, jazz, classical, CD, broadcast and podcast work may need different loudness decisions. Verify with Sound Forge Statistics instead of trusting how loud the master feels on your monitors.
Do I need Ozone for mastering in Sound Forge Pro?
No. The built-in workflow — Paragraphic EQ, Wave Hammer, Plug-In Chainer, LUFS normalization, Statistics and dither — covers competent stereo mastering. Ozone Elements is only relevant if your MAGIX-era Sound Forge Pro install actually bundled it, or if you already own Ozone as a separate VST.
When should I dither in Sound Forge Pro?
Dither only when reducing bit depth, usually from a 24-bit or 32-bit float master down to 16-bit for CD or a specific delivery requirement. Do it last, after EQ, dynamics, limiting, normalization and final gain changes. Do not dither a 24-bit streaming master just because it is the final export.
Why use Statistics instead of only a loudness plugin?
Statistics scans the whole selected file and gives a final delivery check for integrated LUFS, true peak, RMS and loudness range. Real-time plugin meters are useful while working, but the Statistics pass is the safer final verification before export.
All Mastering guides
WAV vs FLAC vs MP3 for Editing, Mastering and Archive
A practical guide to choosing WAV, FLAC or MP3 for active editing, mastering, long-term storage, client handoff and listening copies.
Open clip →
Audio Export QA Checklist: Catch Problems Before Delivery
A repeatable pre-delivery check for audio format, channel layout, loudness, peaks, metadata, render boundaries and file integrity.
Open clip →
What Is True Peak? dBTP, Sample Peak and Codec Headroom
Understand dBTP, inter-sample peaks and codec headroom, then verify the encoded file instead of trusting the source meter alone.
Open clip →
Streaming Loudness Standards: What Platforms Publish
Separate master loudness, upload requirements, distribution gain and listener playback before choosing a LUFS or true-peak reference.
Open clip →
Podcast Loudness Standard: LUFS, True Peak and Export Check
Choose a defensible podcast loudness target, separate platform guidance from playback normalization, and verify the encoded file—not only the master.
Open clip →
Free Online LUFS Meter: Loudness & True Peak
A private browser loudness check with integrated LUFS, LRA, estimated true peak, sample peak and a peak-aware gain plan.
Open clip →
Sound Forge Wave Hammer: Compressor & Maximizer Guide
A measured classic Wave Hammer workflow for compression, level-matched bypass checks, sample-peak control, rendering, and separate LUFS and true-peak verification.
Open clip →
Sound Forge Loudness Meter: LUFS, R128 & True Peak
A standards-checked Sound Forge workflow for Integrated LUFS, LRA, True Peak, loudness logs, and final-file verification.
Open clip →
Sound Forge VST Plugins Not Showing? 7 Fixes (2026)
If a VST effect is missing in Sound Forge, check the installed effect build and its folder before reinstalling the
Open clip →
How to Read Sound Forge Statistics: RMS, Peaks & DC Offset
Quick answer: select the exact audio you intend to judge, choose Tools → Statistics, and copy only the fields required by
Open clip →
Sound Forge Pro for Mastering (Full Guide)
Master Sound Forge Pro with EQ, Wave Hammer, Ozone Elements, LUFS targets, Statistics checks, dithering, exports, and genre settings properly.
Open clip →
VST Plugin Chainer on Windows: Build and Save Chains in Sound Forge
Build a reliable VST effect chain in Sound Forge: choose the right host workflow, order processors, preview safely, save presets and avoid bad renders.
Open clip →