# MP3 WWW field (WXXX frame) cannot be exposed in the file list
**URL:** https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209
**Category:** No Bugs
**Created:** [November 21, 2025, 11:59am UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209 "2025-11-21T11:59:59Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@kanda](https://community.mp3tag.de/u/kanda)
#### Post date: [November 21, 2025, 11:59am UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209/1 "2025-11-21T11:59:59Z")
The `%www%` field in the file list shows
only WXXX frames whose description is empty.
WXXX frames with a non-empty description are not shown:
We were told that a WXXX frame with a non-empty description
can be shown using %www _description_% (above: `%www wiki%`)
(see [[You can use %WWW _DESCRIPTION_%](https://community.mp3tag.de/t/cant-add-more-than-one-www-tag-info-wma-file-is-it-correct/70147/10)])
Technically this is true — _but it is functionally pointless_.
The description is _arbitrary user-supplied data_ and is not a part of the tag/field/frame identity.
Users cannot enter %www _description_% in advance, because they cannot know which descriptions the file’s creator used, and there may be many different ones (see “SHAZAM TRACK” description above). Also there may be many abusive descriptions, like “1”, “2”, “3”, etc, given to URLs to workaround “[single-valued WWW](https://community.mp3tag.de/t/cant-add-more-than-one-www-tag-info-wma-file-is-it-correct/70147/8)” ID3 v2.3, v2.4 restriction.
%www% should expose _all_ WXXX frames, regardless of their descriptions.
Mp3tag version tested: v3.32c, Nov 19 2025 12:36:00 (64-bit)
This is a followup to the [[Can’t add more than one WWW tag into WMA file](https://community.mp3tag.de/t/cant-add-more-than-one-www-tag-info-wma-file-is-it-correct/70147/10)]
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 21, 2025, 12:50pm UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209/2 "2025-11-21T12:50:56Z")
> [@kanda](#):
>
> Users cannot enter %www _description_% in advance, because they cannot know which descriptions the file’s creator used
That is why there is the extended tags dialogue.
BTW: the description is not part of
> [@kanda](#):
>
> _arbitrary user-supplied data_
but part of the field structure according to standard.
Similiar files that allow such a mechanism (for ID3V2.x tags) are COMM and TXXX - for such files you also would have to check which name the creator has chosen.
See also this thread about a similar problem with itunes comment fields:
> [@Are these Tags important or can I delete these?](https://community.mp3tag.de/t/are-these-tags-important-or-can-i-delete-these/50285):
>
> HI. I recently took the Time to organize and clean my MP3-Collection and I noticed there are a lot of Tags in some of them that I didn't put there. And now I'm wondering if I can delete these without destroying anything. These Tags are: AUDIOCHANNELS COMMENT ITUNES\_CDDB\_1 COMMENT ITUNES\_CDDB\_IDS COMMENT ITUNES\_CDDB\_TRACKNUMBER COMMENT ITUNNORM COMMENT ITUNPGAP COMMENT ITUNSMPB COMMENT MUSICMATCH\_BIO COMMENT MUSICMATCH\_MOOD COMMENT MUSICMATCH\_TEMPO COMPATIBLE\_BRANDS DESCRIPTION ENC…
---
### Author:  [@kanda](https://community.mp3tag.de/u/kanda)
#### Post date: [November 21, 2025, 2:00pm UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209/3 "2025-11-21T14:00:53Z")
> [@ohrenkino](#):
>
> That is why there is the extended tags dialogue
Good for you. I prefer to see the user-supplied URLs of any kind directly in File List.
> [@ohrenkino](#):
>
> BTW: the description is not part of _arbitrary user-supplied data_
Setting aside your interpretation of the ID3v2 spec. According to the documentation [[Tag Field Mappings](https://docs.mp3tag.de/mapping/)] the field `%www%` maps to `WXXX` frame, not “`WXXX` _frame with empty description_”. Let it be as documented.
> [@ohrenkino](#):
>
> See also this thread about a similar problem with itunes comment fields
I do not see similarities.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 21, 2025, 2:14pm UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209/4 "2025-11-21T14:14:58Z")
> [@kanda](#):
>
> I do not see similarities.
The similarities are:
- There are further fields that allow an additional description (here: COMM and TXXX). As the thread is a little older, the www field was not commonly in use.
- User found it irritating that some of these fields did or did not appear in other applications, depending on whether the interpreted the description or not)
- All these fields and their attributes can be displayed in MP3tag.
- For each of these fields with an extra description a separate GUI element has to be defined.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [November 21, 2025, 7:22pm UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209/5 "2025-11-21T19:22:05Z")
> [@kanda](#):
>
> We were told that a WXXX frame with a non-empty description
> can be shown using %www _description_% (above: `%www wiki%`)
> (see [[You can use %WWW _DESCRIPTION_%](https://community.mp3tag.de/t/cant-add-more-than-one-www-tag-info-wma-file-is-it-correct/70147/10)])
As I've explained before, this is how Mp3tag works wrt. to the WWW field for ID3v2. It's a tradeoff I made to support the description part of the field without adding format-specific UI.
I don't plan to change the behaviour and I'm moving this to #Bug Reports > No Bugs
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [December 21, 2025, 7:22pm UTC](https://community.mp3tag.de/t/mp3-www-field-wxxx-frame-cannot-be-exposed-in-the-file-list/70209/6 "2025-12-21T19:22:41Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.