# Mp3tag v3.33.1 released

**URL:** https://community.mp3tag.de/t/mp3tag-v3-33-1-released/70542
**Category:** Announcements
**Created:** [January 22, 2026, 9:05am UTC](https://community.mp3tag.de/t/mp3tag-v3-33-1-released/70542 "2026-01-22T09:05:22Z")
**Posts on this page:** 1
**Showing post:** 4

<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 6, 2026, 11:17am UTC](https://community.mp3tag.de/t/mp3tag-v3-33-1-released/70542/4 "2026-02-06T11:17:20Z")

</div>

I've just released **Mp3tag v3.33.1** which includes bug fixes and other improvements that have been reported since the last release. If you're curious, the [changelog](https://www.mp3tag.de/en/changelog.html) has the complete list.

Most notably, it reverts back to the previous behaviour where it doesn't try to preserve umodified ID3v2 frames and MP4 atoms. When saving, Mp3tag now writes tags according to its documented [internal mappings](https://docs.mp3tag.de/mapping/) by default.

If someone prefers minimal changes applied to the tag, I've added the configuration options **Reuse unmodified ID3v2 frames** and **Reuse unmodified MP4 atoms** at **Options → Tags → Advanced**.

If those options are enabled, existing user-defined fields for which a mapping exists are not remapped to the target representation unless the field value changes. As a result, mapped fields are only rewritten when their corresponding field contents are modified.

---

_[View the full topic](https://community.mp3tag.de/t/mp3tag-v3-33-1-released/70542)._