# "!BAD ID3v2" - how to restore the tag information?

**URL:** https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600
**Category:** Support
**Created:** [March 5, 2022, 3:36pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600 "2022-03-05T15:36:58Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![mediacity](https://community.mp3tag.de/user_avatar/community.mp3tag.de/mediacity/32/11231_2.png) [@mediacity](https://community.mp3tag.de/u/mediacity)
#### Post date: [March 5, 2022, 3:36pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/1 "2022-03-05T15:36:59Z")

</div>

I have about two thousand files with bad tags. When I look at these files in MP3Tag, the tag field for these files says "!BAD ID3v2". When I look at these files in musicbrainz, and I change the comment field, all of the “missing” mp3 data magically reappears. When I do this in MP3Tag, however, nothing happens. How can I fix these tags in MP3Tag?

---

<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 5, 2022, 3:45pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/2 "2022-03-05T15:45:36Z")

</div>

See here for more hints on how to get files back from the state of bad tags:

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

But depending on the extent of the damage, it could be that the info is lost.  
You could experiment a little and see if V1 tags are still readable. See File\>Options\>Tags\>Mpeg and set ony V1 to read, all other off

---

<div class="post-metadata">

### Author: ![mediacity](https://community.mp3tag.de/user_avatar/community.mp3tag.de/mediacity/32/11231_2.png) [@mediacity](https://community.mp3tag.de/u/mediacity)
#### Post date: [March 5, 2022, 4:01pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/3 "2022-03-05T16:01:27Z")

</div>

Thanks for taking the time to reply. I downloaded MP3diags, but the program, according to itself, was last updated in 1991, that is, 31 years ago. I'm amazed it still executes. I don't want to use this as it has not been updated in so long. It even looks ancient.

Also, the info isn't lost (as I stated in the original post), it is retrievable using musicbrainz. I wanted to know if the info was retrievable using MP3Tag.

---

<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 5, 2022, 4:08pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/4 "2022-03-05T16:08:10Z")

</div>

> [@mediacity](#):
>
> if the info was retrievable using MP3Tag

If MP3tag considers the tag to be bad, then that's it as far as MP3tag is concerned.  
I wonder what MP3tag and the other programs say about the tags that have been rewritten with Musicbrainz ...

> [@mediacity](#):
>
> that is, 31 years ago

Well, the MP3 format also has not changed for a long time.

---

<div class="post-metadata">

### Author: ![sveakul](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sveakul](https://community.mp3tag.de/u/sveakul)
#### Post date: [March 6, 2022, 9:12pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/5 "2022-03-06T21:12:58Z")

</div>

Not sure where you got "1991", but the last release version was actually from 2016-07-29 ([https://sourceforge.net/projects/mp3diags/files/](https://sourceforge.net/projects/mp3diags/files/) . You might also try MP3val which though older (2009) is simpler to use and has worked well for me ([https://sourceforge.net/projects/mp3val/files/mp3val-bundle/](https://sourceforge.net/projects/mp3val/files/mp3val-bundle/) .

---

<div class="post-metadata">

### Author: ![UserWithName](https://community.mp3tag.de/user_avatar/community.mp3tag.de/userwithname/32/22243_2.png) [@UserWithName](https://community.mp3tag.de/u/UserWithName)
#### Post date: [May 13, 2024, 8:28pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/6 "2024-05-13T20:28:12Z")

</div>

Found this be chance, even it did not help me out. I just want to place a hint.

I use `exiftool -G9` to investigate my files and I got all tags but also "Invalid ID3 frame size". That seemed to be a problem due to invalid id3v2.4 tags.

I solved this by using ffmpeg to copy audio codec and enforce 2.3 on writing:

```auto
ffmpeg -loglevel error -i in_with_24.mp3 -c:a copy -vn -id3v2_version 3 out_with_23.mp3

```

After this exiftool and mp3tag are both fine.

---

<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: [August 13, 2024, 12:41pm UTC](https://community.mp3tag.de/t/bad-id3v2-how-to-restore-the-tag-information/56600/7 "2024-08-13T12:41:27Z")

</div>

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