PNG to JPG: A Size Decision, Not a Compatibility Fix
Unlike converting HEIC or WebP files, where the problem is that nothing will open the file, PNG to JPG is a deliberate trade-off. PNG is lossless: it stores every pixel exactly as it was captured, which is why PNG files are large. JPG is lossy: it discards image data that the human eye doesn't notice, which is why JPG files are small. For photographs and photo-based images, this trade-off is almost always worth making. For graphics with transparency, text, logos, or flat colors, it usually isn't.
The single most important thing to know before converting: check whether your PNG has a transparent background. If it does and you convert to JPG, that transparency becomes white. If you need a compressed format that preserves transparency, use WebP instead. If your PNG is a photograph or image with a solid background, convert freely; the JPG will be 50–75% smaller with no visible quality loss.
What PNG Is and Why It Produces Large Files
PNG (Portable Network Graphics) was created in 1996 as a patent-free replacement for GIF. It uses DEFLATE compression, which is lossless: the compressed file contains all the original pixel data and decompresses back to the exact original image with zero degradation. This makes PNG the correct choice whenever quality accuracy matters absolutely, for logos, UI assets, screenshots, and design work where text and hard edges need to stay sharp.
The cost of lossless compression is file size. DEFLATE compression works by finding and encoding repeated patterns in the image data. It's very efficient for images with large flat-color areas and hard edges (logos, UI screenshots, diagrams). It's much less efficient for photographs, where every pixel is slightly different from its neighbors, giving the algorithm very little redundancy to exploit. A photograph as PNG can be 3–5x larger than the same image as JPG.
PNG Technical Specs:
- Compression: Lossless DEFLATE, no quality loss ever
- Transparency: Full alpha channel with 256 levels of opacity
- Color depth: Up to 48-bit (16 bits per channel), far exceeding screen display capability
- Best image types: Logos, icons, UI screenshots, text-heavy images, graphics with solid colors
- Worst image types: Photographs, natural textures, anything with photographic gradients
- Browser support: Universal across all browsers and platforms
What JPG Does to Your Image and When That's Fine
JPG uses DCT (Discrete Cosine Transform) compression, which works by breaking the image into 8x8 pixel blocks, converting each block into frequency components, and discarding the high-frequency details that human vision is least sensitive to. The lower you set the quality, the more frequency data gets discarded. At 85% quality, which is what this converter uses, the discarded data is genuinely invisible at normal screen viewing distances and at standard print resolutions up to about 11x14 inches.
The weakness of this algorithm is those 8x8 blocks. When an image has a sharp hard edge, like the border of a letter or a crisp line in a UI screenshot, the block-based compression creates ringing artifacts and halos. This is why JPG looks bad on screenshots and logos. For photographs, where edges are typically soft and colors blend gradually, the 8x8 block size is invisible.
JPG Technical Specs:
- Compression: Lossy DCT, quality adjustable 1–100%
- Transparency: Not supported; transparent areas become solid white
- Color depth: 24-bit (8 bits per channel, 16.7 million colors)
- Best image types: Photographs, portraits, landscapes, product photos, any image with smooth gradients
- Worst image types: Screenshots with text, logos, flat-color graphics, UI elements with sharp edges
- Browser support: Universal; the most supported image format that exists
When Converting PNG to JPG Is the Right Decision
Convert when your PNG contains photographic content and file size matters. Here are the specific situations where the conversion is clearly the right call:
- Your design tool exported a photo as PNG by default: Figma, Sketch, and Adobe XD often default to PNG for exports. If the exported image is a photograph or has a photographic background, switch it to JPG. The quality will be identical at display size and the file will be a fraction of the size.
- Your website has large PNG hero images or background photos: Hero images are almost always photographs. Serving them as PNG is one of the most common PageSpeed issues. A 6MB PNG hero that becomes a 1.2MB JPG saves over a second of load time on a typical connection.
- You need to email a photo but it's too large to attach: A full-resolution PNG photo from a DSLR or modern smartphone can be 12–24MB. Converting to JPG brings it to 2–4MB, well within standard email limits.
- You have a library of product photos saved as PNG: E-commerce product images are photographs. Storing and serving them as PNG inflates your storage costs and your page load times. JPG at 85% is the industry standard for e-commerce product imagery.
- You're uploading to a platform that imposes size limits: Many CMS platforms, social media upload forms, and client portals reject files over a certain size. Converting your PNG photographs to JPG before uploading resolves this without any visible quality compromise.
Do not convert to JPG if: your PNG has a transparent background; your PNG contains a logo or icon with flat colors and hard edges; your PNG is a screenshot with text or UI elements; or your PNG is an illustration with solid color areas. In these cases JPG will look worse, often significantly, and you won't gain much in file size either.
How the Conversion Works
PNG to JPG is the most straightforward conversion this tool performs. Both formats are fully supported by every browser natively, so no external decoder library is needed. The process uses the HTML5 Canvas API:
- File selection: You select one or multiple PNG files. They load into browser memory only, no network activity occurs.
- PNG decoding: The browser decodes the lossless PNG data into raw pixel values. Since PNG is lossless, this step produces a perfect, unmodified representation of the original image.
- Transparency handling: If the PNG has an alpha channel, transparent pixels are composited onto a white background before encoding. This is a permanent change; the transparency cannot be recovered from the JPG output.
- JPG encoding: The Canvas API re-encodes the pixel data as JPG at 85% quality. This is where the size reduction happens: the DCT algorithm discards high-frequency detail that's imperceptible in photographs.
- Download: The resulting JPG is offered as a download. Your original PNG remains untouched on your device.
Processing speed is fast: PNG to JPG typically completes in under one second per image on modern hardware because the browser already has native decoders for both formats built in.
Real File Size Reductions by Image Type
The size reduction you get depends heavily on what's in the image. Here are realistic figures across common PNG types, using 85% JPG quality:
- DSLR portrait photo (3024×4032): 12MB PNG → 2.8MB JPG, about 77% smaller
- Landscape/travel photo (5472×3648): 22MB PNG → 5.5MB JPG, about 75% smaller
- E-commerce product photo (2000×2000, white background): 4.5MB PNG → 1.1MB JPG, about 76% smaller
- Website hero image (1920×1080, photographic): 6MB PNG → 900KB JPG, about 85% smaller
- UI screenshot (1920×1080, mostly flat colors and text): 800KB PNG → 580KB JPG, only 28% smaller, and visibly worse quality
- Logo on transparent background (500×500): 45KB PNG → 60KB JPG with white background, actually larger and worse looking
The last two examples illustrate why image type matters. Screenshots and logos are poor candidates for PNG to JPG conversion. Photographs are excellent candidates. The 75–85% size reduction on photographic content is real and consistent.
Common PNG to JPG Problems and What's Causing Them
The image now has a white box or white background where it should be transparent
Your PNG had a transparent background. JPG does not support transparency, so every transparent or semi-transparent pixel was filled with white during encoding. This cannot be undone from the JPG file. If you need compression with transparency preserved, use the PNG to WebP converter instead. If you specifically need JPG, place the image on the correct background color in a design tool before converting.
Text in the image looks blurry or has a halo around it after converting
This is JPG's DCT compression creating ringing artifacts around high-contrast edges. When a sharp black letter sits on a white background, the 8x8 pixel blocks that JPG uses for compression can't accurately represent that hard edge without visible distortion. This is not a bug; it's a fundamental characteristic of the JPEG compression algorithm. If your PNG contains text, UI elements, or anything with sharp geometric edges, keep it as PNG.
The JPG file is barely smaller than the original PNG
This happens when the PNG contains mostly flat colors, solid backgrounds, or geometric shapes. PNG's lossless DEFLATE compression is very efficient at encoding these image types because it can represent large areas of identical pixels compactly. A logo with solid color fills might be 45KB as PNG and 55KB as JPG. In these cases, the conversion is pointless and the JPG will look worse. The big size wins from PNG to JPG only happen with photographic content.
The colors look slightly different after converting
PNG supports up to 48-bit color depth. JPG is limited to 24-bit (8 bits per channel). If your PNG was a 16-bit-per-channel design file with very fine color gradations, converting to JPG clips those extra color values to the 8-bit range. For standard photographs and most design work this is invisible, since screens display 8-bit color and the human eye cannot perceive the difference at this precision level. It only becomes relevant in color-critical professional print workflows.
Quality Settings Explained
Our converter uses an 85% quality setting, which represents the professional sweet spot recommended by photographers and web developers. This quality level is suitable for:
- Website hero images and featured photography
- Social media posts on all platforms (Instagram, Facebook, Twitter, LinkedIn)
- Professional printing up to 11x14 inches at 300 DPI
- Email newsletters and marketing materials
- Online portfolios and photography galleries
- E-commerce product images
Batch Converting PNG Files
Select multiple PNG files at once using Shift+click for a range or Ctrl/Cmd+click for individual selections. All files are processed in sequence and can be downloaded individually or as a ZIP archive.
A practical note for web and design workflows: if you're converting a folder of exported design assets, check each file type before batch converting everything. A folder exported from Figma or Sketch might contain a mix of photographs (good candidates for JPG), UI screenshots (keep PNG), and logos or icons (keep PNG). Batch converting without filtering will degrade your logo and UI assets while correctly optimizing your photos. Sort by image content first, then batch convert only the photographic files.
Your Files Stay on Your Device
PNG files from design tools frequently contain unreleased product mockups, client work in progress, proprietary UI designs, and confidential brand assets. Uploading these to a web service for conversion is a real security consideration, particularly for agencies and freelancers working under NDAs.
This converter has no server component for file processing. Both PNG and JPG are natively supported by browsers, so the entire operation, reading the PNG, converting it on a Canvas, encoding it as JPG, runs locally. Nothing is transmitted. You can verify this by opening your browser's network tab in developer tools while converting: no outbound requests will appear for your image data.
- No uploads: Your PNG files never leave your device
- No storage: We cannot store your files because we never receive them
- No accounts: No sign-up, no email, no personal information required
- Verifiable: Check your browser's network activity during conversion; you will see no file upload requests
- Works offline: After the page loads, internet connection is not required for conversion
- No watermarks: Output files are clean JPGs with nothing added
Why No-Upload Conversion Is Different: What Actually Happens in Your Browser
PNG to JPG is one of the most common image conversions on the web, which means there are hundreds of tools that handle it. Most upload your file to a server. Here is the precise technical difference between that approach and what this converter does, including what is specific to PNG files that makes local processing worth understanding.
What the browser does with your PNG, step by step
When you select a PNG file, the browser hands JavaScript a File object: a sandboxed reference that exposes the file's bytes but never its filesystem path or directory context. The converter passes this to the browser's native image decoder via an HTMLImageElement or createImageBitmap() call. Because PNG is natively supported by every browser, no external library is needed. The browser's internal PNG decoder reads the IHDR chunk (image dimensions, bit depth, color type), decompresses the IDAT chunks using DEFLATE, reconstructs the full pixel grid in memory, and applies any PNG filter transformations to recover the original pixel values. This decoded pixel data lands on an HTMLCanvasElement. The canvas then calls toBlob('image/jpeg', null, 0.85), passing the raw pixel array to the browser's JPEG encoder. The encoder applies DCT compression at 85% quality and returns a Blob containing the completed JPEG file. URL.createObjectURL() creates a temporary in-memory download reference. When you close the tab, the browser garbage-collects the ArrayBuffer, the canvas pixel data, and the Blob. Nothing persists.
What a PNG file actually contains that you may not have considered
PNG uses a chunk-based structure. Beyond the compressed pixel data in IDAT chunks, a PNG file can carry a significant amount of metadata in ancillary chunks. The tEXt and iTXt chunks store plain-text and UTF-8 key-value pairs that commonly include the software used to create the file (e.g., "Adobe Photoshop CC 2024," "Figma," "Sketch 99"), the author or copyright holder, creation and modification timestamps, and in some tools, internal project or document identifiers. The zTXt chunk stores the same data in compressed form. The iCCP chunk embeds a full ICC color profile, which can be several kilobytes and identifies the color space the file was authored in. The eXIf chunk can carry standard EXIF data including GPS coordinates if the PNG came from a camera or mobile device export.
For design professionals, this metadata can expose details they may not intend to share: the software and version used, internal naming conventions embedded by export scripts, or copyright strings embedded by their tools. When you upload a PNG to a server-side converter, that metadata travels with the file. When this converter processes the PNG locally, the Canvas API reads only the pixel values during decoding. It does not parse or forward ancillary chunks. The JPEG output contains no tEXt metadata, no software identification, no color profile chunk, and no embedded EXIF. The output is pixel data only.
The ICC color profile trade-off
There is one technical consequence worth being transparent about. The Canvas API composites and outputs pixel data in the sRGB color space. If your PNG was authored in a wide-gamut color space such as Display P3, Adobe RGB, or ProPhoto RGB and carries an embedded ICC profile, the Canvas API will perform color space conversion to sRGB during decoding. The JPEG output will be in sRGB with no embedded profile. For most web and sharing use cases this is invisible. For color-critical print work or professional photography where wide-gamut color accuracy matters, this is a real difference: a server-side tool using ImageMagick or libvips with -profile flags can honor and preserve the original ICC profile during conversion. If you are converting professional photography or design assets where color profile accuracy is a requirement, a desktop tool like Adobe Photoshop or GIMP with color management enabled will give you a more faithful result than any browser-based converter.
What server-side PNG converters actually do
The typical server-side PNG to JPG pipeline receives your file as a multipart form upload, writes it to temporary storage, and passes it to a library like Sharp (Node.js), Pillow (Python), libvips, or ImageMagick on a remote server. These are well-built tools that handle color profiles, metadata preservation, and edge cases well, which is their genuine advantage over browser-based conversion. The trade-off is the upload itself: your PNG, including its pixel data and all metadata chunks, leaves your machine and lives on someone else's infrastructure for the duration of processing, and for however long their data retention policy keeps temporary files. For a photo of your lunch, this is irrelevant. For an unreleased product mockup, a client deliverable under NDA, or a design file containing internal asset naming conventions, it is worth considering.
You can verify this converter's behavior in about 30 seconds. Open developer tools in your browser, click the Network tab, and filter for requests. Select your PNG file for conversion and watch. No outbound request carrying your image data will appear. The only network activity you will see is the initial page load of static assets. The conversion lives entirely inside your browser process, which is the only claim worth making and the only one you can actually verify.
Frequently Asked Questions
Does converting PNG to JPG lose quality?
For photographs, the quality loss at 85% JPG is genuinely imperceptible at screen viewing sizes and for printing up to about 11×14 inches. For graphics with text, logos, or hard edges, the quality loss is visible as ringing artifacts and blurriness. The answer depends entirely on what's in the image. Photographs: convert freely. Logos, UI screenshots, and graphics with text: don't convert.
Why does Facebook compress my PNG photos when I upload them anyway?
Facebook, Instagram, Twitter, and most social platforms automatically re-compress uploaded images regardless of format. When you upload a PNG, they convert it to JPEG on their servers using compression settings you have no control over. Converting to JPG yourself at 85% quality before uploading gives you a higher-quality starting point than letting their automated system do it, and you avoid the double-compression artifact accumulation that happens when their system re-encodes an already-uploaded PNG.
Is there a file size limit for conversion?
No limit from the tool. The only constraint is your device's available RAM. PNG to JPG is a native browser operation and is very fast, so even large PNG files (50–100MB) process quickly on modern hardware. Very large files on older devices with less RAM may cause the browser tab to slow down; if that happens, close other tabs and try again.
My website's PageSpeed score is poor because of images. Will converting PNGs to JPG help?
Yes, significantly, if your slow images are photographs saved as PNG. Google's PageSpeed Insights and Lighthouse flag oversized images as one of the most impactful performance issues. Converting a 6MB PNG hero image to a 900KB JPG directly improves your Largest Contentful Paint (LCP) score, which is one of Google's Core Web Vitals. For even better results, after converting to JPG, consider serving WebP versions for browsers that support it with JPG as the fallback.
I exported from Figma and got a PNG. Should I convert it?
It depends on what you exported. Figma defaults to PNG for all exports, which is a safe choice because PNG handles everything correctly. If you exported a photographic image or a design with a solid non-transparent background, converting to JPG will reduce file size significantly. If you exported a logo, icon, UI component, or anything with transparency or text, keep the PNG. A better long-term solution is to set the export format in Figma directly: select your frame, go to Export, and change PNG to JPG for photographic exports.
Can I use the converted JPG files commercially?
Converting a file changes its format, not its ownership. The copyright and usage rights belong to whoever owns the original image. We add no watermarks, claim no rights, and impose no restrictions on output files. The converted JPGs are standard files you can use however the original PNG's license permits.
Related Image Converters
Visit our complete converter directory for all 25+ image format combinations.