# ACTIONS that mimics a WYSIWYG to Change File Extension or File Name and Extension (2022-2023)

**URL:** https://community.mp3tag.de/t/actions-that-mimics-a-wysiwyg-to-change-file-extension-or-file-name-and-extension-2022-2023/60139
**Category:** General Discussion
**Created:** [February 20, 2023, 10:00pm UTC](https://community.mp3tag.de/t/actions-that-mimics-a-wysiwyg-to-change-file-extension-or-file-name-and-extension-2022-2023/60139 "2023-02-20T22:00:48Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [February 21, 2023, 6:49am UTC](https://community.mp3tag.de/t/actions-that-mimics-a-wysiwyg-to-change-file-extension-or-file-name-and-extension-2022-2023/60139/3 "2023-02-21T06:49:20Z")

</div>

> [@wneclass2018](#):
>
> Change BOTH File Name (%\_filename%) and File Extension (%\_extension%) by wneclass2018 (December 29th 2022).mta

Somehow that action does not make any difference: upper case stays upper case, mixed case stays mixed case .. Do I really have to type in the new filename and the extension and then run the action? Wouldn't it then be much easier to do that in the file explorer which saves me the effort to create fields, write them, start the action and then delete them?  
And even though you claim to have a

> [@wneclass2018](#):
>
> WYSIWYG

way - it is not: if I enter e.g. mP3 as new file extension, the extension becomes lower case.  
Why doesn't the action create the fields it needs when all it does is to convert to lower case only any way?  
Where is the benefit that I have to create user-definded fields first, then apply the action, then delete these fields again?  
While a simple "Replace with regular expression" would serve the same purpose much quicker, see

> [@Change file extension to lowercase - Regular expression](https://community.mp3tag.de/t/change-file-extension-to-lowercase-regular-expression/59816):
>
> Seems like the regular expression thread is locked Previously found some nice examples there, why was it closed? Not an overly complex one but couldn't find it so posting here in case it's useful to someone else: Had a number of uppercase file extensions and was looking to convert them all to lowercase; there doesn't seem to be such a thing as the '"file extension" field so here's my take on it: Field : \_FILENAME Regular expression : \.(.\*)$ Replace with : .$lower($1) Cheers,

It could still be that I have simply not grasped what this should be all about.

---

_[View the full topic](https://community.mp3tag.de/t/actions-that-mimics-a-wysiwyg-to-change-file-extension-or-file-name-and-extension-2022-2023/60139)._