PNG to JPG Converter

The product shoot went well, which is the problem. The camera pipeline delivered 47 PNGs at 11 or 12 megabytes each, the marketplace wants JPGs under a reasonable size, and the listing tool is already complaining about the first three uploads. Somewhere in the requirements document is the sentence that matters: main image on a pure white background. Your PNGs have transparency where the white should be, and the deadline is doing that thing deadlines do.

The PNG to JPG Converter above this article was built around that exact Thursday afternoon. Drop the batch, flatten every transparent background onto pure white, pick a quality level with a real slider instead of mystery defaults, and download 47 JPGs with their original filenames. Everything runs on your machine — an e-commerce catalog is not something anyone should have to upload to a stranger's server.

The direction of this conversion deserves respect, because it is the one-way door: PNG to JPG spends fidelity to buy file size, permanently. This page explains how to spend it well — what the quality numbers actually control, how white-background flattening works at the pixel level, and how the batch engine keeps a 47-file job from eating your browser tab.

PNG is lossless: every pixel you saved is the pixel you get back. JPEG is lossy: every save re-compresses the image through quantization, and whatever the quantization rounds away does not come back. Converting PNG to JPG is therefore a deliberate purchase — you are trading invisible amounts of image detail for dramatic reductions in file size, and the slider is the price tag.

Done once, at a sensible quality, the trade is excellent — a photograph at quality 0.85 looks identical to its PNG source at normal viewing sizes and weighs a fraction as much. Done carelessly — repeated saves, quality ratcheted downward each time — the trade compounds, and the artifacts stack visibly. The professional habit is simple: keep the PNG as the master, convert to JPG once per use, and re-export from the master whenever something changes.

The reverse trip has its own page — the JPG to PNG Converter documents the preservation direction — and the two tools are deliberately mirrors: same interface rhythm, opposite philosophy, no shared confusion about which one un-deletes detail. This one does not. Nothing does.

One myth worth killing while we are here: quality numbers do not multiply. Saving twice at 0.85 is not the same as saving once at 0.72 — each pass re-quantizes whatever pixels it receives, so the damage compounds in steps rather than multiplying into a tidy formula, and the second pass at 0.85 actually costs less than the first because the image has already been rounded once. The practical lesson is unchanged — one conversion from the master, always — but the reason is compounding arithmetic, not a phantom multiplication table.

A converter page telling you not to convert is either honest or confused, and the cases below settle which. JPEG is the wrong destination whenever the image is not photographic in nature or the use case cannot tolerate loss, and recognizing those cases takes less time than undoing them.

• Line art, screenshots and text: the sharp-edge territory where PNG is simultaneously smaller and cleaner. Converting a 260 KB screenshot to a 480 KB JPG buys nothing except ringing around every glyph.
• Anything needing transparency: logos, cutouts, overlays. The alpha channel does not survive the trip, and the flattened result cannot be un-flattened later.
• Images destined for more editing: every additional JPEG pass spends fidelity again. Masters stay lossless; exports happen once, at the end.
• Documents where loss is prohibited or inadvisable — scans with fine print, archival records, anything a regulator or a lawyer might someday squint at. JPEG's plausible-looking approximation is exactly the property you do not want under scrutiny.
• Palette-limited graphics with few colors, where indexed PNG often beats JPEG at both size and fidelity by a mile.

Notice what every item shares: a reason rooted in what the image is, not in habit. The most expensive conversions are the ones done because JPG is what the last person in the chain asked for. If the destination genuinely requires JPG — and marketplaces, email and most web contexts do — the rest of this page is about doing it right.

The tool is above this section. The standard run for the Thursday-afternoon crowd:

1. 1

   Drop your PNGs

   One file or fifty — drag them onto the zone or click to browse. Each gets a row showing dimensions, original size and a progress bar that fills as it converts.

