Mastering prepares a finished mix for release by checking translation, continuity, level, spectral balance, dynamics, sequencing where relevant, file format, and metadata. It is a final quality-control and delivery stage, not a substitute for fixing a wrong vocal balance, clipped recording, poor edit, or broken arrangement in the mix. Mastering may use level adjustment, equalization, dynamics, limiting, fades, spacing, sample-rate conversion, bit-depth reduction, and metadata. These processes interact: EQ can change peaks, limiting can change transients and distortion, and conversion choices depend on the production master and recipient requirements.
Who this is for: Independent artists and producers preparing a finished mix for release while preserving an earlier master and avoiding fixed loudness recipes.
- Return source-specific balance, edit, clipping, or arrangement problems to the mix whenever possible.
- Make restrained global changes, compare level-matched references, and label all numeric settings as listening starting points.
- Verify every rendered format and metadata field against the current recipient requirement before release.
Understand the signal and the goal
Mastering prepares a finished mix for release by checking translation, continuity, level, spectral balance, dynamics, sequencing where relevant, file format, and metadata. It is a final quality-control and delivery stage, not a substitute for fixing a wrong vocal balance, clipped recording, poor edit, or broken arrangement in the mix.
Mastering may use level adjustment, equalization, dynamics, limiting, fades, spacing, sample-rate conversion, bit-depth reduction, and metadata. These processes interact: EQ can change peaks, limiting can change transients and distortion, and conversion choices depend on the production master and recipient requirements.
Prepare a controlled session
Export the mix without clipping or accidental master processing, include complete tails, and provide notes about sample rate, bit depth, intended release, references, and concerns. Work in a calibrated or at least repeatable monitoring setup, lower the listening level periodically, and keep the original mix plus every master revision.
Listen from beginning to end before processing, write translation and defect notes, and return mix problems to the mix when possible. Make one restrained global change at a time, compare at similar perceived level, check several sections, and render revisions rather than relying only on live plug-in playback.
Make and judge the change
Assess vocal or lead focus, low-end stability, harshness, noise, clicks, fades, stereo and mono behavior, transient integrity, distortion, pumping, section dynamics, and reference relationship. Use loudness and peak meters for delivery evidence, not as a replacement for listening or a mandate to match another track's number.
Treat every EQ point, compression ratio, attack, release, limiter ceiling, and output value as a starting point to adjust by listening and metering. No fixed mastering chain, streaming target, or loudness outcome fits every release. Stop when another change weakens translation or musical intent.
Check, document, and deliver
Create files from the approved production master according to current distributor or manufacturer specifications, then reopen each export and verify format, channels, duration, start, end, metadata, loudness, and peak behavior. Archive the unmastered mix, production master, distribution copies, notes, and checksums or transfer confirmation.
Mastering cannot recover clipped transients, isolated stems, or detail masked inside a stereo mix. Home monitoring may conceal low-frequency or stereo problems. Streaming normalization policies can change and do not guarantee playback level, so mastering should not promise a fixed loudness advantage or platform outcome.
Worked example: master a release track
An artist submits a stereo mix whose chorus vocal is slightly buried and asks mastering to make the release competitively loud.
- Listen through the unprocessed mix, confirm that the vocal issue is localized to the chorus, and request a mix revision instead of using broad mastering EQ to affect every source.
- After receiving the revision, compare it at matched level, inspect peaks and noise, and make only global changes that improve the whole track across several sections.
- Test limiting conservatively by listening for transient loss, distortion, pumping, and changed section contrast rather than chasing a promised loudness outcome.
- Render the distributor's current required formats, reopen and measure them, verify metadata and tails, and archive the mix and production master separately.
Mastering quality-control sheet
Use this record to repeat and review mastering a track for release without losing the source, context, or reason for each choice.
- Artist, track, mix version, format, sample rate, bit depth, tails, references, concerns, and approval owner.
- Full-listen notes, mix-return issues, clicks, noise, balance, low end, harshness, dynamics, stereo, and mono.
- Processing purpose, EQ, dynamics, limiter, fades, output, starting-point label, bypass method, and side effects.
- Current recipient specification, conversion, dither where applicable, channels, loudness method, peak rule, and metadata.
- Reopened export, duration, beginning, ending, measurement, codec check, checksum or transfer, versions, and archive.
Common mistakes
- Using broad mastering processing to repair one buried source that should be changed in the mix.
- Applying a fixed EQ frequency, compression ratio, limiter ceiling, or streaming loudness target to every release.
- Sending a file based on live session playback without reopening the render and checking format, metadata, peaks, and tails.
Try one
A master becomes louder but loses drum attack and makes the chorus feel smaller than the verse. What should happen next?
Reduce or remove the limiting and compare at similar perceived level. Inspect whether the chorus already needs a mix or arrangement revision, then check transients, distortion, pumping, and section contrast across the song. Do not defend the setting because it reaches a number. The accepted master should preserve musical hierarchy and meet the current delivery specification by listening and metering.
Sources
- Ableton audio fact sheetOfficial Ableton explanation of digital-audio handling, sample-rate conversion, bit depth, and export behavior.
- Audacity Export Audio guideOfficial Audacity guidance for file formats, export ranges, audio options, metadata, and mixing on export.
- Audacity loudness normalization guideOfficial Audacity documentation for measured loudness normalization and its controls.