# Mp3tag inserts an extra space character in custom tag field names starting with COMMENT or WWW

**URL:** https://community.mp3tag.de/t/mp3tag-inserts-an-extra-space-character-in-custom-tag-field-names-starting-with-comment-or-www/71434
**Category:** Support
**Created:** [June 12, 2026, 8:19am UTC](https://community.mp3tag.de/t/mp3tag-inserts-an-extra-space-character-in-custom-tag-field-names-starting-with-comment-or-www/71434 "2026-06-12T08:19:05Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![yorickausyps](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/y/f6c823/32.png) [@yorickausyps](https://community.mp3tag.de/u/yorickausyps)
#### Post date: [June 12, 2026, 8:19am UTC](https://community.mp3tag.de/t/mp3tag-inserts-an-extra-space-character-in-custom-tag-field-names-starting-with-comment-or-www/71434/1 "2026-06-12T08:19:05Z")

</div>

To reproduce this issue add a new custom tag in the Extended Tag View (Alt+T) dialog, with a tag name that has` COMMENT` at the beginning and one or more arbitrary characters following, e.g. `COMMENTAR`, and then write something into the Value field and save it in the file. Now open the Extended Tag View (Alt+T) again and the new tag field got the name `COMMENT AR`, i.e. a space character has been inserted behind the COMMENT-part.  
A similar effect can be observed with standad tags that start with `WWW`. In this case the space always appears behind `WWW`, e.g. `WWWARTISTXY` becomes `WWW ARTISTXY`. All other standard tags act normal, that means that there does't turn up no extra space character, if their name is used together with some more characters at the end.  
Before storing the tags in the file:

 ![2026-06-12082116](https://community.mp3tag.de/uploads/default/original/3X/3/8/38b5ca0e82e9583af30705e295b1ea0b2599e74a.png)  
After storing and rereading the tags:  
 ![2026-06-12082302](https://community.mp3tag.de/uploads/default/original/3X/4/5/45842809f7731876eeb7728655faaf167f0034fb.png)  
Same effect also appears in web source scripts.

---

<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: [June 12, 2026, 8:35am UTC](https://community.mp3tag.de/t/mp3tag-inserts-an-extra-space-character-in-custom-tag-field-names-starting-with-comment-or-www/71434/2 "2026-06-12T08:35:16Z")

</div>

This is expected behaviour for these two fields and the part after `COMMENT` or `WWW` is treated as the description part of the respective ID3v2 frame.

---

<div class="post-metadata">

### Author: ![yorickausyps](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/y/f6c823/32.png) [@yorickausyps](https://community.mp3tag.de/u/yorickausyps)
#### Post date: [June 13, 2026, 8:53am UTC](https://community.mp3tag.de/t/mp3tag-inserts-an-extra-space-character-in-custom-tag-field-names-starting-with-comment-or-www/71434/3 "2026-06-13T08:53:58Z")

</div>

Thank you @Florian for this explanation, I didn't know that. It seems to me to be best practice to always in the first place insert a space between `COMMENT` or `WWW` and succeding chracters or words.  
This is necessary in web source scripts, because e.g. using `COMMENTX` in a script will always create a new tag field `COMMENT X` and never overwrite an already existing one with every run of the script. This is contrary to the usual behaviour of replacing existent tag fields if at the `Adjust tag information` screen the OK is given.

---

<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: [June 20, 2026, 8:54am UTC](https://community.mp3tag.de/t/mp3tag-inserts-an-extra-space-character-in-custom-tag-field-names-starting-with-comment-or-www/71434/4 "2026-06-20T08:54:51Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
