Your destination for everything in the adult industry.
ATN — All Things NSFW. Explore. Create. Build.

Check audio loudness before delivery.

An audio delivery check should start with the destination’s actual requirements and end with the exported file. Avoid choosing a loudness target simply because it appears as an editor’s default. Keep the requested measurement, processing choices, and listening review together in one small release record.

1. Collect the real delivery requirements

Find the current specification supplied by the destination or client. Record the requested measurement, target and tolerance if provided, channel arrangement, file format, and any separate peak limit. Keep the source and check date with the project so an old preset does not silently become the requirement.

If there is no published target, record that gap and agree on a delivery choice with the responsible person. Do not invent a universal number for podcasts, videos, or all websites. A tool’s starting value tells you how that tool is configured; it does not tell you what a particular recipient expects.

2. Distinguish the relevant measurements

Audacity’s manual separates Normalize, which can set peak amplitude, from Loudness Normalization, which includes a perceived-loudness target in LUFS. Its documentation notes that required loudness levels vary by application. Keep those controls distinct rather than treating any option named normalize as equivalent.

Use the measurement requested for the task, and record its unit beside the value. A summary that says only “level checked” is difficult to audit later. If the brief includes both loudness and a peak limit, verify both through appropriate tools instead of assuming that meeting one automatically establishes the other.

Sources: [1] [2]

3. Prepare the intended mix before finishing

Confirm that edits, music balance, fades, and intended channel routing are ready for the finishing pass. Listen for abrupt changes, distracting noise, or a missing channel before adjusting overall level. A single processing operation should not be treated as a substitute for reviewing the mix.

Keep an editable copy and identify the portion being processed. Audacity recommends loudness adjustment as a late step before export. If you change the content or mix afterward, repeat the relevant delivery measurements rather than assuming the earlier result still applies to the new version.

Sources: [1]

4. Review channel-related options

Audacity documents a stereo option that either adjusts channels together or normalizes them independently. It also documents a mono-as-dual-mono option that can affect how its loudness result compares with other meters. These are reasons to record the settings instead of blindly accepting a preset.

Preserve an intentional stereo balance unless you have a specific reason to change it. If two tools report different results, first compare the file, channel layout, selection, and measurement settings. Do not keep applying gain changes to chase matching numbers without understanding what each tool is measuring.

Sources: [1]

5. Verify the exported file and release note

Open the exact file intended for delivery and measure it using the agreed method. Listen to its beginning, transitions, and ending, and inspect the complete program when the delivery requires it. Check that the filename and channel arrangement match the brief and that no older export was selected by mistake.

Record the file version, target source, tool and settings, measured result, and remaining question. Keep a listening judgment separate from a measured value and avoid claiming platform acceptance before the recipient confirms it. If a revised mix is exported later, treat it as a new file needing the relevant checks, even when its title is unchanged.

PUT IT INTO PRACTICE

Your quick checklist

  • The destination’s current requirements and units are recorded.
  • Loudness and peak-level checks are distinguished.
  • The intended edit and mix are ready before finishing.
  • Stereo and mono-related settings are understood and recorded.
  • The exact export is measured and reviewed before delivery.

Sources & scope

Audacity’s current development manual supports the limited control and measurement examples; check your installed release for matching controls. The delivery workflow is ATN editorial guidance. No audio is processed or tested, no universal target is prescribed, and no listening or acceptance result is invented.

  1. Audacity Manual: Loudness Normalization (opens in a new tab)Source checked October 9, 2026
  2. Audacity Manual: Normalize (opens in a new tab)Source checked October 9, 2026

Published October 9, 2026. No affiliate links or paid placements in this guide.

ALL THINGS NSFW