Sound Forge Pro Mastering Guides

Home▸ Mastering

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.