Let's have a look at two common scenarios. These are some of the reasons for having a corrupted or damaged PNG file. When the png file was not transferred properly, or there was a disruption during the file transfer into your system. Trying to open a PNG file with corrupt software. Improperly removing the memory card while in use. The only real solution seems to be to wait until MS fix this.When there is a virus in the system's storage device.

The one possible solution seems to be rather OTT, adding the image to a canvas and rescaling that, but if you've got more than one or two images, this can cause serious lag:

This same issue has been reported and confirmed as a bug by the Edge team twice, since at least November 2016, with no fix.Īnd there are several other posts about it here on SO.

(That demo is from a comment on a MS blogpost from 2013: so it's been talked about for at least four years now!) Really digging into the history, here's another demo - from 2013! Here's another post from August 2015 about this issue, so it's definitely nothing new! Here's a thread on an MS forum about it (note how some people are bizarrely desperate to wish the problem away, blaming it on graphics cards!):

Recently MS seem to have fiddled with it, but they've certainly not fixed it. The issue actually pre-dates the release of Edge. And sometimes, just sometimes, an image seems to remain smoothly scaled! (It seems that one way to definitely re-create the problem is to re-size an image after the page is loaded, such as setting the size in your JSfiddle to 50x50px - in Edge, the image resizes and looks awful, but in other browsers the result is smooth.) I can confirm your experience of seeing a brief flash of smoothly-rescaled image, too. Poor-quality downscaling of images is a known problem in Edge, and has been for years now.

Microsoft edge logo jpg image