# Issue album art image and ID3v2.4 UTF-8 **URL:** https://community.mp3tag.de/t/issue-album-art-image-and-id3v2-4-utf-8/17006 **Category:** Off-Topic **Created:** [June 29, 2015, 6:56pm UTC](https://community.mp3tag.de/t/issue-album-art-image-and-id3v2-4-utf-8/17006 "2015-06-29T18:56:01Z") **Posts on this page:** 1 **Showing post:** 2
### 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: [June 30, 2015, 3:16am UTC](https://community.mp3tag.de/t/issue-album-art-image-and-id3v2-4-utf-8/17006/2 "2015-06-30T03:16:52Z")
I am not sure if you got it right: UTF-16 is written for the V2.3 standard. UTF-8 is written for the V2.4 standard. There is not UTF-16 for V2.4. And as these 2 standards represent a different approach to writing the tags. The WIndows Explorer, e.g., does not read V2.4 tags alltogether. So it could be that your mobile cannot cope with V2.4 tags... I would return to V2.3 tags. There is also a thread in the FAQs on strange displays: [/t/2785/1](https://community.mp3tag.de/t/2785/1) The solution to use iTunes for tagging is weird as iTunes very often does not really tag files but writes data only into its database. I wouldn't do it. Edit: to make sure that your files are ok you should use mp3val and mp3diags to check their integrity - to find out that the hicups do have their origin in some corruption. --- _[View the full topic](https://community.mp3tag.de/t/issue-album-art-image-and-id3v2-4-utf-8/17006)._