# MP3TAG messing up with MP3 comments tag when editing

**URL:** https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125
**Category:** Support
**Created:** [April 24, 2022, 10:08pm UTC](https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125 "2022-04-24T22:08:19Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)
#### Post date: [April 25, 2022, 4:16pm UTC](https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125/4 "2022-04-25T16:16:43Z")

</div>

There was an entire thread on issues with comments not too long ago.

> [@Windows Explorer and Mp3tag Comment field disagree](https://community.mp3tag.de/t/windows-explorer-and-mp3tag-comment-field-disagree/56826):
>
> Windows Explorer show a random string of characters in the Comment field for some mp3 files (ID3v2.3 UTF-16 format). Mp3tag shows its Comment field as blank for those same files. Told Mp3tag to blank the Comment field, then Save the files. The Comment field display didn't change in Explorer. Ran MP3-Diags.exe tool on those same files. It shows those files as having more than one "COMM size=" field in its ID3v2 Xing header. That seems to cause a string of characters from somewhere in the mp…

When looking at the extended tag details, you will likely see in your files that there are multiple COMMENT fields being used. Have a look through this thread, and your files that are showing this issue.

---

_[View the full topic](https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125)._