# Unreadable ID3v2 tags **URL:** \ **Category:** General Discussion\ **Created:** [November 12, 2026, 6:36pm UTC](https://community.mp3tag.de/t/unreadable-id3v2-tags/72066 "2026-11-12T18:36:45Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 12, 2026, 6:36pm UTC](https://community.mp3tag.de/t/unreadable-id3v2-tags/72066/1 "2026-11-12T18:36:45Z")
Yesterday I found a few old CD-Rs in my archive with _very_ old MP3s. Last modified in 2003 😁 - I don't even remember which program I used back then. Definitely pre-iTunes … maybe Winamp? Did Winamp have an option to edit tags? 🤔 Anyway, I loaded them into Mp3tag, and to my surprise it refused to read the ID3v2.3 tag of about 80% of the files. ![image](https://community.mp3tag.de/uploads/default/original/3X/f/c/fcd4d87f7f2f4f6c33980f6f1fc039c775fd5bcf.png) I double-checked with a few other programs (MusicBrainz Picard, AudioGuru, ExifTool), and none of them complained. ![image](https://community.mp3tag.de/uploads/default/original/3X/9/3/93fcb989970d3a92e6a3aa2b16b338fcbf3a711f.png) I'm not saying that this is a bug in Mp3tag, it might well be that the tags are broken. I'm just curious what Mp3tag does not like about them that doesn't seem to bother the others. If anyone wants to have a look, I've uploaded the smallest of those files: [id3v2\_testfile\_bad.mp3](https://www.dropbox.com/scl/fi/me0uoz08jlnyfvbo0l2yg/id3v2_testfile_bad.mp3?rlkey=5hro0tx5lekfomxp76u4p9q8c&st=n6kcsrq8&e=1&dl=0) (ignore the login prompt, just click "download only"). ---
**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:** [November 12, 2026, 6:46pm UTC](https://community.mp3tag.de/t/unreadable-id3v2-tags/72066/2 "2026-11-12T18:46:05Z")
The supplied file shows these problems in MP3diags: ![grafik](https://community.mp3tag.de/uploads/default/original/3X/f/a/fadb4f2c83889605a05b6cade56d5dd0ead991c6.png) The most important one: Invalid ID3V2.3.0 frame. Incorrect frame size or file too short. MP3diags also so says that the ID3V1 seems to be OK. So perhaps you can salvage some of the data if you cut and paste the whole tag. ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [November 12, 2026, 6:53pm UTC](https://community.mp3tag.de/t/unreadable-id3v2-tags/72066/3 "2026-11-12T18:53:23Z")
All of what @ohrenkino said. In addition and specific to Mp3tag, I'm stopping at a "frame" with ID `MP3e` (invalid frame ID, prefix of repeated garbage data `MP3ext V3.3.17(ansi)` in the ID3v2 tag structure. ---
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 12, 2026, 7:20pm UTC](https://community.mp3tag.de/t/unreadable-id3v2-tags/72066/4 "2026-11-12T19:20:10Z")
Aaaaahh ... 💡 "MP3ext" rings a bell ... it was a shell extension to access the tags directly from Windows Explorer. So that's the culprit. No longer needed, since this is now a built-in function. The repeated garbage was probably an attempt to write some padding, so that the tag could be extended later without rewriting the whole file. Those CDs are mostly ancient backups of files that are still in my audio library and have long been tagged properly, there's no need to salvage them. But cut & paste indeed seems to fix it. Case closed, thanks for looking into it! ---
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 13, 2026, 1:58pm UTC](https://community.mp3tag.de/t/unreadable-id3v2-tags/72066/5 "2026-11-13T13:58:32Z")
PS, for the records: Overwriting the "MP3ext …" garbage with null bytes, as the standard requires – _"The value of the padding bytes must be $00"_ – made the file readable for Mp3tag, too.