# How do I quickly populate custom lists for various fields?

**URL:** https://community.mp3tag.de/t/how-do-i-quickly-populate-custom-lists-for-various-fields/70259
**Category:** Support
**Created:** [December 2, 2025, 2:46am UTC](https://community.mp3tag.de/t/how-do-i-quickly-populate-custom-lists-for-various-fields/70259 "2025-12-02T02:46:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![KHS](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/k/65b543/32.png) [@KHS](https://community.mp3tag.de/u/KHS)
#### Post date: [December 2, 2025, 2:46am UTC](https://community.mp3tag.de/t/how-do-i-quickly-populate-custom-lists-for-various-fields/70259/1 "2025-12-02T02:46:40Z")

</div>

Excited to see (now that I’ve tagged over 7,000 files manually LOL) that there are now custom list dropdowns. How do I populate those lists quickly from the hundreds of different Composers, Lyricists, Conductors, etc., that I’ve already normalized? Is it all fields or only certain ones?

---

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [December 2, 2025, 7:23am UTC](https://community.mp3tag.de/t/how-do-i-quickly-populate-custom-lists-for-various-fields/70259/2 "2025-12-02T07:23:49Z")

</div>

You can have a look here, including Import/Export to populate your Custom List Values:

> [@Add custom user-defined Genres](https://community.mp3tag.de/t/add-custom-user-defined-genres/61122):
>
> Add and Edit user-defined Genres via Custom List Values Every field on the Tag Panel can have custom values added to its drop-down list. These can be customized via [Options → Tag Panel](https://docs.mp3tag.de/customization/tag-panel/) and the Genre field is no exception. You can use Options → Tag Panel → Genre → Custom list values → Manage... to edit the list of custom Genres and also hide the standard genres, if you prefer your own. The following screenshot exemplifies the process: Import and Export of Custom List …

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [December 2, 2025, 7:46am UTC](https://community.mp3tag.de/t/how-do-i-quickly-populate-custom-lists-for-various-fields/70259/3 "2025-12-02T07:46:52Z")

</div>

> [@KHS](#):
>
> hundreds of different Composers, Lyricists, Conductors

The techincal aspects aside: I wonder how many names you really have that participated in a noticeable amount of pieces.  
As the function does not add data to existing data but sets the entry as absolute item, it is not possible to create a list of performers - which means that you need any combination as separate entry which will create such a long list, that I doubt the amount of offered entries will really ease the work.  
E.g. looking at a folder with samplers and 28,000 files, the list of (unique) artist names adds up to some 14,000 artist names - which means that only very few names appear more than twice, most of them probably only once.  
If there are performers with difficult spelling then I think sorting by name and the use of the tag panel is much easier than to maintain a longish list of custom entries.  
But as the use cases vary, I speak only for myself.

To get a list of e.g. composers, load all the files, create an export script with the expression  
`$loop(%composer%,1)%composer%$loopend()`  
and let it output a text file.  
Then you can use the resulting list as input for the custom lists for fields.

---

<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: [January 1, 2026, 7:47am UTC](https://community.mp3tag.de/t/how-do-i-quickly-populate-custom-lists-for-various-fields/70259/4 "2026-01-01T07:47:33Z")

</div>

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