# %\_playlist\_filename% etc. not available/ functional anymore

**URL:** https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092
**Category:** Support
**Created:** [April 21, 2026, 7:16am UTC](https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092 "2026-04-21T07:16:49Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![ehrlacher](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/e/5e9695/32.png) [@ehrlacher](https://community.mp3tag.de/u/ehrlacher)
#### Post date: [April 21, 2026, 7:16am UTC](https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092/1 "2026-04-21T07:16:49Z")

</div>

After trying everything and asking in the Forum I dare to call it a Bug:

The playlist related placeholders ( %\_playlist\_filename%, %\_playlist\_filename\_ext%, %\_playlist\_folderpath% ) that are described in the docs aren't available from the context menu (unlike the other placeholders) and If You add them manually as a column there are never filled though a playlist is opened.

Thanks for caring.

---

<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: [April 21, 2026, 7:59am UTC](https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092/2 "2026-04-21T07:59:46Z")

</div>

I just loaded a playlist into MP3tag ("Kalle.m3u") and checked with Convert\>Tag-Tag

 ![grafik](https://community.mp3tag.de/uploads/default/original/3X/e/4/e41a18bcd515cd98c3217a23e7f610b92dca3aa5.png)  
(the folder path is also available, but that would be too intimate)

So the variables are filled - I assume that they are read-only and only available in the context of a playlist but not generally, like e.g. %\_counter% which also cannot be used sensibly in a column.

---

<div class="post-metadata">

### Author: ![ehrlacher](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/e/5e9695/32.png) [@ehrlacher](https://community.mp3tag.de/u/ehrlacher)
#### Post date: [April 21, 2026, 9:32am UTC](https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092/3 "2026-04-21T09:32:23Z")

</div>

Thanks, now I understand how "it" works - You can obviously only show tags that are already written in the \*.mp3 file in columns.

So as a test I definied a new field %playlist\_release% definied an action from type "format value" (I guess this is the english name, "Tag Feld formatieren") and then I was/am able to see %playlist\_release% as a column filled with the name of my actual playlist...

... but IMHO this wasn't what %\_filename\_playlist% was meant to do but it should so the name of the actual "loaded" playlist to the user

(In my test it would always show the last value written to %playlist\_release% even if I opened it not from a playlist or from another playlist, but didn't start the formatting action...

---

<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: [April 22, 2026, 3:50pm UTC](https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092/4 "2026-04-22T15:50:37Z")

</div>

Yes, I think there was a slight misunderstanding. [Playlist-related information fields](https://docs.mp3tag.de/format/#playlist) are only available when a playlist was loaded.

* * *

I'm moving this back to #Support .

---

<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: [April 29, 2026, 3:50pm UTC](https://community.mp3tag.de/t/playlist-filename-etc-not-available-functional-anymore/71092/5 "2026-04-29T15:50:39Z")

</div>

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