# ID3v2.4 YEAR vs DATE

**URL:** <https://community.mp3tag.de/t/id3v2-4-year-vs-date/16815>\
**Category:** Support\
**Created:** [April 9, 2015, 2:02am UTC](https://community.mp3tag.de/t/id3v2-4-year-vs-date/16815 "2015-04-09T02:02:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![neothe0ne](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/n/5fc32e/32.png) [@neothe0ne](https://community.mp3tag.de/u/neothe0ne)\
**Post date:** [April 9, 2015, 2:02am UTC](https://community.mp3tag.de/t/id3v2-4-year-vs-date/16815/1 "2015-04-09T02:02:29Z")

</div>

> [@](#):
>
> With Mp3tag v2.53 released almost one year ago we decided to combine the release year (ID3v2.3 frame TYER, displayed as YEAR) and release date (ID3v2.3 frame TDAT, displayed as DATE) in YEAR and display it as YYYY-MM-DD. The intention was to improve compatibility with other applications and the ID3v2 standard.
> 
> Since then we've received numerous support requests both on the Mp3tag Forums and via email from users who are unsatisfied with that change. Either because they use a different formatting of date values, use some value denoting a specific time frame (e.g., the 80s) or simply wanted to preserve values that were not fitting in the new date formatting scheme.
> 
> With Mp3tag v2.58 we revert this change to the previous behaviour.

Why is this quote applying to my ID3v2. **4** files? I thought this was only supposed to affect ID3v2.3?

(I've now realized that since 2.58, Mp3tag has been breaking my foobar2000 media library by mangling all my MP3 dates.)

---

<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:25pm UTC](https://community.mp3tag.de/t/id3v2-4-year-vs-date/16815/2 "2026-02-09T12:25:38Z")

</div>

Closed on February 9, 2026, 12:25pm UTC