# Why some of my custom tags stored in UPPERCASE and others in lowercase?

**URL:** https://community.mp3tag.de/t/why-some-of-my-custom-tags-stored-in-uppercase-and-others-in-lowercase/56087
**Category:** Support
**Created:** [January 27, 2022, 4:52pm UTC](https://community.mp3tag.de/t/why-some-of-my-custom-tags-stored-in-uppercase-and-others-in-lowercase/56087 "2022-01-27T16:52:52Z")
**Posts on this page:** 1
**Showing post:** 8

<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: [January 27, 2022, 5:27pm UTC](https://community.mp3tag.de/t/why-some-of-my-custom-tags-stored-in-uppercase-and-others-in-lowercase/56087/8 "2022-01-27T17:27:46Z")

</div>

There is noting wrong with direct editing in the file list, i.e., delayed double click to enter editing mode. It's perfectly fine to do it this way 🙂

What I meant was that the way you've set up the column for the custom field via _View → Columns..._ determines the way the field name is written to the file. If you use `%MyField%` as _Field_ in the configuration, it would use `MyField` when writing the custom tag to the file. If you use `%MYFIELD%`, `MYFIELD` is written.

This is purely cosmetic and doesn't make a difference from a technical perspective. If you want consistency, I'd use all uppercase field names — because the extended tag dialog and the Tag Panel also use those.

---

_[View the full topic](https://community.mp3tag.de/t/why-some-of-my-custom-tags-stored-in-uppercase-and-others-in-lowercase/56087)._