# \[X\] Special chars in tags retrieved from Amazon or freedb cause invalid filenames

**URL:** https://community.mp3tag.de/t/x-special-chars-in-tags-retrieved-from-amazon-or-freedb-cause-invalid-filenames/18803
**Category:** No Bugs
**Created:** [March 14, 2017, 6:38pm UTC](https://community.mp3tag.de/t/x-special-chars-in-tags-retrieved-from-amazon-or-freedb-cause-invalid-filenames/18803 "2017-03-14T18:38:32Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![drakanor](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/d/c68b51/32.png) [@drakanor](https://community.mp3tag.de/u/drakanor)
#### Post date: [March 14, 2017, 6:38pm UTC](https://community.mp3tag.de/t/x-special-chars-in-tags-retrieved-from-amazon-or-freedb-cause-invalid-filenames/18803/1 "2017-03-14T18:38:32Z")

</div>

Today I encountered the following issue:

I retrieved tags from Amazon for an album that had a song named something like "first/second.mp3". Since my own filenames for that album weren't right, I executed "rename files from tags". During that process, mp3tag created a subfolder named "first" and inside a file named "second.mp3".

While this is not exactly dangerous, I can't think of a scenario where this would be intended. Also, there may be other special chars coming from external sources containg more undesired chars for file naming. Maybe mp3tag should consider these chars when executing something like renaming from tags.

Greetings from Radebeul,  
drakanor

---

_[View the full topic](https://community.mp3tag.de/t/x-special-chars-in-tags-retrieved-from-amazon-or-freedb-cause-invalid-filenames/18803)._