# Not possible to change filename w/ extension via file view

**URL:** https://community.mp3tag.de/t/not-possible-to-change-filename-w-extension-via-file-view/12107
**Category:** Support
**Created:** [June 6, 2011, 7:09pm UTC](https://community.mp3tag.de/t/not-possible-to-change-filename-w-extension-via-file-view/12107 "2011-06-06T19:09:15Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![ptrk.mj](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ptrk.mj/32/300_2.png) [@ptrk.mj](https://community.mp3tag.de/u/ptrk.mj)
#### Post date: [June 7, 2011, 3:00pm UTC](https://community.mp3tag.de/t/not-possible-to-change-filename-w-extension-via-file-view/12107/5 "2011-06-07T15:00:50Z")

</div>

I'm not searching for a workaround. I know I can do this with an action. I've reported this as I considered it a bug/oversight.

> [@](#):
>
> Changing the content of %\_filename\_ext% from within a list view cell with consequence to the real filename **should not be accepted** anyway by Mp3tag.

Why?

In my opinion setting 'Field' to %\_filename\_ext% should result in modification of filename _with_ extension even though it may cause Mp3tag not see the file (if you change extension to one denoting unsupported file format).

The default setting is %\_filename% so it wouldn't cause any trouble for those not fiddling with their column settings.

> [@](#):
>
> There is **only one** action in Mp3tag which can do this:

That's right. Another inconsistency. If "Replace with regular expression" applies regex to the whole filename than why "Format value" should act different?

I think the best solution would be to provide two pseudo tag-fields \_FILENAME and \_FILENAME\_EXT in the future.

---

_[View the full topic](https://community.mp3tag.de/t/not-possible-to-change-filename-w-extension-via-file-view/12107)._