Why You Are Here: Four Real Problems
Most people arrive at an image converter because something broke. The file will not open, the email bounced, the background came out wrong, or the upload was rejected. Before diving into format theory, here are the four situations that send the most users to a converter:
- iPhone HEIC files will not open on Windows. You took photos on your iPhone, transferred them to a Windows PC, and every image shows as an unrecognized file type. This is a codec licensing issue, not a corrupted file. The fix is converting to JPG or PNG.
- Downloaded WebP images that nothing will open. You saved an image from a website and now it sits on your desktop with a question-mark icon. Most desktop apps, older Photoshop versions, and email clients do not support WebP. Convert to PNG for universal compatibility.
- File too large for email. Your photo is 8MB and the email system caps attachments at 5MB. Converting a PNG or TIFF photograph to JPG at quality 85 typically reduces size by 80 to 90 percent and gets you under any reasonable limit.
- Logo needs a transparent background. You have a JPG logo but the white background shows up on colored slides and websites. JPG cannot store transparency. Convert to PNG, then remove the background in an editor. The converted PNG will support a fully transparent layer.
Format Decision Tree: Pick the Right Format in Four Questions
Use this decision path before converting. Picking the wrong format is how you end up with a 2.5MB file when you needed 250KB, or a broken image in an email.
Question 1: Is this a photograph or a graphic?
Photographs (camera shots, screenshots with gradients, realistic illustrations) compress well with lossy formats like JPG or WebP. Graphics with flat colors, text, or hard edges (logos, diagrams, icons, screenshots of UIs) compress better losslessly as PNG or SVG.
Question 2: Does it need a transparent background?
If yes, your options are: PNG (works everywhere), WebP (web-only, not supported in email), SVG (vector only, not for photographs), or GIF (binary transparency with jagged edges -- avoid for logos). JPG cannot store transparency under any circumstances.
Question 3: Where will this image be used?
- Web browser: WebP for modern browsers, JPG as fallback. AVIF for modern web stacks.
- Email attachment or embedded in email: JPG or PNG only. Email clients, including Gmail, Outlook, and Apple Mail, do not render WebP. Sending a WebP in email produces a broken image icon for many recipients.
- Professional print: TIFF with CMYK color space at 300 DPI minimum. Web images at 72 DPI will print blurry and pixelated at any reasonable size.
- Long-term archive: PNG or TIFF. Both are lossless. PNG is better for digital storage. TIFF is better when print shops or publishers are involved.
- Social media (Instagram, Facebook): JPG. Both platforms re-compress uploads anyway, so there is no benefit to uploading PNG for photographs.
Question 4: Is compatibility or file size more important?
If compatibility is the priority (sharing across unknown devices, email, legacy software), use JPG for photographs and PNG for graphics. If file size is the priority and you control the rendering environment (your own website), use WebP or AVIF.
Real File Size Numbers: PNG vs JPG vs WebP vs AVIF
Format marketing often glosses over actual numbers. Here are measured file sizes for a typical 1920x1080 photograph:
| Format | Settings | File Size | Quality |
|---|---|---|---|
| PNG | Lossless | ~2.5 MB | Perfect, no loss |
| JPG | Quality 85 | ~250 KB | Excellent, barely perceptible loss |
| JPG | Quality 60 | ~120 KB | Good, visible artifacts on close inspection |
| WebP | Lossy default | ~180 KB | Excellent, slightly better than JPG at same size |
| AVIF | Default | ~130 KB | Excellent, best compression at equivalent quality |
The JPG-to-PNG Quality Myth
This is one of the most common misconceptions in image conversion: converting a JPG to PNG does NOT improve image quality. It never has and it never will.
Here is why. When a camera or app saves a JPG, it permanently discards image data to achieve compression. That data is gone. Converting the JPG to PNG simply takes the already-degraded pixel data and stores it losslessly. You get a file that is 10 times larger, but the image is still the same degraded JPG. PNG cannot reconstruct data that JPG threw away.
The only reason to convert JPG to PNG is if you need to: (1) add a transparent background, (2) do further editing without accumulating additional JPG compression artifacts on each save, or (3) archive an image you plan to edit repeatedly. For pure viewing or sharing, JPG to PNG is always a size increase with zero quality gain.
HEIC: The Complete Story
HEIC causes more confusion than any other image format, and the confusion is completely justified. Here is everything you need to know.
Why Apple created HEIC
Apple switched iPhones to HEIC (High Efficiency Image Container) in 2017 with iOS 11. The reason was storage. HEIC uses the HEVC video codec for still images and achieves roughly half the file size of JPG at the same visual quality. A photo that takes 4MB as JPG takes roughly 2MB as HEIC. At 12 megapixels and 48 megapixels on modern iPhones, this matters significantly for storage.
Why Windows rejects HEIC files
Windows does not natively decode HEIC because HEVC (the underlying codec) requires patent licensing fees. Microsoft chose not to bundle the HEVC codec with Windows. The result: you transfer iPhone photos to a Windows machine and every .heic file appears as an unrecognized format with no preview.
Microsoft does sell a HEVC Video Extensions pack in the Microsoft Store for $0.99, which adds HEIC support. But most users do not know it exists, which is why HEIC-to-JPG conversion is the single most common image conversion request on the internet.
The iPhone Settings fix
If you regularly transfer photos to Windows or non-Apple devices, there is a permanent fix that does not require any conversion tool. On your iPhone, go to: Settings > Camera > Formats. You will see two options:
- High Efficiency: Saves photos as HEIC on the device (best for storage).
- Most Compatible: Saves photos directly as JPG. No conversion needed, ever.
There is also an "Automatic" behavior when using a USB cable to transfer to a Mac or PC: when you plug in via cable and import through Windows Photos or macOS Image Capture, iOS can automatically convert HEIC to JPG during the transfer. However, this only works with cable transfers and specific import tools -- AirDrop, iCloud, and direct file copy do not trigger the automatic conversion.
If you only occasionally need Windows-compatible copies, a converter is faster than changing the camera setting. If you are consistently frustrated by HEIC, change the camera format to Most Compatible and be done with it.
Converting HEIC files
Use the HEIC converter to convert individual HEIC files to JPG or PNG. JPG is the right choice for sharing and compatibility. PNG is the right choice if you need lossless quality for further editing.
Web, Print, Email, and Transparency: What Actually Works Where
Web delivery
For web images delivered in a browser, WebP is the current best practice. All major browsers (Chrome, Firefox, Safari, Edge) have supported WebP since 2022. WebP lossless is smaller than PNG, and WebP lossy is smaller than JPG at equivalent quality. A proper web stack uses WebP with a JPG fallback for older browsers.
AVIF offers even better compression than WebP but encodes roughly 47 times slower. For a static site where you encode images once and serve them many times, AVIF is excellent. For any pipeline that generates images dynamically or in real time, the encoding overhead makes AVIF impractical.
Email is NOT the web
This distinction causes constant problems. Email clients are not browsers. Gmail, Outlook (especially desktop versions), and Apple Mail have their own image rendering engines that are years behind browser standards. WebP is not supported in most email clients as of 2026. If you embed a WebP image in an HTML email, a significant portion of recipients will see a broken image placeholder.
For email, use JPG for photographs and PNG for graphics or anything requiring transparency. These two formats have had universal email client support for over two decades.
Professional print
Print is an entirely different world from screen. Key requirements:
- Resolution: Web images are typically 72 DPI (dots per inch). Professional printing requires 300 DPI minimum. An image that looks sharp on screen may print as a blurry, pixelated mess. Before sending an image to a print shop, confirm its resolution in pixels and divide by 300 to get the maximum print size in inches without quality loss.
- Color space: Screens use RGB (red, green, blue additive light). Printers use CMYK (cyan, magenta, yellow, black subtractive ink). If you send an RGB file to a commercial printer, they will convert it to CMYK, and colors can shift significantly. Dark blues often become muddy purple. Vibrant oranges may go flat. For professional print work, confirm that your TIFF or EPS file is in CMYK color space before delivery.
- Format: TIFF is the standard for print. It supports CMYK color space, lossless compression, and high bit depth. JPEG is acceptable for some print uses but is lossy and does not support CMYK natively. PNG is RGB-only and not standard in professional print workflows.
Transparency
Not all transparency is the same. Here is what each format actually provides:
- PNG: Full alpha channel transparency. Each pixel can be any opacity from fully transparent to fully opaque, including semi-transparent. This is the standard for web graphics, logos, and UI assets. Works in virtually every application and platform.
- WebP: Supports full alpha transparency and produces smaller files than PNG for web use. The limitation is compatibility: WebP transparency works in browsers but not in most desktop applications, not in email clients, and not in older design tools.
- SVG: Vector format that supports transparency natively. Ideal for logos and icons because it scales to any size without pixelation. Cannot meaningfully represent photographs. SVG is code (XML), not pixels, so you cannot convert a photograph to SVG and expect it to look like a vector illustration.
- GIF: Binary transparency only -- each pixel is either fully transparent or fully opaque, nothing in between. This produces jagged edges on anything with an anti-aliased (smooth) edge. GIF transparency is acceptable for simple pixel-art style graphics but looks amateurish for logos or photographs. Avoid GIF for transparency work.
Platform Compatibility Matrix
Before converting, check whether your target platform supports the format natively:
| Format | Windows | macOS | iOS | Android | Email Clients | ||
|---|---|---|---|---|---|---|---|
| JPG | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| PNG | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| GIF | Yes | Yes | Yes | Yes | Yes | No animation | Yes |
| WebP | Partial | Yes (2020+) | Yes (2020+) | Yes | No | No | No |
| HEIC | No (paid codec) | Yes | Yes | No | No | Converts on upload | Converts on upload |
| AVIF | Partial | Yes (2021+) | Yes (2021+) | Partial | No | No | No |
| TIFF | Partial | Yes | Yes | No | No | No | No |
| SVG | Partial | Yes | Yes | Yes | No | No | No |
| BMP | Yes | Yes | Partial | Partial | No | No | No |
Email clients in this table include Gmail (web), Gmail (Android/iOS), Outlook 2019/2021/365 desktop, Outlook web, and Apple Mail. WebP rendering in email clients varies by client and version -- the safest assumption is that WebP will not display in email.
Quality Loss: When It Happens and When It Does Not
When quality loss is permanent and irreversible
The one-way door rule: converting from a lossless format to a lossy format permanently discards image data. You cannot get it back.
- Saving any image as JPG applies lossy compression. The discarded data is gone forever.
- Re-saving a JPG as JPG again compounds the damage. Each generation of re-saving adds another round of compression artifacts. This is called generation loss. A JPG saved five times at quality 85 looks noticeably worse than a JPG saved once at quality 85 from the original source.
- Converting a high-quality TIFF to JPG loses data permanently. Saving it back to TIFF after that does not restore anything -- you just have a losslessly stored low-quality image.
When quality is fully preserved
- PNG to WebP lossless: no data loss. WebP lossless is a different compression algorithm but preserves every pixel exactly.
- PNG to TIFF: no data loss. Both are lossless formats.
- TIFF to PNG: no data loss, assuming bit depth is compatible.
- JPG to PNG: the pixels are preserved exactly as they were in the JPG -- but the JPG compression artifacts that already existed are preserved too. No new damage, but no repair either.
The one-way door principle stated plainly
Lossless to lossy is a one-way door. Once you step through it -- once you save to JPG, once you accept the compression -- you cannot step back. The original data is gone. The practical consequence: always keep original lossless files (RAW, PNG, TIFF) and treat JPG or WebP lossy as the final export format, not the working format. If you only have a JPG, convert it to PNG before editing. Then export as JPG again when you are finished. This limits generation loss to one round instead of accumulating it with each edit-save cycle.
Format-Specific Insights
JPG: The generation loss trap
JPG is the universal photograph format and it is excellent -- for delivery. The trap is using it as a working format. Every time you open a JPG, edit it, and save it again as JPG, the codec re-compresses the pixels. Over multiple rounds, artifacts accumulate: blotchy areas, color banding, loss of fine detail. Professional photographers shoot RAW and export to JPG only as the final step before delivery. If you only have a JPG source file, convert it to PNG before editing. Then export to JPG for the final deliverable. This limits compression damage to one generation.
PNG: Not always better quality for photographs
PNG has a reputation as the "high quality" format, and for graphics that reputation is accurate. For photographs, the relationship is more nuanced. A PNG photo is lossless -- it contains every pixel exactly. A JPG at quality 90 is nearly indistinguishable to the human eye at 10 to 20 times smaller file size. PNG is the right choice when you need lossless preservation (archiving, future editing, design work) or transparency. It is not the right choice just because you want "better quality" from a photograph -- the JPG visual quality at high settings is already excellent, and PNG of the same photograph buys you little visually while costing enormous storage space.
WebP: Great for web, broken in many other contexts
WebP is technically excellent. Google designed it specifically for web delivery and it achieves better compression than both JPG and PNG at equivalent quality. The problem is ecosystem support. Desktop applications, particularly older versions, often cannot open WebP without plugins. Adobe Photoshop did not support WebP natively until 2022. Email clients do not render it. Windows Photo Viewer does not open it. If someone downloads a WebP from your website and tries to open it on their desktop, many users will be confused when it fails to open. For web-only pipelines where you control the serving environment, WebP is excellent. For anything that might be downloaded and opened in arbitrary applications, convert to PNG or JPG.
AVIF: Encoding speed cost
AVIF produces the smallest file sizes of any mainstream image format at equivalent quality, often 20 to 30 percent smaller than WebP and 50 percent smaller than JPG. The cost is encoding time. AVIF encodes approximately 47 times slower than WebP. For a static website where you encode a library of images once and serve them thousands of times, this is a perfectly reasonable tradeoff. For any real-time pipeline -- user uploads, on-demand resizing, dynamic image generation -- AVIF encoding latency is a serious bottleneck. Most real-time pipelines should use WebP and reserve AVIF for pre-encoded static assets.
HEIC: The "Automatic" cable transfer behavior
iPhone users have an option that many do not know about. When you connect an iPhone to a Windows PC via USB and import photos using the Windows Photos app or Windows Explorer auto-import, iOS can automatically convert HEIC to JPG during the transfer. This is the "Automatic" behavior -- it detects that the destination system may not support HEIC and converts on the fly. This only works via cable import with supported apps. AirDrop sends HEIC as-is. Direct file copy (drag from iPhone storage) sends HEIC as-is. iCloud syncs HEIC as-is unless you have configured iCloud settings to optimize for device compatibility. For users who regularly transfer to Windows, changing the iPhone camera format to Most Compatible (Settings > Camera > Formats > Most Compatible) is the most reliable permanent solution.
GIF: 256 colors makes photographs look terrible
GIF was designed in 1987 for simple web graphics and supports a maximum of 256 colors per frame. Photographs contain millions of colors. When a photograph is converted to GIF, the codec must reduce the entire image to 256 colors. The result is severe color banding, dithering patterns, and a posterized look. GIF is only appropriate for simple flat-color graphics and animations. For animations with photographic quality or more than 256 colors, use WebP animated or video formats instead. For still images, there is almost no modern use case where GIF is the right choice over PNG or JPG.
BMP: Convert immediately
BMP (Bitmap) is an uncompressed Windows format from the early 1990s. It stores every pixel as raw data with no compression whatsoever. A 1920x1080 image in 24-bit BMP is approximately 5.9MB. The same image as WebP is approximately 200KB. That is roughly a 30-to-1 size reduction with no meaningful quality difference. There is no modern use case for BMP in file exchange, web delivery, or storage. If you encounter a BMP file, convert it immediately to PNG for lossless storage or JPG/WebP for smaller lossy storage.
TIFF: Confirm color space before sending to print
TIFF files can be stored in either RGB or CMYK color space, and the color space is not always visible from the filename or thumbnail. If you send an RGB TIFF to a print shop expecting CMYK output, the printer will convert it, and color fidelity is not guaranteed. Blues may shift purple. Bright greens may go muddy. Before sending a TIFF to any professional printer, open the file in your editing software and confirm the color space. Convert to CMYK yourself before delivery if the printer requires it, rather than relying on the print shop automated conversion to produce accurate colors.
SVG: Vector only -- photographs cannot meaningfully become vectors
SVG is a vector format, meaning it stores shapes, paths, curves, and text as mathematical descriptions. It can be scaled to any size without any quality loss because there are no pixels to enlarge -- only instructions for drawing shapes. This makes SVG ideal for logos, icons, diagrams, and illustrations. The limitation: SVG cannot meaningfully represent photographs. Converting a photograph to SVG runs a trace algorithm that attempts to approximate the photo with vector paths. The result is either a massive SVG file with thousands of tiny paths (still not a true vector), or a highly stylized approximation that looks like a posterized art piece. If you need a scalable logo, you need an SVG created in a vector editor, not a rasterized photograph converted to SVG.
Decision Guide by Use Case
Sharing iPhone photos with Windows users
Convert HEIC to JPG. JPG has universal Windows support with no additional software required. If the recipient needs to edit the image extensively, HEIC to PNG preserves lossless quality, but the files will be significantly larger.
Web delivery on your website
Convert to WebP for images served on your website. Use JPG as a fallback for older browsers. If your images are pre-generated and encoding time is not a concern, AVIF offers the best compression. Avoid PNG for photographs on the web unless transparency is required.
Email attachments or inline email images
Use JPG for photographs and PNG for graphics. Do not use WebP, HEIC, AVIF, or TIFF in email. Outlook desktop in particular has notoriously inconsistent rendering, and WebP breaks in most email clients regardless of how modern the recipient system is.
Professional print output
Convert to TIFF and confirm the color space is CMYK. Verify resolution is 300 DPI or higher. If you are starting from a web image (72 DPI), you cannot simply convert it to TIFF at 300 DPI and expect print quality -- the pixels do not contain more information just because you change the DPI metadata. A true 300 DPI print-quality image needs to be captured or created at that resolution from the source.
Logo or graphic with transparent background
Convert to PNG. PNG supports full alpha transparency and works in every application and platform. If the logo is for web use only and file size matters, WebP also supports transparency and is smaller. If the logo needs to scale to any size without quality loss, it should be in SVG format, which requires a vector source, not a rasterized conversion.
Archiving for long-term storage
Use PNG for digital archiving. PNG is lossless, widely supported, and produces reasonable file sizes for most images. TIFF is a valid alternative, especially for images that will eventually be used in print workflows. Avoid JPG for archival copies because the lossy compression permanently discards data you may need later.