2. 2

   Set the background color

   Pure white is the default because marketplaces require it — hex #FFFFFF, the exact shade Amazon's guidelines specify for main listing images. Any color is available for non-marketplace work, and fully opaque PNGs ignore the setting entirely.

3. 3

   Choose a quality level

   The slider runs the full range with live guidance: 0.85 marked as the everyday default, 0.9 and up for masters, 0.75 and below for thumbnails. The estimated output size updates as you move it.

4. 4

   Convert

   One click starts the queue. Files process sequentially — decode, flatten, encode — with per-file timing shown, so a 50-image batch is predictable rather than a frozen tab and a prayer.

5. 5

   Download

   Take files individually or all at once. Filenames carry over with the extension changed, and no watermark appears on anything, ever.

For listings that also need exact pixel dimensions — the 1000-pixel minimum for zoom on Amazon, the 2000-pixel width Etsy recommends — resize first, then convert: the Image Resizer handles dimensions, and this tool handles format and weight.

The slider feeds a single number to the JPEG encoder, and that number's real job surprises people: it scales the quantization tables. In the reference encoder from the Independent JPEG Group, quality 50 leaves the standard tables untouched; above 50, the divisors shrink toward 1; below 50, they grow. Quality is not a percentage of information kept — it is a dial on how hard each frequency coefficient gets rounded toward zero.

That non-linearity explains the file-size curve, which is the part worth internalizing. Bytes saved per notch of quality are roughly constant in percentage terms — each meaningful step down buys about a third off the file — while the visual cost accelerates: nothing visible from 0.9 to 0.8, a trained eye notices 0.7, everyone sees 0.5. Spending quality is cheap at the top of the range and expensive at the bottom, so the slider's default sits where the exchange rate is still favorable.

Read the middle rows as the working range. The step from 0.85 to 0.75 removes another 32 percent of the bytes for a difference most viewers will never find, which is why galleries and thumbnails live there. The step from 0.75 to 0.60 removes 36 percent more and starts spending fidelity you can see — the point where the exchange rate turns against you.

Transparency cannot survive this conversion — JPEG has no alpha channel — so the converter composites every image onto a solid background before encoding. The operation is one line of canvas work conceptually: fill the destination with the background color, then draw the PNG on top, letting the browser's alpha blending resolve every semi-transparent pixel against that fill. Pure white, RGB 255-255-255, is the default because it is a documented marketplace requirement, not an aesthetic preference.

The subtlety lives in the edge pixels. A well-cut product PNG has a one-or-two-pixel halo of partial transparency around the subject — anti-aliasing that made the cutout look smooth on any background. Flattened onto white, that halo blends into exactly the shade of near-white it needs to, and the result is the clean floating-on-white product shot listings want. Flattened onto a colored background chosen carelessly, the same halo shows as a faint ghost of the old cutout. The rule: flatten onto the destination color, not a convenient one.

If your source photos still have their original busy backgrounds, this tool is step two, not step one. Cut the subject out first with the Background Remover, export the cutout as PNG, then flatten here onto pure white — a two-step pipeline that produces the marketplace-ready main image in under a minute per product.

The batch engine is built on the browser's File API, and its design constraint is memory: a 4000-pixel PNG decodes to roughly 48 megabytes of raw pixel data, and converting 47 of them at once would demand well over two gigabytes of tab memory. Instead, the queue processes one file at a time — decode, convert, hand off the result, release — so memory stays flat no matter how long the queue is.

Downloads avoid a second copy in memory by generating object URLs — short-lived browser: references to the encoded blobs — and revoking them the moment each download completes. It is housekeeping nobody notices until a 100-file batch finishes without the tab collapsing, which is precisely the point. Progress reporting is per-file and honest: the bar reflects decode and encode time for the current image, not a synthetic animation.

Camera JPEGs arrive carrying EXIF — exposure settings, timestamps, and on phones the GPS coordinates of the shot. PNGs almost never do: the format's spec gained an optional eXIf chunk only in 2017, and real-world PNGs from editors and cameras overwhelmingly skip it. Whichever way the source leans, the JPG this tool writes contains image data and nothing else, because a canvas re-encode has no mechanism for carrying metadata forward.

