Common Image Conversion Mistakes, and the Quick Fix for Each

Keep the original until the copy has been accepted

Conversion is not always reversible. Moving to JPEG or WebP discards detail for good, flattening transparency cannot be undone, and rebuilding from pixels drops metadata. Once the original is deleted, none of that can be recovered. So treat the original as the master and keep it until the converted file has been accepted where it is going, whether that means published, uploaded or approved. Converting creates a new file beside the old one, so keeping both costs only disk space. If space is tight, a second drive or a cloud folder is cheaper than a lost original.

It also makes every other mistake on this page cheap. If you picked the wrong quality, the wrong background color or the wrong format, you convert again from the master. If the master is gone, you are stuck with whatever the first attempt left.

Treating conversion as a quality upgrade

No conversion adds detail. A PNG made from a JPEG keeps the JPEG's flaws and typically weighs several times more; do it only when something downstream insists on PNG, as in converting JPG to PNG. A picture passed through several lossy saves, such as JPEG to WebP to JPEG or a screenshot of a screenshot, loses a little each time, fastest when the settings or formats change between saves; convert once, from the best version you have, to the final format. The measurements are in image quality after converting.

Enlarging works the same way. An 800 x 600 image shown at 1600 x 1200 has four times the pixels (480,000 becomes 1,920,000) and exactly the same information, only blurrier. For print, work backwards from the output: a 6 x 4 inch print at 300 pixels per inch needs 1800 x 1200 pixels, and a smaller file looks soft however it is converted. The converter never enlarges raster images, for this reason.

Choosing a format that does not fit the content or the destination

Three variations of one error. Photographs saved as PNG are huge: a 12-megapixel photo as PNG is typically many times its JPEG size, and a 5 MB upload limit then rejects it; JPEG vs PNG has the numbers. Text, logos and screenshots saved as JPEG fuzz at the edges and are often not even smaller, so those belong in PNG. And the newest format helps nobody if the recipient cannot open it. Check what the destination accepts first, and when you cannot tell, use JPEG or PNG. If a site keeps refusing a file, why a website rejects your image lists the usual causes: format, size in bytes, pixel dimensions and file name.

Letting transparency, metadata and extensions surprise you

Transparency. JPEG cannot store see-through areas, so they must be filled with a solid color; this converter uses white unless you pick another. A white logo vanishes on it, and a dark one can get a pale halo. Pick the color of the place the picture will sit; the whole process is in transparent backgrounds when converting PNG to JPG.

Metadata. Converted copies lose camera data, location and capture date. That is a feature when you post publicly and a problem when your photo library sorts by date. Decide on purpose, using EXIF metadata and privacy when converting.

Extensions. Renaming photo.heic to photo.jpg changes a label, not the bytes. Programs that check content still see HEIC, and many sites reject the file. Real conversion rewrites the data; what an image file format is shows how files identify themselves.

Setting quality by habit instead of by test

Two opposite habits waste effort. Choosing the top of the slider for everything buys almost nothing visible: in my synthetic test, a gradient-and-noise picture at JPEG quality 100 was 4.6 times the size of the quality 90 file (1,534,583 against 330,904 bytes), and still not an exact copy. Choosing a very low number to hit a size limit produces blocks and fuzz around text. A better order is to cut pixel dimensions first, because halving each side leaves a quarter of the pixels, and then lower quality in small steps while comparing at full size. The testing method is laid out in image quality after converting.

A thirty-second check before a batch

1. Who receives it, and what do they accept? That decides the format.
2. Photo or flat graphic? That decides lossy or lossless.
3. Is anything transparent? If yes, and the target is JPEG, choose the background color.
4. Convert one representative file and read both sizes. If the new file is larger than the old one, stop and reconsider before doing a hundred.

Decision guide for the common cases

When you are in a hurry, find your case in the table and use the answer.

You have	You need	Do this
Camera photo	Small file for email or a form	JPEG, then check the size
Screenshot or logo	Same crispness, any size	PNG
Transparent PNG	JPEG-only destination	Pick the destination's background color first
Photo for your own web page	Fast loading	WebP or JPEG; reduce pixel size before quality
HEIC from an iPhone	Something that opens everywhere	JPEG (the converter opens HEIC only in Safari)
File too big after converting	Smaller	Keep the original format or lower the pixel size, not the quality

If you have already made one of these mistakes

Start by checking whether the original still exists somewhere: the recycle bin or trash, the phone's recently deleted album, the cloud drive's version history, a backup, or the chat where you first received the picture. A converted file can sometimes be the only survivor, and then the best you can do is make sure you do not convert it again, since each further lossy save removes a little more. If the file came out too large, small, dull or with the wrong background, convert again from the master with the right setting. If metadata is missing from copies already shared, nothing brings it back, but you can often re-enter the date by hand in a photo library. Mistakes at this level are almost always cheap to fix as long as one good source remains.

For next time, a small habit pays for itself: when you receive an important picture, copy it into a folder named for the job before touching it, and do all conversions on copies from that folder. Then a batch gone wrong is a ten-second redo rather than a lost afternoon, and you can compare any converted file against the source whenever a recipient says something looks off.