How to Convert Product Images Between PNG, JPG & WEBP (Free, In-Browser, No Photoshop)

Converting a product photo is the job sellers hit the moment a marketplace rejects a PNG for the main image, a Shopify theme will not render a WebP, or an ad platform demands JPG and the file is sitting there as a transparent PNG. The part that trips sellers up is the assumption that converting means re-saving, or that "convert" and "resize" or "compress" are the same operation. They are not — resizing changes the pixel dimensions, compressing changes the byte size, and converting changes the encoding format the file is stored in. A photo that is already the right dimensions and the right byte size can still be rejected because it is the wrong format for the placement. This is the step-by-step method I run, from reading which format each placement actually accepts through to a batched export where transparency lands on white instead of black.

The goal is a file in the encoding the placement reads natively — the product keeps its pixels and its bytes, the transparency is handled so a cut-out does not get a black box around it, and the format matches what the marketplace, the storefront theme, and the ad platform each expect. Get the conversion right once and the same master photo feeds the Amazon main as JPG, the Shopify hero as WebP, and the email creative as a small JPG without a re-shoot per placement.

Step 1 — Read which format each placement accepts

The single biggest factor in a clean conversion is not the tool — it is knowing what format you are converting to, per placement. Every marketplace, storefront, and ad platform reads a different set of encodings, and uploading a format the placement does not accept is the most common reason a listing image is rejected or silently re-encoded into something with a black halo around the product.

• Amazon, eBay, Walmart, Etsy, TikTok Shop, Pinterest, Google Shopping, Shopify each accept a different mix of JPG, PNG, and WebP, and several reject WebP entirely on the main image even when they allow it on secondary slots. The exact per-platform rules live in the image-requirements guides — Amazon, eBay, Walmart, Shopify, Instagram — and the image resizer presets their dimension minimums so you are not reformatting per upload.
• Match the format to the slot, not to a single house style. A marketplace main that demands JPG, a storefront theme that rewards WebP, and an ad creative that demands JPG are three different conversion targets off the same source photo. Convert per placement, not once for the whole catalog.
• Separate the format decision from the byte decision. Converting PNG to JPG drops the byte size as a side effect, but that is not the goal of a conversion — compressing is the operation that targets bytes. Convert to match the encoding the placement reads; compress separately if the resulting file is still too heavy.

Step 2 — Open the free in-browser converter

Use the image format converter. It runs entirely in the browser on the canvas API — no upload to a server, no signup, no watermark on the output — so a catalog of product photos never leaves the seller's machine. That matters for two reasons: a marketplace main is commercial inventory you do not want parked on a stranger's server, and a batch of fifty SKUs converts in seconds locally instead of uploading and re-downloading per file.

• Drop the source files in. The converter accepts PNG, JPG, and WebP as input and converts in any direction — PNG to JPG, JPG to WebP, WebP to JPG, PNG to WebP. Drag a batch in; it queues them.
• Pick the target format per batch. Set the output to JPG for marketplace mains, WebP for storefront heroes, or back to PNG when you need to keep transparency for a composite.
• Set the transparency handling before you export. This is the setting that decides whether a cut-out product lands on white or on black, and it is the step most sellers skip — covered next.

Step 3 — Handle transparency so cut-outs land on white

This is the step that ruins more conversions than any other. A product photo cut out from its background is a PNG with transparency — the pixels around the product are empty, not white. When you convert that PNG to JPG, JPG has no transparency channel, so the empty pixels get filled with a default color. In most converters that default is black, and the product lands in a black box. The marketplace then rejects it for a non-white background, or the listing goes live with a black halo around the product.

