Please have a look at Names and mapping of ID3v2 tag fields for a complete list of ID3v2 tag fields.
The order below, is the order in which Mp3tag reads the different tags (that means that displaying APEv2 tags is prioritized over displaying ID3v1 tags).
if enabled, Mp3tag reads an existing ID3v1 tag.
if enabled, Mp3tag reads an existing ID3v2 tag.
if enabled, Mp3tag reads an existing APEv1 or APEv2 tag.
if enabled, Mp3tag writes an ID3v1 tag to the file.
if enabled, Mp3tag writes an APEv2 tag to the file. If the file already has an APEv1 tag, Mp3tag will update this tag to an APEv2 tag. If the file has an ID3v1 tag, Mp3tag will update this tag too.
if enabled, Mp3tag writes an ID3v2 tag to the file.
if enabled, Mp3tag writes only an ID3v2 tag, if the information in the tag input fields exceeds the limitations of the ID3v1 tag. If the file already has an ID3v2 tag, Mp3tag will update this tag. If the tag contains user definied genre, also an ID3v2 tag is written.
newest revision of the ID3v2 standard. Tags are written in Unicode as UTF-8 encoded string. If you have problems with displaying the tags in other programs, please aks their authors to support ID3v2.4 (or switch to another option).
if enabled, Mp3tag writes ID3v2.3 tags in Unicode encoded as UTF-16 LE.
if enabled, Mp3tag doesn't use Unicode when writing ID3v2 tags. This is useful if you are using software or devices (like some car radios) which can't read tags stored in Unicode format.
if enabled, Mp3tag removes an existing ID3v1 tag.
if enabled, Mp3tag removes an existing ID3v2 tag.
if enabled, Mp3tag removes an existing APEv1 or APEv2 tag.
All content and graphics are protected by copyright law! Copyright © 2000-2010 Florian Heidenreich