Image Format

Image format is the file type that determines how an image is encoded, compressed, and stored — affecting quality, file size, transparency support, and compatibility.

Related workflow terms: Image Compression.

Common formats compared

The four formats you will encounter most often are PNG, JPG, WebP, and AVIF. Each makes different trade-offs.

• PNG — lossless compression, supports transparency, produces large files. Every pixel is preserved exactly, making it the default choice for screenshots with text, UI elements, and sharp edges. File sizes are the largest of the four.
• JPG — lossy compression, no transparency, produces small files. Designed for photographic content with smooth gradients. Artifacts appear around sharp edges and text at lower quality settings. Not ideal for screenshots.
• WebP — supports both lossy and lossless compression, supports transparency, produces smaller files than PNG or JPG at comparable quality. Widely supported in modern browsers and a strong general-purpose choice.
• AVIF — the newest of the four, offering the best compression ratios. Supports both lossy and lossless modes and transparency. Browser support is broad but not yet universal, and encoding is slower than other formats.

When to use each format

• PNG — when text clarity and pixel-perfect accuracy matter most, or when the recipient may use older software. Documentation, bug reports, and compliance captures.
• JPG — when the image is photographic, file size is a priority, and transparency is not needed. Marketing photos, social media images, and email attachments where slight quality loss is acceptable.
• WebP — when the image is destined for modern web browsers and you want smaller files without sacrificing quality. Blog images, product pages, and web-based documentation.
• AVIF — when maximum compression is the goal and you can serve a fallback format for unsupported clients. Performance-critical web pages and image-heavy applications.

Format and screenshot quality

Format choice directly affects how a screenshot looks after saving. A screenshot of a text-heavy UI saved as JPG at default quality will show visible artifacts around letterforms and interface edges. The same screenshot saved as PNG will be pixel-perfect but two to five times larger.

For workflows that produce many screenshots — automated captures, batch exports, visual documentation — format choice compounds. Choosing WebP lossless over PNG can cut storage by 20-30% with no quality difference. Choosing JPG instead of PNG saves more space but introduces artifacts that may make text unreadable at smaller sizes.

Some capture tools let you select the output format before capture, so the image is saved in the optimal format from the start rather than requiring a conversion step afterward.

Common mistakes

• Using JPG for screenshots with text. JPG's lossy compression creates visible artifacts around sharp edges and letterforms. Use PNG or WebP lossless for anything with readable text.
• Defaulting to PNG when file size matters. PNG files are large. If the screenshots are for web delivery and text clarity is not critical, WebP lossy or AVIF will produce dramatically smaller files.
• Ignoring transparency requirements. JPG does not support transparency. Saving a screenshot with a transparent background as JPG fills the alpha channel with a solid color, usually white, with no way to reverse it.
• Converting between lossy formats repeatedly. Each lossy re-encode degrades quality further. Always convert from the original lossless source when changing formats.