For sellers that is a compliance convenience; for anyone publishing images taken at home it is a quiet privacy guarantee — there is no location tag to leak, because there is no tag. Orientation is a non-issue in this direction: PNG pixels are stored upright by convention, so the JPG comes out the same way the PNG went in. If you want to inspect any file's metadata before it travels, ExifTool — linked below — remains the reference instrument.

What the converter will and will not do, stated without marketing.

• Detail discarded by the quality setting is gone for good — there is no lossless JPG, and re-running at higher quality afterward does not recover what the first pass rounded away. Convert from the PNG master every time.
• 16-bit-per-channel PNGs are accepted and output as 8-bit JPEGs — the format's ceiling — with a note attached to the file row, since banding in deep gradients is the one case where that matters.
• Indexed-color PNGs convert normally; the palette is expanded during decode and re-quantized by the encoder like any other source.
• Extremely saturated wide-gamut sources (Display P3 screenshots, mainly) are normalized to sRGB by the browser pipeline, slightly compressing the outermost color range. Marketplace use is unaffected; print workflows should convert in a color-managed editor instead.
• Animated PNGs convert as their first frame, silently — if the file moves, it belongs in a video tool.
• The quality slider tops out at 0.95 rather than 1.0 on purpose: reference-quality 100 produces files larger than useful PNG territory with no practical gain, and that corner of the dial exists mainly to trap the conscientious.

E-commerce sellers are the design-center audience: whole product catalogs in PNG, whole listings in JPG, and a white-background rule in between. The flattening-plus-batch combination exists because that workflow is repetitive enough to deserve exactly one tool that does both halves correctly.

Bloggers and newsletter writers convert for weight — a 12-megabyte PNG in a post is a page-speed audit waiting to happen, and the same photo at quality 0.85 is a fraction of the load with no visible difference at article width. Email attachments are the same arithmetic against a 25-megabyte limit. Students and office workers round it out: presentation decks and LMS uploads that reject oversized files but never complain about quality 0.85.

Designers use it as the export step of the pipeline: work in PNG or the editor's native format, ship in JPG, keep the master. That discipline — one-way exports, never re-compressing the output — is the difference between a catalog that ages well and one that slowly acquires a patina of compression blocks.

One more group deserves a mention because they never email: web teams converting hero graphics and OG images down to payload budgets. A 2.4-megabyte social-card PNG that becomes a 320-kilobyte JPG at quality 0.82 loads before the user finishes blinking, and social platforms — which re-compress everything anyway — treat the smaller file more gently than the giant one. The same teams keep a pinned note of the quality number that passed their visual review, which is the most professional habit in this entire paragraph count.

Every desktop editor, several marketplaces and a hundred upload-based websites will convert PNG to JPG. The differences are trust and control.

The last row deserves its caveat repeated: platforms that auto-compress uploads do it after upload, with settings you never see, on files you already shipped at full weight. Converting locally first means the platform's recompression runs on a file already sized right — and usually skips it entirely.

Sourced from search queries and seller email, answered once each. The sections above hold the long versions.

Three tools share this converter's workflows most often, and the pairing order below matches how real sessions run.

• JPG to PNG Converter — the return trip, for masters, preservation and alpha support.
• HEIC to JPG Converter — iPhone originals translated to the format every marketplace accepts.
• Compress Image to Target KB — when the requirement is a hard size ceiling rather than a quality judgment, this one lands the file under it.

Everything above in one breath: a browser-based PNG to JPG converter with a quality slider whose numbers mean something, white-background flattening for marketplace compliance, batch handling that stays polite to your memory, and output files born without a byte of metadata. Keep the PNG masters, spend quality deliberately, and the 47-photo Thursday stops being a Thursday problem.