# Hidden and conflicting tags in MP3 files

**URL:** https://community.mp3tag.de/t/hidden-and-conflicting-tags-in-mp3-files/49818
**Category:** Support
**Created:** [August 3, 2020, 8:48pm UTC](https://community.mp3tag.de/t/hidden-and-conflicting-tags-in-mp3-files/49818 "2020-08-03T20:48:49Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Brothbeard](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/f1d935/32.png) [@Brothbeard](https://community.mp3tag.de/u/Brothbeard)
#### Post date: [August 3, 2020, 8:48pm UTC](https://community.mp3tag.de/t/hidden-and-conflicting-tags-in-mp3-files/49818/1 "2020-08-03T20:48:49Z")

</div>

I've recently changed the media player I use from Windows Media Player to MediaMonkey. The transition mostly went well but I have had some nagging tag issues with a few MP3 files. I use MP3Tag as my tag editor but these few files, which looked perfect in MP3Tag were being incorrectly identified by MediaMonkey which showed alternative tag values to those displayed in MP3Tag.

I have have concluded that there must be two sets of embedded tags - is that possible? I note that MP3Tag identifies most of my MP3 files as having both ID3V1 and ID3V2.3 variants embedded. Does this explain the mystery - until now I assumed one was just an extension of the other and that the values of both would be the same.

To help resolve my challenges, does anyone know of a utility that shows both sets of values?

Of course, if I'm off beam here about the cause of my problems, could someone explain what is actually happening and how to deal with it.

BTW - I've had no issues with my FLAC files.

Many thanks for your help.

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [August 4, 2020, 12:33pm UTC](https://community.mp3tag.de/t/hidden-and-conflicting-tags-in-mp3-files/49818/2 "2020-08-04T12:33:00Z")

</div>

> [@Brothbeard](#):
>
> I have have concluded that there must be two sets of embedded tags - is that possible? I note that MP3Tag identifies most of my MP3 files as having both ID3V1 and ID3V2.3 variants embedded. Does this explain the mystery - until now I assumed one was just an extension of the other and that the values of both would be the same.

Mp3Tag reads the tags in the order Ape-\>ID3v2-\>ID3v1.  
So this might be a possible reason if your tags are not in sync.

Have a look at File-\>Options-\>Tags-\>MPEG for your settings in Read and Write.  
If you have different content in ID3v2 and ID3v1 you can observe that in enabling and disabling the read-option. I.e. to see **only** ID3v1-tags just have only this enabled.  
Normally Mp3Tag puts ID3v1 and ID3v2 in sync if both are enabled to read and to write and you save the file again.

But there be other reasons. The file can be corrupted, which does not always mean that you cannot play the file or all software shows a problem.  
Check your files for errors:

> [@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 …

---

<div class="post-metadata">

### Author: ![Brothbeard](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/f1d935/32.png) [@Brothbeard](https://community.mp3tag.de/u/Brothbeard)
#### Post date: [August 4, 2020, 5:22pm UTC](https://community.mp3tag.de/t/hidden-and-conflicting-tags-in-mp3-files/49818/3 "2020-08-04T17:22:28Z")

</div>

Thank you, poster. With your help I have discovered a whole new world of tag detail I didn't know existed and more importantly a mechanism for sorting out the problem. The MP3 files that caused the issue were not created by me and the originator clearly used different software. Still playing about but I now have the knowledge to resolve everything.

---

<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: [February 9, 2026, 12:28pm UTC](https://community.mp3tag.de/t/hidden-and-conflicting-tags-in-mp3-files/49818/4 "2026-02-09T12:28:45Z")

</div>


