Intelligent File Naming Based on Loudness Standards
Names derived from actual processing — not guesswork
Keeping track of which files match which loudness standard is a constant source of errors. BatchesBrew solves it by generating filenames directly from the loudness processing applied — so the name is always accurate, no manual labeling required.
The Problem: Tracking Standards Across Hundreds of Files
- ✗ Multiple exports of the same source file — no reliable way to tell which is which by name
- ✗ Manually adding standard names ("_EBU", "_LUFS14") after export — slow and error-prone
- ✗ Wrong file delivered to broadcaster because naming was ambiguous
- ✗ Archive files missing loudness information — impossible to identify years later
- ✗ Separate renaming step after every conversion session doubles the time spent
A real delivery mix-up:
You processed 60 files — EBU R128 masters for the broadcaster, -14 LUFS for streaming, and Full Scale archives. Three folders, similar filenames. You send the wrong folder. The broadcaster's QC catches it 48 hours later. You re-export, re-name, re-deliver. That's a day of your life — and a damaged client relationship — from a naming error.
With BatchesBrew, the loudness standard is embedded in every filename the moment processing completes. There is no separate renaming step. There is no ambiguity.
How Loudness-Based Naming Works
- ✓ Standard inserted automatically — The loudness target applied to the file (EBU R128, -14 LUFS, etc.) is written into the filename during processing
- ✓ LUFS value or standard name — Choose to embed the numeric value (-14LUFS), the standard name (EBU_R128), or both, depending on your workflow
- ✓ Derived from actual processing — The name reflects what was done to the file, not a template that could drift out of sync
- ✓ Per-target customization — Each loudness target in the same batch job gets its own naming convention
- ✓ Combined with other rules — Stack loudness naming with case conversion, format indicators, bit depth, and custom text using the 14-rule engine
- ✓ Saveable as presets — Configure loudness naming once per client or workflow, reuse on every job
All Loudness Standards — All Named Automatically
EBU R128
European broadcast standard. Mandatory for delivery to most European broadcasters. Filename marks the standard clearly for QC.
ATSC A/85
US broadcast standard. Required for American TV network delivery. Differentiated from EBU R128 in the filename to avoid mix-ups.
Streaming (-14 LUFS)
Spotify, YouTube, and most major streaming platforms. Filename embeds platform and loudness target for instant identification.
Podcast (-16 LUFS)
Apple Podcasts recommended standard. Clearly differentiated from streaming versions in the filename.
Spoken Word (-19 LUFS)
Audiobooks, e-learning, and voice content. Quieter standard named explicitly to avoid confusion with podcast exports.
Social Short-form (-10 LUFS)
TikTok, Instagram Reels, and short-form platforms. Louder target named clearly for social media delivery workflows.
Full Scale
Maximum loudness archive masters. FS marker in the filename identifies these as the highest-quality reference files.
Old School (-9 dBFS)
Loud masters for broadcast and vinyl. Peak-limited target named to distinguish from LUFS-normalized outputs.
One Source File — Eight Named Outputs
Every output is processed to a different loudness target and named to reflect exactly what was done.
Broadcast standards:
mix_final.wav→mix_final_EBU_R128_-23LUFS.wavmix_final.wav→mix_final_ATSC_A85_-24LKFS.wav
Streaming and platform delivery:
mix_final.wav→mix_final_Streaming_-14LUFS.mp3mix_final.wav→mix_final_Podcast_-16LUFS.mp3mix_final.wav→mix_final_SpokenWord_-19LUFS.mp3mix_final.wav→mix_final_Social_-10LUFS.mp3
Archive masters:
mix_final.wav→mix_final_FullScale_32bit_96kHz.wavmix_final.wav→mix_final_OldSchool_-9dBFS.wav
How It Works in Practice
Drop in your source audio — WAV, MP3, or M4A. As many files as your plan allows, all processed in one batch.
Choose which standards to output. Configure your naming rules for each target — or load a saved preset for instant setup.
Loudness normalization and file naming happen in the same operation. The processing result determines the name — they cannot get out of sync.
Every file is named to reflect exactly which loudness standard was applied. No ambiguity. No separate renaming step. Ready to deliver.
Workflow Applications
Broadcast delivery
EBU R128 and ATSC A/85 masters clearly differentiated in filename. Broadcasters and their QC systems can verify compliance from the name alone.
Streaming distribution
Multiple platform exports from one source. Each file named with platform and loudness target — Spotify, Apple, YouTube all clearly labeled.
Archive management
Full Scale and peak-limited masters named with their actual loudness characteristics. Retrievable years later without re-measuring.
Multi-standard projects
When a project requires simultaneous delivery to broadcast, streaming, and podcast — every output is named for its exact standard. No folder relabeling required.
Client deliverables
Send clients files they can immediately identify. The loudness standard in the filename confirms spec compliance without them needing to measure.
Team QC workflows
Team members can verify correct standards at a glance from the filename. QC rejections from wrong-standard deliveries become rare.
Free trial available. Plans start at €4.99/month.