Will converting a PNG to JPG always make the file smaller?
Converting a PNG photograph to JPG almost always cuts file size dramatically, often by 60% to 85%, because lossy JPEG compression discards imperceptible color noise. However, flat-color UI screenshots containing sharp text and solid panels can compress smaller and look noticeably crisper in PNG.
If you later need an editable, lossless copy of a converted photo for repeated cropping or overlays, you can convert JPG files back to lossless PNG in one step.
Why camera photos shrink dramatically as JPG
When a phone or camera photo is exported as a lossless PNG, the encoder must record every tiny sensor grain variation verbatim, producing files that often reach 5 MB to 15 MB. As explained in the MDN Web Docs Image file type and format guide, JPEG applies lossy chroma subsampling and frequency quantization tailored specifically to continuous-tone photographs.
| Image type | PNG behavior | JPG behavior (0.90 High) |
Recommended format |
|---|---|---|---|
| Camera photo / portrait | Very large (3x–8x bigger) |
Compact, natural gradients | JPG |
| Transparent logo / icon | Preserves alpha channel | Flattens onto Background fill | PNG (unless flat card needed) |
| UI screenshot with text | Crisp 1-pixel edges | Faint halos around small text | PNG (or Maximum 0.97 JPG) |
| Product shot on white | Heavy file weight | Fast-loading marketplace file | JPG |
| Scanned document page | Large grayscale/color file | Compact attachment for email | JPG |
When flat UI screenshots stay sharper and smaller in PNG
Screenshot tools on macOS and Windows save captures as PNG by default because Deflate compression encodes long runs of identical background pixels efficiently. Re-encoding a flat-white code editor screenshot into lossy JPG can introduce faint compression halos around dark letters and occasionally produce a larger file at 0.97 quality.
Testing High (0.90) or Smaller file (0.75) in the browser lets you check the resulting byte count immediately before discarding your original PNG.
Handling transparent PNG backgrounds with Background fill
The JPEG standard has no alpha channel, so any transparent region in a PNG must be painted over a solid color before encoding. Setting Background fill explicitly prevents dark-on-transparent logos or stickers from turning unreadable against a default black canvas.
If your workflow also includes WebP assets downloaded from modern websites, you can convert WebP images into universal JPGs using the same background-fill controls.
Choosing White, Black, or a custom hex matte color
In the options panel, Background fill defaults to White (#ffffff), which matches standard documents, product listings, and light-mode web pages. Clicking Black (#000000) or picking any hex color from the custom color swatch fills the offscreen canvas before the PNG is drawn.
Preventing black artifacts on alpha-channel logos
Under the W3C Portable Network Graphics (PNG) Specification Third Edition, transparent pixels carry an alpha value of 0 alongside RGB values that are often zeroed out. Naive converters that strip the alpha byte without compositing leave behind solid black cutouts.
Drawing the decoded PNG onto a pre-filled HTML5 Canvas blends semi-transparent drop shadows and anti-aliased icon edges smoothly onto your chosen matte color. That guarantees clean edges with zero jagged black fringes.
Choosing Quality presets and HTML5 Canvas encoding limits
Two code-level mechanisms govern the final file weight and sharpness of your exported JPG: the Quality dropdown and browser canvas dimension bounds. Both run locally in browser memory without sending image bytes over the network.
If an online form enforces a strict kilobyte cap even after switching to Smaller file (0.75), you can shrink photos to exact kilobyte targets directly from the result panel.
Comparing Smaller file (0.75), High (0.90), and Maximum (0.97)
When you click Convert image to JPG, the encoder passes your selected quality factor to the MDN Web Docs HTMLCanvasElement toBlob API. High (0.90) is selected by default because it keeps photographic textures clean while cutting file weight substantially.
Smaller file (0.75) prioritizes email and web speed where slight softening is acceptable, while Maximum (0.97) preserves fine typography and subtle gradients when file size is secondary.
Canvas 4,096 px and 16.7-megapixel safety bounds
Before allocating the drawing surface, clampCanvasSize verifies that neither edge exceeds 4,096 px and total pixel area stays within 16,777,216 pixels. Images within those bounds convert at 100% of their original width and height.
Oversized screenshots or stitched panoramas exceeding 4,096 px scale down proportionally so mobile Safari and Chromium tabs never run out of graphics memory.
Batch exports, privacy, and next steps after conversion
Every PNG in your queue is decoded, composited onto your Background fill, and encoded to .jpg locally inside your browser tab. Single files download immediately as <name>.jpg, while multi-file batches bundle into a single ZIP archive.
If you are preparing photos for public sharing and want to verify or scrub hidden camera tags from other JPEG originals, open the browser EXIF and GPS metadata remover next.
Single JPG downloads vs multi-file ZIP archives
Converting one PNG renames the output extension from .png to .jpg and starts the download right away. Dropping 5, 20, or 50 PNGs at once runs them sequentially and packages all .jpg outputs into one ZIP download so your browser does not block multiple popups.
Tip: Use the Put in a PDF button in the completion panel right after batch-converting PNG screenshots into JPGs to combine them into a compact, email-ready PDF booklet without re-selecting files.
Zero-upload browser processing and metadata cleanup
Because createImageBitmap and HTMLCanvasElement.toBlob execute entirely on your device, confidential product mockups, tax screenshots, and personal photos never leave your computer. Re-encoding through canvas also strips any PNG text chunks (tEXt or iTXt) from the exported .jpg stream.