# Misleading tag abstraction causes release of incorrect metadata

**URL:** https://community.mp3tag.de/t/misleading-tag-abstraction-causes-release-of-incorrect-metadata/70629
**Category:** Support
**Created:** [February 3, 2026, 11:30am UTC](https://community.mp3tag.de/t/misleading-tag-abstraction-causes-release-of-incorrect-metadata/70629 "2026-02-03T11:30:00Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### 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: [February 3, 2026, 12:09pm UTC](https://community.mp3tag.de/t/misleading-tag-abstraction-causes-release-of-incorrect-metadata/70629/5 "2026-02-03T12:09:45Z")

</div>

> [@KetadataServices](#):
>
> In this case, the only reliable solution was to strip Lyrics3v2 entirely using external tooling, because MP3tag does not currently provide a way to surface or columnise it.

Existence of Lyrics3v2 tags is denoted in the aforementioned "Tag" column in Mp3tag's File List.

If you configure Mp3tag to remove all tag formats (incl. ID3v1), it will also remove Lyrics3v2, as it can only exist with an ID3v1 tag present.

---

_[View the full topic](https://community.mp3tag.de/t/misleading-tag-abstraction-causes-release-of-incorrect-metadata/70629)._