Automated Audio File Naming with 14-Rule Engine
Rule-based naming for broadcast, streaming, and post-production
Manual file naming doesn't scale for professional workflows. When you're processing hundreds of files for multiple clients and standards, you need automation that handles complex naming logic — not just a prefix.
The Problem with Manual Audio File Naming
- ✗ Files named inconsistently across team members and projects
- ✗ Hours lost to manual renaming after every export session
- ✗ Wrong file delivered to the wrong client or platform
- ✗ No way to tell loudness standard or format from the filename alone
- ✗ Client-specific conventions impossible to enforce across a team
A typical delivery session:
30 source files. Each needs a broadcast master, a streaming version, and a full-resolution archive — all named differently for the client's filing system. That's 90 files, all requiring case-specific naming, loudness suffixes, and format indicators. Doing that manually takes hours and introduces errors.
BatchesBrew's 14-rule naming engine handles all of it automatically, with rules configured once and applied to every file in the batch.
How the 14-Rule Naming Engine Works
- ✓ Per-target customization — Different naming rules for each output target (broadcast, streaming, archive) in the same job
- ✓ Rules execute in sequence — Build up complex filenames from simple, composable steps
- ✓ Loudness insertion — Automatically embed the standard name or LUFS value into the filename
- ✓ Case conversion — Uppercase, lowercase, CamelCase, snake_case, kebab-case per target
- ✓ Format and quality detection — Bit depth, sample rate, and codec inserted from actual output settings
- ✓ Saveable as presets — Configure once, reuse on every job for that client
- ✓ Team sharing (BB Studio) — Naming presets shared with all team members for consistent output
Rule Categories
The 14 rule types span five categories, covering every naming pattern professional workflows require:
Text Manipulation
- Prefix / Suffix
- Find & Replace
- Insert at position
- Remove characters
Case Conversion
- UPPERCASE
- lowercase
- CamelCase
- snake_case
Audio-Specific
- Loudness standard
- LUFS value
- Format (WAV/MP3/M4A)
- Bit depth / Bitrate
Structure
- Separator style
- Sample rate
Before and After: Real Industry Examples
The same source file, named correctly for three different delivery targets — automatically.
Broadcast delivery:
interview_raw.wav→interview_raw_EBU_R128_24bit.wavinterview_raw.wav→INTERVIEW_RAW_ATSC_A85_16BIT.wav
Streaming and podcast:
episode_05_mix.wav→episode_05_mix_Streaming_-14LUFS.mp3episode_05_mix.wav→episode_05_mix_Podcast_-16LUFS.mp3
Post-production archive:
scene_04_sfx.wav→Scene04Sfx_FullScale_32bit_96kHz.wavscene_04_sfx.wav→SCENE_04_SFX_ARCHIVE_FS_96K.wav
Industry Applications
Broadcast
EBU R128 and ATSC A/85 masters clearly labeled with standard and bit depth. Deliver to multiple networks with zero naming confusion.
Post-Production
Dialogue, SFX, music, and stems all named to conform to client templates. Archives include full quality metadata in the filename.
Podcast Networks
Consistent episode naming across dozens of shows. Platform-specific exports automatically named for Spotify, Apple, and YouTube.
Music Production
Streaming masters, CD masters, and vinyl archives all clearly differentiated. Album releases ship with consistent naming across all formats.
Advertising
Campaign-specific templates applied to every variant. 30-second, 60-second, and web cuts all named to agency spec without manual effort.
Streaming Delivery
Platform-specific loudness targets (Spotify -14 LUFS, Apple Music -16 LUFS, YouTube -14 LUFS) with platform name in each filename.
Who Uses This
- Broadcast delivery engineers
- Post-production sound editors
- Podcast production teams
- Mastering engineers
- Audio post supervisors
- Multi-editor creative studios
Free trial available. Plans start at €4.99/month.