Guide

Recording and editing a sound library without burning weeks

Updated July 26, 2026

The slow part of making a sound pack is almost never the recording. It's the sixty individual files you then have to touch one at a time. This is the workflow we actually use, ordered by how much time each step saves.

1. Spec the pack before you record anything

Decide the categories and the target count per category first, and write it down. A spec sheet with name, category, target length, whether it's recorded, synthesised or hybrid, and how many variations you need per sound.

This sounds like bureaucracy and is actually the thing that stops a pack sprawling. An open-ended "record some footsteps" session produces material you then have to sort, cut and count. A session against a spec produces a pack.

2. Record 8–10 takes, keep 3–5

Buyers want variation — repeated identical sounds are what make game audio feel cheap, and runtime pitch-shifting only papers over so much. So capture generously.

The important half of that rule is the second half: selection beats refinement. If a take is weak, cut it. Do not spend twenty minutes rescuing something you have eight alternatives to. That instinct — polishing rather than discarding — is the single biggest time sink in the middle of a library project.