Nearly every renaming tool ever made does the same thing: it takes the name a file already has and edits it. Find this, replace it with that, strip these characters, add a number. It is a good idea, it is why those tools exist, and it has one assumption baked into it that is usually false.
What pattern renaming assumes
A rule like take everything before the first dash and call that the artist works beautifully, right up until it meets a file where the artist name itself has a dash in it, or a file with no dash at all, or a file where the order is reversed.
So you add a second rule for that case. Then a third. Each new rule fixes a group of files and quietly damages another group, and because you are running across hundreds of files at once you do not find out which is which.
The effort curve is the wrong shape. The messier the folder, the more rules you need, and the less confident you can be in any of them. The tool gets weaker exactly where you needed it to get stronger.
Why the filename is the worst source of truth
Think about everything that has touched a filename by the time it reaches you.
- The system that created it, using whatever convention it had.
- Whatever exported, converted or compressed it, often adding a suffix.
- Anyone who edited it by hand, including you, at some point you do not remember.
- Cloud services and messaging apps, which append numbers to avoid collisions.
- Zip files, which sometimes flatten a folder structure that was carrying meaning.
Nothing in that chain ever checked whether the name was true. Meanwhile the tags inside an audio file were written by the software that produced or catalogued it, and have mostly been left alone.
The same folder, both ways
| As it arrived | Pattern rename | Built from the file |
|---|---|---|
| 01_track01_final.mp3 | 01 Track01 Final.mp3 | Nightbird - Slow Return.mp3 |
| Nightbird-SlowReturn_128.mp3 | Nightbird SlowReturn 128.mp3 | Nightbird - Slow Return.mp3 |
| Track 04.mp3 | Track 04.mp3 | Ardent - Halfway Home.mp3 |
| audio 1 (2) copy.mp3 | Audio 1 2 Copy.mp3 | Ardent - Halfway Home (Radio Edit).mp3 |
What content renaming can actually read
It depends on the file type, because it depends on what the format stores.
Audio
The richest case. Artist, title, album, track number, version, year, genre, and for DJ libraries the BPM and musical key. Enough to build a complete name without ever looking at the old one.
Photos
Camera body, lens, date and time, and often the location. Good for chronological naming, though the useful part is nearly always the timestamp.
Documents
Author and created date, sometimes a title field that is filled in and sometimes not. Weaker, because the interesting content is the text rather than the metadata.
When a pattern is still the right answer
Being fair to the approach: if your files came out of one system, with one convention, and are wrong in one identical way, a pattern is faster and simpler and you should just use Finder. Content renaming earns its place when the folder has no single convention, which is what happens to any collection that has been added to over years.
Both halves in one pass
For audio this is exactly what RenameBrooo does. It reads and repairs the ID3 tags, then builds the filename out of artist, title, version, BPM and key, so the result does not depend on what the file was called when it arrived. Underscores, dashes and leftover clutter come out, filename and metadata end up agreeing, and every change is shown side by side before it is applied.