# Export properties of current embedded cover (incl. dimensions)

**URL:** https://community.mp3tag.de/t/export-properties-of-current-embedded-cover-incl-dimensions/57307
**Category:** General Discussion
**Created:** [May 15, 2022, 7:48am UTC](https://community.mp3tag.de/t/export-properties-of-current-embedded-cover-incl-dimensions/57307 "2022-05-15T07:48:36Z")
**Posts on this page:** 4
**Page:** 1

<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 15, 2022, 7:48am UTC](https://community.mp3tag.de/t/export-properties-of-current-embedded-cover-incl-dimensions/57307/1 "2022-05-15T07:48:36Z")

</div>

I would like to see that when exporting an embedded picture to file with the action of the type "Export cover to file" that all the properties are taken from the current picture - and not just from the first.  
So, e.g. if a cover file name is defined as  
`%album%_%_cover_type%_%_cover_width%x%_cover_height%`  
and there are embedded picture with the property  
front: `600*539`  
and  
back: `840*472`  
then the resulting filenames for the picture are:  
My Album\_Front Cover\_600x536  
My Album\_Back Cover\_600x536  
whereas  
My Album\_Back Cover\_840x472  
would have been correct.

PS: even though most front and back covers of the same album would probably have the same size, there are a number of other possible cover types that most likely have different properties: Leaflet, media, icon, Publisher logotype etc.  
So it would have its use cases ...

---

<div class="post-metadata">

### Author: ![Roland](https://community.mp3tag.de/user_avatar/community.mp3tag.de/roland/32/8001_2.png) [@Roland](https://community.mp3tag.de/u/Roland)
#### Post date: [May 16, 2022, 6:39am UTC](https://community.mp3tag.de/t/export-properties-of-current-embedded-cover-incl-dimensions/57307/2 "2022-05-16T06:39:51Z")

</div>

The alignment of the attributes of all embedded images enables the comparison by corresponding routines. In this way, covers whose type or dimensions do not match the individual specifications can be automatically removed and reordered by procedures. This gives MP3TAG basic functionality in the field of automatic image processing. 👍👍

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [May 16, 2022, 12:38pm UTC](https://community.mp3tag.de/t/export-properties-of-current-embedded-cover-incl-dimensions/57307/3 "2022-05-16T12:38:42Z")

</div>

Thank you both for the suggestion! I've added this with [Mp3tag v3.14k](https://community.mp3tag.de/t/455).

---

<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: [June 15, 2022, 12:39pm UTC](https://community.mp3tag.de/t/export-properties-of-current-embedded-cover-incl-dimensions/57307/4 "2022-06-15T12:39:10Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
