# Problems with jpg covers in progressive format

**URL:** https://community.mp3tag.de/t/problems-with-jpg-covers-in-progressive-format/69404
**Category:** Support
**Created:** [August 13, 2025, 4:23am UTC](https://community.mp3tag.de/t/problems-with-jpg-covers-in-progressive-format/69404 "2025-08-13T04:23:28Z")
**Posts on this page:** 1
**Showing post:** 10

<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: [August 13, 2025, 1:48pm UTC](https://community.mp3tag.de/t/problems-with-jpg-covers-in-progressive-format/69404/10 "2025-08-13T13:48:25Z")

</div>

> [@Mp3Tag is not exporting all my cover art](https://community.mp3tag.de/t/mp3tag-is-not-exporting-all-my-cover-art/69294/33):
>
> I'm wondering Ohrenkino you remove the 'e' from the .jpeg extension to get .jpg it won't work for you...

That is not what I said.  
Your idea to transform a file

> [@Sergius](#):
>
> I deal with this type of file sometimes. I remove the letter 'e' from the .jpeg extension to get a .jpg, and the image appears perfectly...

(or that is what I understood) by simply changing an extension does not work.  
The discussed problem was a difference in jpg-file-formats, one baseline and one progressive where progressive may cause problems.  
For me it sounded as though removing the "e" from jpeg to get "jpg" would change the file format - which it does not.

See eg.g here:

> [@New Features Proposal](https://community.mp3tag.de/t/new-features-proposal/17507/10):
>
> Stop that immediately, it is completely crazy to disguise a jpg file as a bmp file. For example ... the "IrfanView" detects the type failure immediately ... [image] DD.20160102.0940.CET [image]

---

_[View the full topic](https://community.mp3tag.de/t/problems-with-jpg-covers-in-progressive-format/69404)._