PDFJadoo › Blog › JPG to PNG: The Transparency Myth

JPG to PNG: no, the background stays — and that is not the point

The direct answer: converting a JPG to PNG does not make the background transparent — a JPG contains no transparency information at all, so there is nothing for the conversion to recover; the PNG is an exact, pixel-for-pixel copy of the JPG, solid background included. JPG to PNG states it in its own FAQ's words: PNG stores every pixel exactly, so the PNG is a perfect copy of the picture in your JPG — the file may be bigger, never worse. That sentence contains the conversion's real value, which the myth obscures: JPG loses a little quality at every re-save, and PNG loses none — so converting once gives you a lossless working copy whose hundredth edit looks like its first. What conversion cannot do is equally mechanical: detail the JPG's compression already discarded does not return, and transparency that was never stored cannot be invented. Removing a background is a different job (an editor's selection work), after which PNG is exactly the right container for the result. This article separates the three ideas the search results tangle: copying, restoring, and cutting out.

Free, in your browserFiles never uploadedLossless copy · no invented alpha · bigger, never worse
PDFJadoo logoBy the PDFJadoo Team6 min read
Diagram: a JPG photo becoming an identical-looking PNG, with a note that no transparency is created
Same picture, new container. The gain is in what stops happening afterwards.

Why the myth survives

The direct answer: PNG is famous for transparency, so “convert to PNG” sounds like “add transparency” — but a format can only carry what the source contains, and a JPG's pixels are fully opaque, every one of them a solid colour. The converter faithfully copies those solid pixels into the format that could hold transparency, holding none. One quotable test settles any converter's honesty: if a tool claims its JPG-to-PNG conversion produced a transparent background automatically, it either guessed at the background colour and cut it (an edit, with ragged edges on anything complex) or it is describing the format, not the result. Genuine background removal is selection work — increasingly automated, but an edit with judgement in it — and its output then saves as PNG precisely because PNG keeps the alpha the edit created.

What the JPG discarded stays discarded, too. JPG compression throws away fine detail permanently at each save; the PNG copy preserves the current state exactly — artefacts included. Converting is a preservative, not a restorer, and the distinction decides real workflows: the photo you will crop, annotate and re-export five times deserves the PNG working copy on day one.

The re-save problem, in one paragraph

The direct answer: every time a JPG is opened and saved again, its compression runs again on already-compressed data, and the losses compound — edges soften, flat areas blotch — while a PNG can be saved a thousand times and stay bit-identical. That compounding, called generation loss, is the conversion's whole economic case: pay a larger file once, stop paying quality forever. Delivery can still be JPG at the end; the master should not be.

Convert a JPG to PNG, step by step

The direct answer: drop the JPG — or a whole batch — onto the converter, press Convert to PNG, and download each file or the batch as a ZIP, at the same full size.

Step 1 — drop your JPG image, or a batch, onto JPG to PNG. Everything happens on your device.

Step 2 — press Convert to PNG. There is no quality setting to choose, because there is no loss to negotiate: every pixel is copied exactly.

Step 3 — download singly or as a ZIP. Same dimensions as the JPG; expect a larger file — lossless storage of a photograph costs bytes, and that is the preservative working.

Step 4 — file the PNG as the working master. Edit from it; export delivery copies (JPG, WebP) from it; never edit the delivery copies themselves.

If you actually need transparency

The direct answer: remove the background in an editor first — select the subject, delete the surroundings — then keep and deliver the result as PNG, the format whose alpha channel the edit needs. The order matters: edit creates transparency; conversion only preserves it. The reverse order — convert, then hope — is the myth's itinerary.

Convert for the right reason: stop the losses, keep the master.

A pixel-perfect copy at full size, batch as ZIP — and no transparency promised that was never there.

Open JPG to PNG

A worked example: the much-edited product photo

The direct answer: a marketplace seller's product JPG — cropped, re-cropped for three platforms, annotated, re-exported a dozen times — has visibly softened by its twelfth save; converted to PNG at the start of the next listing cycle, its next twelve edits cost it nothing. The walkthrough's before/after is the generation-loss lesson in one file: the twelfth-generation JPG beside the first, edges furred; the PNG branch, saved as often, unchanged. The seller's rule going forward is the article's: camera JPGs are delivery copies; the first act of any editing session is the PNG master.

Edge cases

Screenshots and text. The strongest case: JPG artefacts cluster around sharp edges, so a screenshot's PNG copy freezes its current state before further edits add more — and any new screenshot should be captured as PNG from the start.

“But the file got bigger.” Expected and correct: the PNG may be several times the JPG's size. Storage is the price of the preservative; delivery formats exist for the journeys where bytes matter.

Scans received as JPG. Convert before any cleanup work (deskew, fix, OCR preparation) so the pipeline's intermediate saves stop taxing the image.

Before you finish: the 60-second check

Fair questions

Does converting JPG to PNG make the background transparent?

No. A JPG contains no transparency information, so there is nothing to recover — the PNG is a pixel-perfect copy with the same solid background. Transparency is created by an editing step (removing the background), and PNG is then the right container for the result.

Will JPG to PNG improve my picture's quality?

No — and it will not worsen it either. PNG stores every pixel exactly, so the copy is perfect, including any artefacts the JPG already had. Detail the JPG discarded earlier does not return; what stops is further loss at every future re-save.

Why is the PNG file so much bigger?

Lossless storage of a photograph costs bytes — every pixel kept exactly. The file may be bigger, never worse. Keep the PNG as the working master and export smaller JPG or WebP copies for delivery.

Can I convert a whole batch?

Yes — drop as many JPG files as you like. Each converts with the same settings; download them one by one or all together as a ZIP.

When is JPG to PNG actually worth doing?

Before repeated editing: the PNG working copy ends generation loss, so the hundredth save looks like the first. Also for screenshots and graphics whose sharp edges JPG artefacts attack first.

Is my image uploaded?

No — the picture is decoded and re-encoded entirely on your device; your files never leave it.

Tool behaviour — pixel-exact lossless copying at the same full size, batch conversion with ZIP download, and the “bigger, never worse” framing — is from PDFJadoo's own JPG to PNG page. Checked 18 November 2026.

Keep reading