WAV audio export — Delivery workflow

Worked example

Hand over a WAV with its sample rate and channel count written in the name, and plan the transfer, because uncompressed audio is large.

The tool names the download after the source plus the mode, such as session-wav.wav. A name that carries the specification saves the recipient a properties check: session_48k_stereo_v2.wav. A sound editor who receives twelve stems from you wants to know at a glance that all of them share one rate.

Plan the size. One minute of 48 kHz stereo is 11.52 MB, so a 20-minute dialogue stem is 230 MB, which is over what most email services will carry, and a shared folder or a file-transfer link is the sensible route. Zipping a WAV saves little, since PCM audio compresses only modestly, and this tool does not produce FLAC.

The typical mistake is sending WAV when a listening copy would do. A client who only wants to approve a rough cut does not need 635 MB per hour; send an MP3 at 128 or 192 kbps for review and keep the WAV for the final hand-off to the editor or the mastering engineer. Say in the message which file is which.

For repeatable delivery, use the same sample rate and channels for the whole project, note them once in a shared document, and open one finished file in the target application before sending the rest. Confirm the recipient has enough free space before a large transfer starts.

60 s × 44100 Hz × 2 channels × 16 bit

10,584,000 PCM bytes before container overhead

Keep the WAV files until the project is approved, since regenerating them from a lossy copy cannot restore quality.