To master one finished stereo track in Sound Forge Pro 2026, work through five checkpoints: measure the untouched mix, correct broad tonal balance, control dynamics with Wave Hammer, verify loudness and peaks, then save and reopen the exported file. Keep every comparison level-matched, and if a processor doesn't solve a problem you can hear, remove it.
This page is the short execution workflow. The full Sound Forge mastering guide covers album sequencing, multiple deliverables and wider platform decisions. Here the job is narrower: finish one stereo file without relying on a preset or a universal loudness number.
Quick answer: run Tools → Statistics, make small gain-matched corrections in Modern Equalizer, use the compressor and Volume Maximizer inside Wave Hammer as two separate decisions, rescan the complete file, convert bit depth only when the delivery format requires it, then reopen and check the saved master.
The five-step Sound Forge mastering workflow
- Measure the untouched source. Save the Statistics baseline before processing.
- Balance the spectrum. Use Modern Equalizer only for problems that survive a level-matched bypass check.
- Control dynamics. Set Wave Hammer compression first, then decide how much final level the Volume Maximizer can add cleanly.
- Verify the result. Rescan LUFS, LRA, sample peak and both true-peak fields. Convert bit depth only when reducing the final word length.
- Export and reopen. Inspect and listen to the file that will actually be delivered.
The diagram is a decision map, not a screenshot. The Wave Hammer box contains its two internal processors; the bit-depth branch is conditional rather than a required mastering effect.
Before processing: protect the source and know when to stop
Start from the finished stereo mix at its native sample rate and bit depth, and save a copy before touching the waveform. Sound Forge is well suited to precise stereo-file work, but it can't independently lower a vocal, move a snare or rebalance a bass line once those parts have been mixed together.
Return to the mix when any of these problems is obvious:
- the source already clips or has audible distortion;
- one instrument or vocal needs a level change that affects only that element;
- the stereo bus is already limited so heavily that transients no longer recover;
- a narrow resonance moves with the melody and a static master-bus cut damages other notes;
- the requested loudness needs more limiting than the mix can take cleanly.
A mastering chain should improve a finished mix. It shouldn't stand in for a mix revision that's still possible.
Step 1: Measure the untouched file with Statistics
Select the complete track and choose Tools → Statistics. The current Sound Forge 2026 Statistics help documents the values below. Save them in a note or screenshot so the finished render can be compared with the same source window.
| Readout | What it tells you | How to use it |
|---|---|---|
| Maximum sample value | The highest stored sample | Find sample-level headroom and possible clipping |
| Maximum true peak | An oversampled peak estimate | Check peaks that can appear between stored samples |
| Filtered true peak | The larger filtered or unfiltered true-peak result | Catch readings affected by asymmetry or DC offset |
| Integrated LUFS | Average programme loudness across the complete track | Compare the source, brief and final render |
| Maximum short-term | The loudest three-second integration window | Locate sections that dominate perceived loudness |
| Maximum momentary | The loudest 400 ms window | Inspect brief loud passages without treating them as the whole song |
| LRA | Loudness range across the programme | Track broad dynamic change, not a quality score |
These numbers describe the source; they don't prescribe a target. A quieter track can be healthy, and a louder one can still have useful dynamics. Note what the music is doing before deciding what has to change.
Step 2: Correct broad balance with Modern Equalizer
Load Modern Equalizer in the Plug-In Chain and loop both a dense passage and a quieter passage. The current Modern Equalizer documentation describes an eight-band parametric EQ with high-pass, low-pass, shelf, peaking and band-pass filters, Left/Right/Mid/Side processing, Output Gain, A/B memories, Bypass and oversampling up to 8×.
Make one broad correction at a time: match the processed level with Output Gain, switch Bypass, and listen again. A broad 1 dB move can be consequential on a stereo mix, and there's no reliable recipe that says every master needs a cut at 200 Hz or a boost at 8 kHz.
Use the analyzer to locate energy, then use references and hearing to decide whether that energy is a problem. If the EQ curve becomes a collection of narrow repairs, stop and ask whether the mix or an earlier stem is the better place to work.
Step 3: Treat Wave Hammer as two decisions inside one plug-in
The official Wave Hammer help is explicit: Wave Hammer is one mastering plug-in containing a classic compressor and a Volume Maximizer. They run in sequence, but they solve different problems. Don't represent them as two independent effects in the chain, and don't use the whole plug-in as a one-click loudness preset.
First decision: compressor
Begin with the Volume Maximizer bypassed. Adjust the compressor while listening to the loudest sections, transitions and sustained notes. The goal is controlled movement, not a particular ratio or attack time.
Reduce the processing when the groove becomes smaller, cymbal decay jumps forward, consonants spit or the low end pumps between kicks, then match the bypass level. If the compressed version wins only while it's louder, the comparison hasn't proved an improvement.
Second decision: Volume Maximizer
Enable the Volume Maximizer after the compressor decision is stable. Raise level until the first audible trade-off, then back away. Listen for flattened transients, rough vocal edges, narrowed depth and low-frequency pumping. The clean stopping point depends on the mix and delivery brief, so fixed gain and ceiling settings are poor substitutes for a test render.
A sample-based ceiling inside the effect is not a promise that the encoded or reconstructed signal will return the same dBTP value. Save a short test, run Statistics and inspect both true-peak fields. Two heavy maximizing passes aren't inherently cleaner than one; if one controlled pass can't reach the requested level without damage, revise the target or the mix.
Step 4: Verify loudness and make the bit-depth decision
Render or save a test from the chain, select the complete file and run Statistics again. Compare integrated LUFS, LRA, maximum sample value, maximum true peak and filtered true peak with the baseline and the delivery brief.
Don't treat −14 LUFS as a universal music-master submission target. Playback normalization varies by service and user setting, while genre, dynamics, client requirements and the loudest clean result all affect the master. If a broadcaster or client gives a formal loudness specification, follow that document rather than a generic streaming chart.
For a specified broadcast-style delivery, choose Process → Normalize, then select Loudness in the dialog. The current Normalize help documents EBU R128 and ITU-R BS.1770/1771 modes, integrated loudness, tolerance, maximum true peak and loudness-range handling. Peak normalization is a different operation: it applies constant gain, so it also changes integrated loudness.
Use Bit-Depth Converter only when the word length must fall
If a 24-bit or 32-bit-float source must become a 16-bit deliverable, perform all EQ, compression, maximization and gain changes first. Then choose Process → Bit Depth → Bit-Depth Converter. The Sound Forge 2026 Bit-Depth Converter help lists Half Rectangular, Rectangular, Triangular, Highpass Triangular, Gaussian and POW-r dither options.
Audition the quietest fade or tail and apply dither once. The official help says the best POW-r mode depends mainly on the signal, so there's no defensible type for every track. Skip conversion when the approved delivery remains at the source bit depth; increasing an existing file's bit depth doesn't restore information that was never recorded.
Step 5: Export, reopen and check the deliverable
Create the approved high-resolution master first, then derive a 16-bit WAV or lossy preview when the brief requires one. Use a filename that identifies the version, sample rate and bit depth. Close the working file, reopen the export and check that file from start to finish.
Run Statistics on the reopened master and confirm duration, channel count, sample rate, bit depth, integrated LUFS, LRA, maximum sample value and both true-peak readings. Listen to the first and last seconds, every fade, transitions around edits, the loudest chorus and the quietest tail. Check derived lossy files for clicks, pumping, harshness or codec-related distortion.
Finally, compare the export with the untouched source and a relevant reference at matched perceived level. The master should show a clear improvement once the loudness advantage is removed. If it doesn't, return to the last checkpoint that changed the sound instead of adding another processor.
Stop signs and the next move
| What you hear or measure | Likely checkpoint | Next move |
|---|---|---|
| Low end pumps after loud hits | Wave Hammer compressor or maximizer | Reduce processing and retest the loudest section |
| The louder version loses depth when level-matched | Volume Maximizer | Back away from the first audible trade-off |
| True peak is higher than expected after saving | Render and verification | Adjust the chain, save a new test and rescan |
| The 16-bit fade sounds grainy | Bit-depth conversion | Compare dither on the quiet tail and apply it once |
| A vocal or instrument is still too loud | Source mix | Return to the mix or stem instead of forcing the stereo master |
Five-step checklist
- Measure: save the full-track Statistics baseline.
- Balance: use Modern Equalizer with level-matched A/B checks.
- Control: set Wave Hammer compression, then maximization.
- Verify: rescan loudness and peaks; dither only for a real reduction in bit depth.
- Deliver: reopen the export, inspect it and listen against the untouched source.
Frequently Asked Questions
What order should I use for mastering in Sound Forge Pro?
Measure the complete source first, then correct tonal balance with Modern Equalizer, control dynamics with Wave Hammer, verify loudness and true peak, convert bit depth only when required, and reopen the exported file for final QA.
What is Wave Hammer in Sound Forge Pro 2026?
Wave Hammer is one mastering plug-in with two internal processors: a classic compressor followed by a Volume Maximizer. Set and evaluate those stages as separate decisions, then verify the saved result with Statistics.
Does a −1 dB ceiling guarantee −1 dBTP?
No. A sample-based plug-in ceiling does not guarantee the same reconstructed true-peak reading. 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 music's dynamics and the loudest clean result, and remember that playback normalization varies by service and user setting.
Should I peak-normalize after Wave Hammer?
Only when you deliberately need the resulting constant gain change. Peak normalization changes integrated loudness along with the peak level, so rescan the complete file afterward rather than treating Normalize as an automatic final step.
Which POW-r dither type should I use?
There is no single type for every master. Sound Forge's current help says the best mode depends mainly on the signal. Compare the quietest fade or tail, and apply dither once when the final bit depth is being reduced.
Is Ozone included with Sound Forge Pro 2026?
Do not assume it is. Some older MAGIX-era bundles included Ozone Elements, but it is absent from the current Boris FX product comparison. A separately licensed compatible Ozone build may be loaded as a VST effect.
For a difficult stage, use the focused guides to Modern Equalizer, the Plug-In Chain, normalization or Statistics, LUFS and true-peak verification.
Last fact-checked: September 4, 2026 against the current Boris FX Sound Forge 2026 Statistics, Modern Equalizer, Wave Hammer, Normalize and Bit-Depth Converter documentation.