The Journalist's Field Recording Workflow: Recorder to Newsroom

Field reporting has a physics problem. Professional recorders — Zoom H5s, Tascams, broadcast kits — write uncompressed WAV by design, because you never get a second chance at the audio and storage is cheaper than regret. But uncompressed audio is enormous: a 48 kHz, 24-bit stereo WAV burns about 17 MB per minute, so an hour-long presser is a 1 GB file. Meanwhile your editor wants the cut five minutes ago, your upload is riding a phone tether from a parking lot, and the newsroom inbox caps attachments at 25 MB. The gap between what the recorder produces and what deadline allows is closed by a three-step pipeline: convert, trim, compress.

Why recorders shoot WAV — and why you should let them

Do not fight the recorder's defaults. WAV is the right capture format: no encoding artifacts, no generation loss when you edit, and total tolerance for the level mistakes that happen when you are recording a scrum with one hand. The MP3 vs WAV FAQ lays out the trade-off, and for capture it lands firmly on WAV. The conversion to MP3 belongs at the filing stage, not the recording stage — file the MP3, archive the WAV.

The deadline pipeline

Step 1: Convert the WAV to MP3

Straight off the SD card, run the file through a WAV to MP3 converter in the browser — no software install, which matters on a borrowed laptop or a locked-down newsroom machine. For spoken material, 128 kbps stereo or 96 kbps mono is broadcast-usable and transparent for editorial review; that one step turns 17 MB per minute into roughly 1 MB per minute. A press conference recorded on a mono shotgun mic gains nothing from stereo, so a stereo to mono pass is often a free halving on top.

Step 2: Trim to the usable tape

An hour of raw recording usually contains a few minutes an editor needs now. Use a trim tool to cut the newsworthy exchange — the question and the answer, with a couple of seconds of handle on each side so the producer has room to work. File the tight cut first; the full recording can follow when you are back on real bandwidth. The trimming FAQ covers the mechanics.

Step 3: Compress to fit the pipe

If the file still will not fit — long-form interviews, multiple cuts, a hotel connection measured in double-digit kilobytes — run it through MP3 compression and target the size you need. Speech survives aggressive compression far better than music: a 64 kbps mono file of a clean interview remains fully intelligible and quotable, and editors would always rather have a slightly crunchy file now than a pristine one after the slot closes. The compression settings FAQ maps bitrate to file size per minute so you can do the arithmetic before uploading.

Field-tested numbers

Rules of thumb worth memorizing, because deadline math happens without a calculator:

• WAV, 48 kHz stereo: about 17 MB per minute (24-bit) or 11 MB per minute (16-bit).
• MP3 at 128 kbps: about 1 MB per minute.
• MP3 at 96 kbps mono: about 0.7 MB per minute.
• MP3 at 64 kbps mono: about 0.5 MB per minute — a 45-minute interview in about 21 MB, under the standard email cap.

Phone recordings in the mix

Plenty of field audio now comes from a phone rather than a dedicated recorder — a scrum captured on Voice Memos, a source who sent their side as a memo. Those arrive as M4A; run them through an M4A to MP3 converter so everything you file arrives in the one format every newsroom system ingests. Filing a mix of M4A, WAV, and MP3 for one story is how clips get lost in the production chain.

Levels: fix them before you file

Field tape has wild level swings — you at arm's length, the subject across a table, a crowd behind both. A quick normalization pass before filing means the producer is not riding the fader through your clip, and quiet answers do not get overlooked in a fast edit. It is a ten-second step that reads as professionalism on the receiving end.

Multiple cuts, one file

When a story needs several pulls from the same recording — three answers from different points in an hour of tape — resist sending three attachments with cryptic names. Trim each pull, then merge them into a single MP3 in story order, and say so in the filing note: "three cuts, merged, timecodes in email." One file is one download for a producer working a bulletin, and nothing gets separated from its context in a busy inbox. The merge tool preserves quality since no re-encode of the speech itself is involved beyond the cut points.

The archive discipline

The MP3 you filed is the deadline artifact; the WAV is the record. When the story ships:

• Keep the original WAV untouched — it is your defense if a quote is challenged, and your source for any future re-edit.
• Keep the filed MP3 alongside it, named identically, so what aired and what was captured stay linked.
• Name by date, story slug, and subject — "2026-03-11 council-vote mayor-scrum.wav" — while you still remember which parking lot it was.

A repeatable kit

The reporters who file fastest are not the ones with the best gear; they are the ones whose pipeline is muscle memory. Recorder writes WAV. Card reader into the laptop. Browser tab: convert, trim to the cut, check the size, compress if the tether demands it, normalize, send. Five minutes from pulling the card to the editor having usable tape — and the same five minutes every time, whether you are filing from a courthouse hallway or a highway shoulder. Build the habit on a slow news day, and it will be there on the day that is not.