To master a finished stereo track in Sound Forge Pro 2026, use a short chain with a clear job at each stage: Modern Equalizer → Wave Hammer → loudness/true-peak verification → Bit-Depth Converter only if required → export. Keep an untouched source and level-match every bypass comparison. If a processor does not solve a problem you can hear, remove it.
This is the practical, one-track workflow. The broader Sound Forge mastering guide covers delivery formats, album consistency and platform decisions. Here the focus is the current tools and the order that keeps corrections reversible and measurable.
Quick answer: scan the source with Tools → Statistics, make small gain-matched corrections in Modern Equalizer, use Wave Hammer’s compressor and Volume Maximizer conservatively, rescan integrated LUFS and true peak, then dither once only if the final file must be reduced to 16-bit.
Before mastering: make a source copy and measure it
Start from the finished stereo mix at its native sample rate and bit depth. Don’t overwrite the only copy. If the mix already clips, contains vocal/instrument balance problems or has heavy bus limiting you cannot undo, go back to the mix when possible. Mastering can shape a stereo file; it cannot independently lower a snare or repair a clipped vocal without affecting everything around it.
Open the full track and choose Tools → Statistics. Record:
- maximum sample value;
- maximum true peak and filtered true peak;
- integrated LUFS;
- maximum short-term and momentary loudness;
- loudness range (LRA).
The current Sound Forge 2026 Statistics help defines short-term as a 3-second window and momentary as 400 ms. Those baseline numbers are not targets by themselves. They are the before-state you compare with the finished master.
Step 1: Correct balance with Modern Equalizer
Use the current Modern Equalizer, not an old Paragraphic EQ screenshot as your default reference. Sound Forge 2026 documents an eight-band parametric EQ with high/low-pass, shelves, peaking and band-pass filters, Left/Right/Mid/Side processing, Output Gain, A/B memories, Bypass and up to 8× oversampling.
- Load Modern Equalizer in the track’s Plug-In Chain.
- Loop a representative loud section and a quieter section.
- Make one broad correction at a time.
- Use Output Gain to match the processed loudness to bypass.
- Compare A/B without letting the louder version win automatically.
There is no universal “cut 200 Hz, boost 8 kHz” mastering recipe. A broad 1 dB move can be significant on a stereo mix. Use the analyzer to locate energy, then decide with your ears and references. If a narrow problem changes from note to note, a static cut may damage more than it fixes.
The full current control set is documented in Boris FX’s Modern Equalizer help.
Step 2: Control peaks with Wave Hammer
Wave Hammer is the Sound Forge-specific processor at the center of this workflow. The current 2026 help describes it as two processors in one: a classic compressor and a Volume Maximizer. Use them as two separate decisions, not as a one-click loudness preset.
Compressor stage
Start with the maximizer bypassed. Set the compressor so the loudest sections are controlled without pulling ambience and cymbal decay forward in every pause. Preview the whole song, especially transitions. If the groove gets smaller, consonants spit or low end pumps, reduce the amount of compression or change the timing.
Do not copy a fixed ratio and attack from a generic mastering chart. The correct timing depends on tempo, transient shape and what the mix bus already did. The useful test is level-matched bypass: does the compressed version hold together better when it is not simply louder?
Volume Maximizer stage
Enable the maximizer only after the compressor decision is stable. Raise level until the first audible trade-off, then back away. A ceiling inside a sample-based limiter is not proof of a safe encoded true peak. After saving a test render, run Statistics and check both true-peak fields. The current Wave Hammer help confirms the compressor-plus-maximizer design; Statistics provides the verification the effect window cannot replace.
Avoid the old “two heavy passes are cleaner than one” claim. Every nonlinear pass changes the signal. If one pass cannot reach the requested level without audible damage, the answer may be a lower target or a mix revision—not another maximizer.
Step 3: Set loudness from the delivery specification
Do not treat −14 LUFS as a universal music-mastering target. Streaming services can normalize playback, but that does not mean every master should be processed to the same number. Genre, dynamics, label/client requirements and the loudest clean result all matter.
For a formal broadcast deliverable, Sound Forge’s Process → Normalize → Loudness mode supports current EBU R128 and ITU-R BS.1770/1771 target controls, including integrated loudness, tolerance, maximum true peak and LRA handling. Use it when the destination actually specifies that standard.
For a music master:
- render or save a test from the processing chain;
- run Statistics on the complete track;
- compare integrated LUFS and true peak with the delivery brief;
- return to Wave Hammer or chain gain if the result is wrong;
- rescan after every level-changing adjustment.
Peak normalization after loudness processing is not a harmless final ritual. It applies constant gain and changes integrated loudness along with peak level. Use it only when you have calculated and accepted that change. The current Normalize help separates Peak, RMS and Loudness modes and documents their different clipping policies.
Step 4: Dither only for a real bit-depth reduction
If the source is 24-bit or 32-bit float and the required final file is 16-bit, choose Process → Bit Depth → Bit-Depth Converter after all EQ, compression, limiting and gain changes. Select 16-bit and audition an appropriate dither/noise-shaping option.
Sound Forge 2026 includes Half Rectangular, Rectangular, Triangular, Highpass Triangular, Gaussian and POW-r choices. Its current help says the best POW-r mode depends mainly on the signal; it does not prescribe Type 2 for all music or Type 3 for “more high-frequency content.” Use the quietest fade and tail to compare noise shaping, then apply it once.
Skip this step when the delivery file remains at the source bit depth or stays 24-bit. Increasing bit depth does not improve existing audio, although a higher working depth can reduce rounding during further processing. The current Bit-Depth Converter documentation explains each dither and noise-shaping mode.
Step 5: Export and run final QA
Create a high-resolution master first, then derive any 16-bit WAV or lossy preview from that approved file. Include the sample rate and bit depth in the filename. Reopen the exported master—not only the open working window—and verify:
- duration and channel count;
- sample rate and bit depth;
- integrated LUFS and LRA;
- maximum true peak and filtered true peak;
- start/end silence, fades and metadata;
- audible clicks, pumping, harshness or codec clipping in derived files.
Compare at matched level with the untouched source and a relevant reference track. The master should make a clear improvement that survives the level match. If the only improvement is loudness, you have not finished the evaluation.
Five-step Sound Forge mastering checklist
- Measure: save the Statistics baseline.
- Balance: use Modern Equalizer and level-matched A/B.
- Control: set Wave Hammer compression, then maximization.
- Deliver: verify LUFS/true peak and dither only for bit-depth reduction.
- QA: reopen the export, rescan and listen against source/reference.
Frequently Asked Questions
What order should I use for mastering in Sound Forge Pro?
Measure first, then Modern Equalizer, Wave Hammer compression/maximization, loudness and true-peak verification, Bit-Depth Converter only when reducing bit depth, and final export QA.
What is Wave Hammer in Sound Forge Pro 2026?
Wave Hammer is a mastering processor with a classic compressor and a Volume Maximizer. Treat compression and final level as separate decisions and verify the saved result with Statistics.
Does a −1 dB limiter ceiling guarantee −1 dBTP?
No. A plug-in ceiling is not automatically an oversampled true-peak guarantee. Save a test and inspect maximum true peak and filtered true peak in Tools → Statistics.
Should I master every streaming track to −14 LUFS?
No. −14 LUFS is not a universal submission requirement. Use the destination brief, the genre’s dynamics and the loudest clean result; expect playback normalization to vary by service and user settings.
Should I peak-normalize after Wave Hammer?
Only if you deliberately need the constant gain change. Peak normalization also changes integrated loudness, so rescan the complete track afterward rather than treating it as an automatic last step.
Which POW-r dither type should I use?
There is no single type for every master. The current Sound Forge help says the best mode depends on the signal. Compare the quietest fade or tail, and dither once only when reducing bit depth.
Is Ozone included with Sound Forge Pro 2026?
Do not assume it is. Some MAGIX-era bundles included Ozone Elements, but the current workflow should rely on the tools listed for your Boris FX edition. A separately licensed Ozone build can be loaded as a compatible VST effect.
Use the full Sound Forge mastering guide when the job includes multiple delivery formats or album consistency. For a single difficult stage, open the focused walkthrough for Modern Equalizer, the Plug-In Chain, or Statistics and LUFS verification.
Last fact-checked: August 2, 2026 against the current Boris FX Sound Forge 2026 Statistics, Modern Equalizer, Wave Hammer, Normalize and Bit-Depth Converter documentation.