Editing vs Mastering vs Proofing: What’s the Difference?
Post-production isn’t one thing — it’s three distinct steps with different goals, skills and budget lines. Learn the difference between editing vs mastering vs proofing in audiobook production, who does each job, and how to estimate costs using practical calculators.
Quick overview — editing vs mastering vs proofing
When someone asks “what’s the difference between editing vs mastering vs proofing?”, they’re usually looking to understand three questions:
- What does each step actually do?
- Who performs the work?
- How should I budget for each line item?
Short answer: Editing assembles and polishes raw takes; mastering balances levels, applies EQ/noise control and ensures platform specs; proofing is the final content check (misreads, wording, pacing) before delivery. Each step requires different tools and experience, and skipping or conflating them risks quality, compliance, or extra revision rounds.
What is editing? — the heart of post-production
Editing is where the recorded session becomes a coherent performance. Editors remove mistakes, select the best takes, stitch clips, fix obvious mouth noises, and prepare the timeline for later stages.
Key editing tasks
- Take selection: choosing the cleanest, most natural performances when multiple takes exist.
- Cutting & comping: combining the best phrases from several takes into a seamless read.
- Noise & click removal (basic): light cleanup like removing pops, lip smacks, or chair creaks.
- Level matching: rough leveling so the audio is consistent between clips.
- Creating chapters & markers: building the export-ready timeline for mastering and proofing.
Editing is typically measured and billed by recorded or edited hours, sometimes by per-finished-hour (PFH) rates. Use the Narration Cost Estimator and the Production Budget Planner to model editor fees alongside narration costs.
What is mastering? — technical polish and spec compliance
Mastering turns an edited timeline into delivery-ready files. This stage focuses on consistency, loudness, EQ, noise floor, and meeting distributor technical specifications (file format, peak/RMS targets, metadata).
Key mastering tasks
- Leveling & gain staging: applying subtle limiting and normalization so chapters play consistently.
- EQ & tone shaping: correcting problematic frequencies and ensuring voice clarity across devices.
- Noise reduction: applying careful reduction to remove hiss without introducing artifacts.
- File formatting & spec checking: exporting chapters with correct sample rate, bit depth, file names, and metadata for platforms like ACX, Audible, or Google Play.
- Silence & spacing: set lead-in/out silence and ensure chapter transitions meet platform rules.
Mastering usually requires an experienced engineer with calibrated monitoring. Pricing is often quoted per finished hour or per project; mastering is where you lose the least money by doing it properly (a poor master forces repeats).
What is proofing? — the quality gate
Proofing (sometimes called QC or quality control) is the content check after editing and before final delivery. A proofing pass catches misreads, skipped lines, consistency errors (names, numbers), repeated phrases and pacing issues that slip through earlier passes.
Proofing activities
- Full listen-through: someone listens to final edits end-to-end to catch content problems.
- Script comparison: comparing audio to the manuscript to find misreads and missed lines.
- Timecode notes: creating a list of timestamps for any fixes (e.g., “12:34 — misread ‘their’/’there’”).
- Final checks: verify chapter markers, file names, metadata, and loudness targets one last time.
Proofing is sometimes handled by a second editor or a dedicated prooflistener; it’s best practice to have a fresh pair of ears for this stage. Budget a small but dedicated block of time for proofing — it often saves money by preventing costly re-masters.
Who does each job?
| Role | Primary focus | Who typically performs it |
|---|---|---|
| Editing | Assemble takes, remove obvious mistakes, comping | Audio editor / producer |
| Mastering | Technical polish, leveling, EQ, spec compliance | Mastering engineer / experienced audio engineer |
| Proofing | Content correctness, misreads, final QC | Prooflistener / editor / QA specialist |
Note: In low-budget projects a single person may perform multiple roles — but each hat requires different skills. Combining roles can save money, but increases the risk of missed issues because the same person is less likely to catch their own mistakes.
How to budget for editing vs mastering vs proofing
Budgeting depends on your production model (freelancer, studio, or DIY). A rough allocation guideline for a typical indie audiobook production (excluding narration fees):
- Editing: 40–55% of post-production budget (most time-consuming)
- Mastering: 20–30% (technical, less time but high expertise)
- Proofing: 10–20% (critical QA step)
Use the Production Budget Planner and Narration Cost Estimator to plug in real numbers and produce a line-item budget. If you pay editors by per-finished-hour (PFH), convert your expected finished hours into cost using your negotiated PFH rates and include allowances for rework.
Common mistakes that blur editing vs mastering vs proofing
- Skipping proofing: leads to misreads escaping to final files and creates costly replacements.
- Asking mastering to fix editorial errors: mastering can’t fix bad takes or content mistakes — it can only improve the audio quality.
- Underestimating editorial time: poor session management and many retakes increase editing hours rapidly.
- Combining inexperienced roles: novice editors who also master often introduce artifacts that require rework.
Practical workflow: sample production pipeline
- Record sessions with high-quality capture, good mic technique and consistent levels.
- Editor pass (editing): comping, removing obvious distractions, basic noise removal.
- Proofing pass: listen for misreads, mark corrections with timecodes.
- Revisions: editor fixes flagged spots and finalizes chapter timelines.
- Mastering pass: final loudness, EQ, noise control and export to platform specs.
- Final QC/proofing: one more full listen-through of mastered files and metadata checks before delivery.
That loop (Edit → Proof → Revise → Master → QC) reduces the chance of rework and ensures the delivered files meet both quality and platform requirements.
Tools and tips for each stage
- Editing: DAWs like Reaper, Pro Tools, or Adobe Audition; iZotope RX for cleanup.
- Mastering: reference meters (LUFS/RMS), high-quality plugins for EQ/limiters, and mastering templates for target specs.
- Proofing: a distraction-free listening environment, good headphones, and a concise timestamped note format to log issues.
Pro tip: keep a master checklist (silence length, chapter names, file names, loudness target) to tick off before delivery — it’s faster than redoing files later.
When you can combine roles (and when not to)
Combining roles can work on low-budget projects or short reads: an experienced editor who masters and proof-reads might be fine for a 2–3 hour short. But for commercial audiobooks, long-form fiction, or projects with heavy sound issues, separate specialists produce better results and reduce revision cycles.
If you must combine: ensure extra time for proofing and consider a paid second-listen by an independent proofreader before final delivery.