Rename Hundreds of Audio Files Correctly in Minutes
Built for Broadcast Professionals
TV networks and broadcasters have strict loudness requirements. EBU R128 in Europe, ATSC A/85 in the US. Miss the spec and your content gets rejected — or worse, auto-limited into distortion.
The Problem With Manual Audio File Naming
- ✗ Rejected deliveries due to loudness non-compliance
- ✗ Hours spent manually renaming files for each broadcast standard
- ✗ Confusion over which file is which after normalization
A typical broadcast delivery:
You've mixed 40 audio stems for a documentary series. The broadcaster needs EBU R128 masters, the streaming platform wants -14 LUFS, and the archive requires Full Scale WAVs. That's 120 files to normalize, rename, and organize correctly.
Common Broadcast Loudness Standards
- EBU R128 (-23 LUFS)
- ATSC A/85 (-24 LKFS)
- OP-59 (Australia)
Complex Broadcast Naming Requirements
Beyond simple prefixes and suffixes, broadcast delivery often requires complex naming logic: case conversion, loudness insertion, format detection, and client-specific templates. BatchesBrew's 14-rule naming engine handles these automatically with per-target customization.
Example transformations:
news_segment.wav→news_segment_EBU_R128_24bit.wavnews_segment.wav→NEWS_SEGMENT_ATSC_A85_16BIT.wavdocumentary_ep01.wav→DocumentaryEp01_BBC_16bit.wav
How Automated Naming Improves Delivery Accuracy
- ✓ Batch processing — Normalize hundreds of files at once
- ✓ 14-rule naming engine — Complex naming logic handles case conversion, loudness insertion, format detection, and client-specific templates automatically
- ✓ Multiple standards — Output to different targets simultaneously
- ✓ Multiple formats — WAV, MP3, M4A/AAC with quality settings
Who Uses This
- Freelance audio engineers
- Post-production studios
- Podcast producers
- Music mastering engineers
- Broadcast delivery teams
Free trial available. Plans start at €4.99/month.