When PNG is the wrong container
PNG is excellent for icons, UI, and anything with a hole in the background. It is a poor default for photographs. Lossless encoding keeps every speck of sensor noise, so a casual 12-megapixel PNG can weigh 20 MB. Email servers bounce it, WhatsApp recompresses it into something uglier than a controlled JPEG would have been, and many government or college portals still list “JPG only” in the upload hint. Converting PNG to JPG is the practical fix: you accept a little softness in exchange for a file that actually sends.
The other reason is transparency you no longer need. A cutout PNG sitting on a white landing page does not need an alpha channel once it is baked into a rectangular photo. JPEG cannot store transparency. ToolPin flattens those pixels—typically onto white—so the subject does not pick up a checkerboard or a black halo. If the PNG was meant to float over a colored banner, flatten it in a design tool onto that color first, then convert. Otherwise you will see a hard white box.
Quality versus size
JPEG quality is a dial, not a promise. Around 75–85 looks fine for most phone photos and marketplace listings. Dropping lower saves more kilobytes and starts to show banding in skies and blotches around small type. Screenshots of text suffer more than landscapes; if the PNG is a UI capture you still need to read, consider staying on PNG or using WebP instead of forcing JPEG.
You also cannot undo a flatten. Once alpha is gone, you cannot recover the cutout from the JPG. Keep the original PNG if you might need the isolated subject again. Think of JPEG as the distribution copy and PNG as the working copy.
Color is another quiet change. PNG is usually sRGB or untagged. JPEG from a browser canvas is sRGB. Wide-gamut PNGs from some cameras or design apps may look slightly less vivid after conversion. For web and WhatsApp that is almost never a problem. For a color-critical print job, ask the shop whether they want TIFF or a JPEG with a profile, and do not rely on a browser flatten for proofing.
Privacy, limits, and what the browser does
Everything runs in the tab. The PNG is decoded, drawn to a canvas, and encoded as JPEG on your machine. ToolPin does not receive the pixels. That is useful when the PNG is a passport scan, a medical form, or a screenshot of a dashboard. Files can be up to 250 MB. Animated APNG is not a target here—you get a still frame. Indexed PNGs and 16-bit PNGs are reduced to standard 8-bit RGB as part of canvas encoding.
There is no watermark and no login. If the output is still too heavy for a 2 MB portal, run Compress JPG on the result or resize the image so the pixel count matches how it will be displayed. A 4000-pixel-wide JPEG of a passport photo is wasted data.
Choose the right exit format
Use JPG when the destination is photo-centric: cameras, labs, many CRMs, older Word documents, and almost every “upload a photo of your ID” form. Use WebP if you control a website and want smaller files with similar quality. Keep PNG when you still need transparency or razor-sharp UI chrome. And if the PNG is already a tiny icon, converting to JPEG will often make it larger and fuzzier—JPEG’s overhead is a bad match for simple graphics.