Quick answer: for a 16-bit delivery, finish processing and any required sample-rate conversion in a high-resolution master. Commit any live plug-in chain before using Process > Bit Depth > Bit-Depth Converter. Choose 16-bit, apply one planned dither stage, then save a separate PCM file at that same depth. Check the reopened delivery without applying the chain again.
This guide follows Sound Forge Pro 2026 documentation, checked September 14, 2026. It is a documented workflow, not a report of a Windows listening test. The Core Editing guides cover the surrounding file-conversion tasks; this page handles the final precision and dither decision.
Start with Current Precision, Not the Filename
Integer PCM uses a fixed amplitude grid. Processing can calculate values between those grid points. Writing those results back to integer PCM requires quantization, even when both the source and output filenames say 24-bit. An unchanged integer file copied without processing is different: it has no new values to round.
| Current signal | Target file | Decision |
|---|---|---|
| Unchanged 24-bit integer PCM | 24-bit integer PCM | No new quantization; don't add dither by habit |
| Processed floating-point result | 24-bit integer PCM | Consider one final 24-bit dither stage; check the processor and export path |
| 24-bit or higher-precision master | 16-bit integer PCM | Use appropriate dither at final reduction |
| Unprocessed 16-bit source | 24-bit or floating-point working file | More room for later calculations, not recovered source detail |
| Floating-point working master | Floating-point intermediate | No conventional integer-target dither needed for this handoff |
| Approved lossless master | MP3 or AAC | Follow encoder requirements; don't make an unnecessary 16-bit intermediate |
32-bit float is not 32-bit integer. Floating point represents a value with a significand and exponent rather than evenly spaced values across the entire range. Its storage word length is not a direct measure of fixed-point audio resolution. It can retain above-full-scale calculated values in a compatible processing path, but cannot repair clipping already recorded or caused inside a processor. Check the actual output format, not just the number 32. Sound Devices explains the floating-point representation; DPA distinguishes the file's range from analog input clipping.
The iZotope explanation of integer export and floating-point intermediates recommends floating-point files for intermediate bounces and identifies float-to-24-bit export as a dither decision. At 24-bit, ordinary flat triangular dither is generally sufficient; its practical noise level is very low. That is not a reason to add it again to an unchanged 24-bit copy.
What Dither Changes
Rounding or truncating a quiet signal can produce signal-correlated error, heard as distortion in exposed fades or tails. Properly chosen dither adds low-level noise before quantization to control that error. It does not restore discarded source information, reduce existing hiss, or repair clipping.
The Audacity explanation of dither and unprocessed copies describes why simple edits without amplitude processing can preserve integer samples without fresh dither. Its product-specific settings are not Sound Forge controls. Noise shaping is another choice: it redistributes noise across frequency to make it less audible in some conditions, rather than removing the noise.
Convert 24-Bit to 16-Bit in Sound Forge
- Preserve the source. Keep the approved high-resolution master unchanged and work on a separate delivery copy. Retain an FRG project's companion folder with its project file.
- Finish and commit processing. Complete repair, EQ, dynamics, gain and fades. If a live Plug-In Chain is active, write a high-precision working render first with final delivery dither disabled, then reopen that render and bypass the already-applied chain. Use floating point where the chosen format supports it.
- Set the required rate and channels. Perform any sample-rate conversion and channel mixing on the high-resolution copy before final reduction. Confirm the destination's file format, depth, peak limit and loudness requirement.
- Open the converter. Choose Process > Bit Depth > Bit-Depth Converter. Select 16-bit for a 16-bit PCM delivery.
- Choose one dither stage. Select the Dither and Noise shaping settings. Triangular with Noise shaping Off is a straightforward unshaped starting point. Do not also add a separate plug-in dither pass.
- Check and apply. Preview an exposed fade or tail using the processing dialog's preview controls, then click OK. Compare alternatives from the unchanged master, not by repeatedly processing the reduced copy.
- Save a separate delivery. Use File > Save As for an ordinary audio file, or File > Render As for an FRG project. Select the required PCM format and a matching 16-bit template; keep rate and channels unchanged. Use Custom if the format supports it. Do not apply an already-committed chain again.
- Reopen and verify. Check actual format, integer depth, rate, channels, duration, peaks and required loudness. Inspect the beginning, loudest passage, fade and ending without new DSP. If it fails, revise the high-resolution master and make a new delivery.
The 2026 Bit-Depth Converter help documents the conversion menu, dither choices and OK action. Save As/Render As help distinguishes audio files from projects and describes Template and Custom. The project documentation warns that deleting the companion folder breaks the FRG project.
Avoid the Live-Chain Order Trap
The current Plug-In Chain documentation says the live window processes playback and applies effects when the file is saved. Hearing a finished master does not mean the underlying samples already contain that processing. If you dither the underlying waveform and then save through EQ, gain or limiting, dither was not last.
The separate FX Plug-Ins > Apply Plug-In Chain workflow can commit processing to a selection; it is not the same as the live chain window. The guide to the two chain workflows explains their scope. For the converter method above, commit the desired full-file processing first and make sure the final file is not processed twice.
Playback Depth Is Not Delivery Conversion
The converter help separately describes right-clicking the status bar's Bit Depth box to set depth for playback only. That shortcut is not proof that a delivery file has been converted. Use the converter and verify the saved file's properties.
Set Level and Sample Rate Before Dither
Sound Forge's converter help recommends maximizing level before reducing depth. Do not interpret that as an instruction to normalize every master to 0 dBFS. Set the intended loudness and required peak headroom first. If the master already meets the brief, leave its level alone.
Use normalization only when needed, and complete sample-rate conversion before the final integer quantization. Resampling calculates new sample values; merely changing a playback-rate property is not resampling. The required output rate comes from the delivery specification, not from a universal rule to convert everything to 44.1 kHz.
Choose Dither and Noise Shaping Separately
The converter offers Half Rectangular, Rectangular, Triangular, Highpass Triangular, Gaussian and POW-r. The official help describes Half Rectangular as having maximum dither amplitude 0.5 LSB and signal-dependent noise, and Rectangular as using 1 LSB. These are the vendor's amplitude descriptions, not instructions to set a separate level knob.
Triangular is described as avoiding conversion distortion and noise-floor modulation. Highpass Triangular shifts more noise toward higher frequencies. Gaussian is available, but the manual says it can perform less well than the rectangular or triangular choices. Those descriptions do not prove which setting will be least audible on your recording.
Noise shaping Off disables the additional shaping stage; it does not make an already high-pass dither spectrum flat. High-Pass Contour moves noise upward. Equal Loudness Contour distributes it into high and low frequencies. The manual generally favors Highpass Triangular with shaping, but warns against shaping below 44.1 kHz. At lower rates, Triangular with shaping Off avoids that choice. Do not treat Equal Loudness Contour as a documented exception to the warning.
POW-r 1, 2, and 3 Are Different Curves
POW-r exposes three shaping modes. The manual describes #1 as a special dither curve, #2 as additional broad-range shaping, and #3 as stronger optimized shaping. It claims 5–10 dB of dynamic-range extension for #2 and up to 20 dB between 2 and 4 kHz for #3. These are algorithm descriptions, not measured results from this article or additional stored bits.
The largest number is not automatically the best choice. Compare the exposed parts of the actual programme and consider what happens next. For files handed off for further processing, avoid treating strongly shaped 16-bit delivery dither as a default intermediate format.
Keep One High-Resolution Source of Truth
Create delivery variants as separate branches from the master. For an audio-CD version, make the required 44.1 kHz, stereo, 16-bit PCM derivative, with rate and channel conversion before dither. A 16-bit WAV for another destination may require a different rate.
For MP3 or AAC, use the input format accepted by the encoder rather than making a 16-bit file solely to feed it. Apple's Digital Masters workflow, for example, uses a floating-point intermediate for AAC encoding without an additional dither step at that boundary. This does not erase an earlier float-to-integer quantization decision. The file-conversion guide covers containers and templates.
Test Dither Without Fooling Yourself
Make comparison files from the same master with identical level, rate, channels, target depth and sample range. Change one dither or shaping setting at a time. Listen at normal matched level first. If raising monitor gain to inspect a quiet tail, isolate that quiet section and lower the gain before returning to loud material.
A sample-aligned polarity-inverted sum reveals differences, not a quality score. Separate dither renders can contain different noise samples even with identical settings; a nonzero residue alone does not prove a faulty export. Don't normalize the delivery to inspect it. Use a separate test copy if you need amplified analysis.
Recheck peaks and required loudness on the reopened output, since dither and shaping can change peaks. Save-time loudness logging is before codec encoding according to the export help, so it cannot by itself certify a lossy file's decoded peaks. If a delivery fails, fix the master and regenerate it.
Bit Depth and Dither FAQ
Do I need dither when converting 24-bit to 16-bit?
Use appropriate dither as the normal final reduction step. Finish sample-changing processing first and avoid a second independent dither stage during saving.
Should I dither a 24-bit export?
A processed floating-point result written to 24-bit integer PCM is a quantization decision. One final 24-bit dither stage can be appropriate. An unchanged 24-bit integer copy does not need another pass.
Does converting 16-bit audio to 24-bit improve quality?
It cannot recover lost source detail. A higher-precision working format provides room for subsequent processing, not restoration of the original recording.
Which Sound Forge dither setting is best?
No setting wins for every programme. Triangular with Noise shaping Off is an unshaped starting point. The manual generally favors Highpass Triangular with shaping, but warns against shaping below 44.1 kHz.
Can I normalize after dithering?
In a planned workflow, set level before final reduction. If a revision is needed, return to the high-resolution master and regenerate the delivery. If only a reduced file survives, processing remains possible, but it cannot recover the earlier source precision.
Is 32-bit float the same as 32-bit integer?
No. Floating point uses a significand and exponent; integer PCM has a fixed amplitude grid. Check the actual file format and destination support instead of treating the number 32 as a complete specification.