# Feature Suggestion: Make »Remove fields except« do what the name promises?

**URL:** https://community.mp3tag.de/t/feature-suggestion-make-remove-fields-except-do-what-the-name-promises/7653
**Category:** General Discussion
**Created:** [December 26, 2008, 6:58pm UTC](https://community.mp3tag.de/t/feature-suggestion-make-remove-fields-except-do-what-the-name-promises/7653 "2008-12-26T18:58:36Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Moonbase](https://community.mp3tag.de/user_avatar/community.mp3tag.de/moonbase/32/207_2.png) [@Moonbase](https://community.mp3tag.de/u/Moonbase)
#### Post date: [December 26, 2008, 6:58pm UTC](https://community.mp3tag.de/t/feature-suggestion-make-remove-fields-except-do-what-the-name-promises/7653/1 "2008-12-26T18:58:36Z")

</div>

I just found that the "Remove fields except« action doesn’t work as it’s name would suggest: Apparently it only removes fields _known_ to Mp3tag.

I had the situation where I wanted to do a »Clean« action to remove some »foreign« tags from a stream editor (SE.. mentioned elsewhere), and some »private« fields another application writes. No luck (checked using _metamp3 --info filename.mp3_).

**Could »remove fields except« be changed in behaviour such that it behaves like _STRG+R/STRG+Z_? (Remove all tags, »undo« [rewrite] only those known by Mp3tag and specified by user?)**

This would allow for _really_ removing any crap/unwanted tags other applications (sadly) write, so one would end up with »clean« tags. (Or, in my case, have the other application see the analysis tags missing and re-calculate them.)

(Used Mp3tag v2.42b to test this.)