• Set the matte to white (#FFFFFF) before converting PNG to JPG. The converter flattens the transparent pixels onto the matte color you choose. White is what Amazon, eBay, Walmart, and Google Shopping demand on the main image — removing the background to transparency and then matting to white on conversion is the standard path to a compliant main image.
• Matte to a brand color only for social and ads. A Pinterest pin or an Instagram ad can sit on a colored backdrop; matte to the brand color there. But the marketplace main stays white — do not carry a colored matte onto the listing.
• Keep the PNG when transparency is the point. If the photo is going onto a composite, a collage, or a storefront theme that overlays the product onto a scene, do not convert it to JPG at all — keep the PNG and its transparency, and flatten only at final placement. Converting away from transparency and then needing it back is a one-way loss.

Step 4 — Pick the conversion direction per use case

The direction of the conversion is not interchangeable. Each direction solves a different problem, and picking the wrong one is how a seller ends up with a soft main image or a storefront that will not render.

• PNG → JPG for marketplace mains. JPG is the encoding every marketplace accepts on the main image, and it is the smallest file at photographic quality. Use this when the photo is already on a white sweep and transparency is not needed. Matte to white if any transparent pixels remain.
• JPG → WebP for storefront heroes. WebP is roughly 30% smaller than JPG at the same visual quality, which keeps the Shopify product page fast. Use this when the storefront theme renders WebP — most modern themes do, and the Shopify image guide notes which slots accept it.
• WebP → JPG for ad platforms and older marketplaces. Several ad platforms and a handful of marketplaces still do not render WebP on the main image. Convert back to JPG when a WebP is rejected on upload — the pixels and bytes are preserved, only the encoding changes.
• PNG → WebP for transparency at small byte size. WebP supports a transparency channel like PNG but at a fraction of the bytes. Use this when you need transparency (a product composited onto a scene) and the placement reads WebP — you keep the cut-out and drop the bytes together.

Step 5 — Batch convert per placement

Convert the master once per placement, not once for the whole catalog. A marketplace main as JPG, a storefront hero as WebP, and an ad creative as JPG are three different conversion targets off the same source photo — do not export one file and force it into all three.

• Queue the marketplace mains as a PNG → JPG batch, matted to white. This is the file that clears the listing's image-requirements gate on the first upload. White matte, JPG output, photographic quality.
• Queue the storefront heroes as a JPG → WebP batch. This is the file that keeps the product page fast. Same pixels, smaller bytes, modern encoding the theme renders.
• Queue the ad creatives as a WebP → JPG or PNG → JPG batch, matted to the brand color. This is the file the ad platform accepts and that sits on the colored backdrop the ad creative expects.

Keep the converted masters in a per-placement folder so the marketplace main, the storefront hero, and the ad creative each have a single canonical file in the encoding its placement reads. Re-uploading is the moment sellers discover they converted to the wrong format for a slot — a WebP main does not belong on a marketplace that rejects WebP, and a JPG with a black matte does not belong on the main image at all.

Step 6 — Verify the format, the transparency, and the color

After the export, open the converted file next to the original and check three things. Conversion defects are quieter than compression artifacts — they show up as a black halo, a color shift, or a file the platform still rejects.

• Confirm the encoding actually changed. Open the file info — the format should read JPG, WebP, or PNG as the target, not the source. A conversion that wrote the wrong encoding is usually a settings panel that defaulted back to the input format.
• Check the matte on a transparent cut-out. Pan to the edges of the product — the area that was transparent should now be solid white (or the brand color), not black, not checkered. A black halo here is the sign the matte was left at its default.
• Check for a color shift. PNG and WebP handle color profiles differently from JPG; a conversion that drops the color profile shifts reds slightly. Compare the product's dominant color to the original — if it matches, the conversion is clean; if it shifted, enable color-profile preservation in the converter and re-export.

A converted file that reads in the target encoding, has its transparency matted to white, and matches the original's color is the goal. If the matte is black, re-run with white; if the color shifted, preserve the profile; if the platform still rejects it, the format is right but the dimensions or byte size is the actual blocker.

When the free method is not enough

In-browser conversion handles a single photo or a small catalog batch cleanly. It struggles when the volume crosses into hundreds of SKUs across a dozen placements, or when the same master has to ship as JPG, WebP, and PNG in a single pass with per-placement matte colors.

• Hundreds of SKUs across placements — the same format-direction-matte decision repeated per product, where a batch pipeline that reads the placement targets and exports all three encodings in one pass is faster than clicking through a tool per image.
• Per-placement matte at scale — when the marketplace main needs white, the ad creative needs the brand color, and the social post needs a scene backdrop, all off the same cut-out, a managed pipeline flattens the same transparent master onto each matte in a single run.

These are the edge cases where a managed pipeline earns its keep — one that reads the placement targets, exports the JPG main, the WebP hero, and the PNG cut-out in a single pass, and restages the same master onto the studio and lifestyle backdrops the listing actually rewards. For the rest of a catalog — a product per upload, a handful of placements — the free in-browser method is faster, private, and good enough that the buyer cannot tell the converted main from the original.

The convert-once, place-many payoff

The point of converting cleanly is that you only do it once per placement. One master photo becomes the JPG marketplace main, the WebP storefront hero, and the JPG ad creative — each a different encoding and a different matte off the same source photo. ShotKit takes that one master and restages it onto the studio, marble, and lifestyle backdrops a marketplace listing actually rewards, so a single capture feeds the main image, the secondary set, and the ad creative without a re-shoot or a re-convert per placement. Convert once, place many times — that is the entire leverage of getting the format direction right.