Why ChatGPT Images Download as WebP (And How to Get PNG)

You generate an image in ChatGPT. You right-click, save it. The file says .png in the save dialog. You open it later and your image editor says it's actually a WebP file. Or it's visibly lower quality than what you saw on screen.

This isn't a bug — it's a deliberate change OpenAI made in 2024, and it's been frustrating users ever since.

What Changed

Before mid-2024, ChatGPT served DALL-E images as actual PNG files. Full resolution, lossless compression, what you'd expect.

Then OpenAI switched to WebP. The images in ChatGPT's interface look the same, and sometimes the file extension even says .png, but the actual data is WebP-encoded. WebP is smaller (good for OpenAI's bandwidth bill) but lossy (bad for your image quality).

The OpenAI community forums have threads with hundreds of replies about this. People noticed. People are unhappy.

Why It Matters

For casual use — sharing on social media, using as a reference — WebP is fine. The quality difference is negligible at screen resolution.

For professional use, it matters:

• Printing: WebP compression introduces artifacts that become visible at print resolutions. If you're printing AI-generated art, you want PNG.
• Editing: Each time you open, edit, and re-save a WebP file, quality degrades (lossy compression compounds). PNG is lossless — edit all you want, no degradation.
• Archival: If you're building a portfolio of AI-generated work, archiving in a lossy format means your collection degrades over time with each re-encoding.
• Compatibility: Some older image editors, CMS platforms, and printing services don't accept WebP. You'll need to convert anyway.

The Manual Workarounds

Method 1: Open Image in New Tab

Right-click the image in ChatGPT → "Open Image in New Tab." Sometimes this gives you a URL to a higher-quality version. Save from there instead.

Results vary. Sometimes you get the same WebP. Sometimes you get a better version. It's inconsistent.

Method 2: Use the ChatGPT API

If you have API access, you can request PNG output directly. The API lets you specify the format, unlike the web interface.

This works perfectly but requires technical setup — API key, code to make requests, handling responses. Not practical for most users.

Method 3: Convert After Saving

Save the WebP file, then convert to PNG using an image converter (online tools, Photoshop, GIMP, ImageMagick).

This preserves whatever quality the WebP has, but it doesn't recover detail lost during WebP compression. You're converting a lossy format to a lossless one — the damage is already done.

Method 4: Screenshot at 100% Zoom

Take a screenshot of the image at 100% zoom. You get a pixel-perfect capture of what's displayed.

The limitation: you're capturing the display resolution, which may be smaller than the generated resolution. And you're capturing UI elements around the image unless you carefully crop.

The Automatic Solution

Chrome extensions that capture images at the API response level — before the browser converts them for display — can grab the full-quality output regardless of what format ChatGPT serves to the web interface.

Opalite Studio's ChatGPT extension intercepts the image at generation time, capturing the full-resolution output. The image in your Opalite gallery is the actual generated output, not the compressed version ChatGPT's interface shows you.

This matters most for heavy users. If you're generating 10-20 images per session, manually checking formats and converting each one is a significant time sink. Auto-capture eliminates the format lottery entirely.

The Same Problem on Other Platforms

ChatGPT isn't the only platform playing format games:

Google Gemini serves images in varying formats depending on browser, device, and image type. Sometimes WebP, sometimes JPEG, sometimes PNG. You can't predict what you'll get.

Grok is more consistent but still doesn't guarantee the format or resolution you'd expect from the generated output.

The pattern is the same across all platforms: the web interface optimizes for display speed and bandwidth, not for download quality. What you see isn't always what you get when you save.

Bottom Line

The WebP issue isn't going away. It saves OpenAI money on bandwidth, and they have no incentive to change it. If PNG quality matters to your workflow, your options are:

1. Manual conversion — works but tedious and doesn't recover lost quality
2. API access — perfect quality but requires technical setup
3. Auto-capture extension — captures full quality at generation time, zero effort

For occasional use, method 1 is fine. For regular use, the time investment in method 2 or 3 pays for itself quickly.