# Pruning non-compliant dimension album art

**URL:** https://community.mp3tag.de/t/pruning-non-compliant-dimension-album-art/68678
**Category:** Support
**Created:** [May 31, 2025, 5:52am UTC](https://community.mp3tag.de/t/pruning-non-compliant-dimension-album-art/68678 "2025-05-31T05:52:20Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [May 31, 2025, 6:17am UTC](https://community.mp3tag.de/t/pruning-non-compliant-dimension-album-art/68678/2 "2025-05-31T06:17:02Z")

</div>

It is still that way as described here:

> [@Action to remove an embedded Album art of a certain size?](https://community.mp3tag.de/t/action-to-remove-an-embedded-album-art-of-a-certain-size/62818):
>
> Hello, I am getting a batch of songs that have two embedded front cover album images, one at 500x500 and one at 700x700. I have an action that works on the higher res. and normalizes it to 600x600 (which I want to keep as the only album art in the song) but the 500x500 hangs out there and I have to manually remove it. Is there an action that can act on the that single file and its dimensions and purge it for me? Thanks!

It would be nice if the field PICTURE could be addressed with something like the $meta... functions for other fields.

---

_[View the full topic](https://community.mp3tag.de/t/pruning-non-compliant-dimension-album-art/68678)._