# Tag to filename allow overwrite?

**URL:** https://community.mp3tag.de/t/tag-to-filename-allow-overwrite/71018
**Category:** Support
**Created:** [April 7, 2026, 11:50pm UTC](https://community.mp3tag.de/t/tag-to-filename-allow-overwrite/71018 "2026-04-07T23:50:14Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![JohnIV](https://community.mp3tag.de/user_avatar/community.mp3tag.de/johniv/32/5647_2.png) [@JohnIV](https://community.mp3tag.de/u/JohnIV)
#### Post date: [April 7, 2026, 11:50pm UTC](https://community.mp3tag.de/t/tag-to-filename-allow-overwrite/71018/1 "2026-04-07T23:50:14Z")

</div>

Hello, I’m doing a curated cleanup of my 560K song collection and would like to use the app to do some of the moving. Is there a way to disable the ‘can’t overwrite existing files exist’ message and allow the destructive move? I think MP3Tag’s move is quicker than the alternative of tag / file to a secondary location and then fileman moving them over the top of the original. Thanks!

---

<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: [April 8, 2026, 5:34am UTC](https://community.mp3tag.de/t/tag-to-filename-allow-overwrite/71018/2 "2026-04-08T05:34:45Z")

</div>

I think that this happens only if the new name would lead to overwriting a different already existing file. After that process you would have 1 file less. Is that intended?  
I would investigate why there is another file with that name.  
Perhaps the tag data does not differentiate enough?  
Is it really a duplicate?

---

<div class="post-metadata">

### Author: ![JohnIV](https://community.mp3tag.de/user_avatar/community.mp3tag.de/johniv/32/5647_2.png) [@JohnIV](https://community.mp3tag.de/u/JohnIV)
#### Post date: [April 8, 2026, 1:25pm UTC](https://community.mp3tag.de/t/tag-to-filename-allow-overwrite/71018/3 "2026-04-08T13:25:51Z")

</div>

I had some damaged ASF in my destination directories copies. I transcoded all the damaged wma files into the new different source directory where they were _fixed_. I wanted MP3Tag to read the new source and then tag → filename move them into the destination over the top of the bad ones (identically named, just repaired now), so I sought an override for the naming warning (I wished a destructive copy). The reason vs. just drag and drop from source to destination was taking too long for the amount of files I’m dealing w/. Appreciate the reply, I ended up building a Powershell script that initiated the transfer over the top a lot quicker. It would be interesting if there is a way in MP3Tag to do this procedure.

---

<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: [April 15, 2026, 1:26pm UTC](https://community.mp3tag.de/t/tag-to-filename-allow-overwrite/71018/4 "2026-04-15T13:26:04Z")

</div>

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