# \[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:** 2

<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: [March 14, 2017, 9:08pm UTC](https://community.mp3tag.de/t/x-special-chars-in-tags-retrieved-from-amazon-or-freedb-cause-invalid-filenames/18803/2 "2017-03-14T21:08:08Z")

</div>

The / is a valid character in Windows.  
If you are not sure whether your filenames will end up with valid characters, use the $validate() function for the whole filename.  
If you have more special characters that you want to replace with a special (other) character, uste the $replace() function for that piece of data.

Also see the FAQs on the Convert function and the possibility to create folder structures:  
[/t/8016/1](https://community.mp3tag.de/t/8016/1)

I would say: no bug.

---

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