# Preventing unwanted Case Conversion script actions - logging/review/dummy run possible?
**URL:** https://community.mp3tag.de/t/preventing-unwanted-case-conversion-script-actions-logging-review-dummy-run-possible/55403
**Category:** Support
**Created:** [December 6, 2021, 4:41pm UTC](https://community.mp3tag.de/t/preventing-unwanted-case-conversion-script-actions-logging-review-dummy-run-possible/55403 "2021-12-06T16:41:44Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@mr-b](https://community.mp3tag.de/u/mr-b)
#### Post date: [December 6, 2021, 4:41pm UTC](https://community.mp3tag.de/t/preventing-unwanted-case-conversion-script-actions-logging-review-dummy-run-possible/55403/1 "2021-12-06T16:41:44Z")
Hi
I'm wanting to use a script to fix all the inconsistent cases in my library and something like this seems to fit my needs.
> [@Need Help With "Case Conversion"; Scripts](https://community.mp3tag.de/t/need-help-with-case-conversion-scripts/13708):
>
> Hey guys. I'm going to apologize in advance for asking about something which has likely been asked countless times before, but I'm having a very hard time finding the information I need. Basically, I would like to run a "case conversion" which corrects filenames/tags to Mixed Case on slightly over 30k files. I found the stock Action for doing this in Mp3tag, but it has a few unwanted quirks. For instance, the filename "04 - W.A.S.P.mp3" is changed to "04 - W.a.s.p.mp3". Roman numerals are a…
However I'm wary of a script making huge numbers of changes with potentially unwanted results without a method of logging what has been changed or reviewing or reverting changes. The ideal would be for the script to do a dummy run without making changes until they are approved.
Like the quoted thread's OP, I'm not a developer, so please be gentle!
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [December 6, 2021, 4:57pm UTC](https://community.mp3tag.de/t/preventing-unwanted-case-conversion-script-actions-logging-review-dummy-run-possible/55403/2 "2021-12-06T16:57:01Z")
No test run, no log, no reverting (unless you undo it all).
The only way out would be: never to use \_ALL as target for a case conversion.
Filter for files that really should get treated.
E.g. all other languages other than English do not capitalize every word in a headline (and I think not even in English that is correct).
So, your precaution is right, not to let loose such a script on all the files in one go - take a subset that you can check at a glance and correct easily.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [December 6, 2021, 7:18pm UTC](https://community.mp3tag.de/t/preventing-unwanted-case-conversion-script-actions-logging-review-dummy-run-possible/55403/3 "2021-12-06T19:18:26Z")
> [@mr-b](#):
>
> The ideal would be for the script to do a dummy run without making changes until they are approved.
Mp3tag doesn't offer something like `--dry-run`
In addition to @ohrenkino s "filter and check" advice, I strongly suggest to backup your collection before you apply mass changes. In the worst case, you could restore your files from such an actual backup.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [February 9, 2026, 12:29pm UTC](https://community.mp3tag.de/t/preventing-unwanted-case-conversion-script-actions-logging-review-dummy-run-possible/55403/4 "2026-02-09T12:29:33Z")