# Moving from MP3/Tag Studio to mp3tag - rename files

**URL:** https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763
**Category:** Support
**Created:** [February 13, 2024, 7:04pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763 "2024-02-13T19:04:55Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![CNA](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/ccd318/32.png) [@CNA](https://community.mp3tag.de/u/CNA)
#### Post date: [February 13, 2024, 7:04pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/1 "2024-02-13T19:04:55Z")

</div>

I am a longtime user of Mp3/Tag Studio, but as it has had no support for years I am having more and more problems on Windows 10. So-- I'm hoping that this program will let me do the things I'm used to without too much confusion. I hope this is the place to ask (probably dumb) questions. I'll start with one. NB, I may well use the wrong terms for the actions, as I have only made one pass through the documentation.

If I have filenames with a number followed by a period and wish to delete the period I used expected/output patterns `<Custom1>. <Custom2>.mp3` and `<Custom1> <Custom2>.mp3`. I saw a mention in the document about "place holders", but there was no description or example that I could find. How would I perform this in mp3tag? (I do know that the delimiters would be percent signs, but I didn't want to write a madeup name between them.)

I'll get to harder example later!

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [February 13, 2024, 7:11pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/2 "2024-02-13T19:11:06Z")

</div>

As MP3tag is a tagging program, the filenames are not the primary target.  
In fact, the best way would be to get the tag fields filled first and then rename a file with the data from the tag fields.  
To get a general impression of MP3tag, see

> **[Overview – Mp3tag Documentation](https://docs.mp3tag.de/getting-started/overview/)**
>
> General description about Mp3tag, the design philosophy and the intention of this documentation. Mp3tag is the universal Tag Editor.

and then perhaps:

> **[First Steps – Mp3tag Documentation](https://docs.mp3tag.de/getting-started/first-steps/)**
>
> A collection of tasks with step-by-step instructions intended for novice users of Mp3tag. Mp3tag is the universal Tag Editor.

---

<div class="post-metadata">

### Author: ![CNA](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/ccd318/32.png) [@CNA](https://community.mp3tag.de/u/CNA)
#### Post date: [February 13, 2024, 7:35pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/3 "2024-02-13T19:35:05Z")

</div>

I am actually asking about this page:

> **[Rearrange Parts of File Names – Mp3tag Documentation](https://docs.mp3tag.de/converters/rearrange-filenames/)**
>
> Documentation on Filename to Filename, a converter to rearrange parts of file names. Mp3tag is the universal Tag Editor.

I note that there is, indeed, an example of a place holder, but I did not realize it, as it seems to differ in syntax from other items. I assumed, from the rest of the document, that the "variables" in the pattern used the % character as both opening and closing delimiters. So would I be correct using patterns like:  
%1. %2 as expected name and %1 %2 as output name?

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [February 13, 2024, 7:37pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/4 "2024-02-13T19:37:24Z")

</div>

> [@CNA](#):
>
> So would I be correct using patterns like:  
> %1. %2 as expected name and %1 %2 as output name?

Yes. Probably.  
The function has a preview.

---

<div class="post-metadata">

### Author: ![CNA](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/ccd318/32.png) [@CNA](https://community.mp3tag.de/u/CNA)
#### Post date: [February 13, 2024, 7:40pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/5 "2024-02-13T19:40:08Z")

</div>

Thank you. Is there a full description of the pattern syntax? I might have missed it, but I did cover most of the documentation.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [February 13, 2024, 7:44pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/6 "2024-02-13T19:44:40Z")

</div>

Which pattern do you mean?  
The one to fiddle with the filename only?  
That consists only of the %1..%n part.  
All the other bits are described in format strings, mappings, scripting, actions.

---

<div class="post-metadata">

### Author: ![CNA](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/ccd318/32.png) [@CNA](https://community.mp3tag.de/u/CNA)
#### Post date: [February 13, 2024, 7:47pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/7 "2024-02-13T19:47:31Z")

</div>

Okay. I need to wrap my head around the differences between the two programs. Having used the old one for 15 or 20 years it will take a bit to get my fingers to type the differences.

I'm sure I'll be back.

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [March 14, 2024, 7:48pm UTC](https://community.mp3tag.de/t/moving-from-mp3-tag-studio-to-mp3tag-rename-files/63763/8 "2024-03-14T19:48:12Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
