Tessalor
Search tools⌘K
EN
ENEnglishDEDeutschفافارسی

Menu

Search toolsChangelog

↑↓ to move↵ to openDescribe the problem, not the tool

Guide answer

Lossy or lossless WebP for a screenshot?

Start with lossless WebP for a screenshot. Interfaces, charts and code contain flat colour, repeated regions and hard edges—the patterns a lossless encoder compresses well and a lossy encoder tends to blur or ring around. If the screenshot is dominated by a photograph, compare both outputs at the actual display size; lossy may then be much smaller. The correct choice is the smaller acceptable measured file, not the mode whose name sounds more aggressive.

What to take away

  1. Text and one-pixel interface edges expose lossy artifacts earlier than photographic detail does.

  2. A mixed screenshot can favour lossy when a large photo dominates the pixel area, so compare real outputs.

  3. Resize to the largest size the image will actually be shown before judging either compression mode.

The full explanation

"Lossy is smaller, lossless is bigger" is a reasonable rule of thumb that is wrong often enough to matter. Which one wins depends on what is in the image, not on which mode sounds more aggressive — and for screenshots, logos, charts and diagrams the lossless encoder frequently produces the smaller file *and* the perfect one. Read the complete guide for the reasoning, examples and definitions behind this answer.

Use the idea

Image to WebP Converterconvert png to webp and make it smallerPNG to JPEG Converterconvert png to jpg without a black backgroundImage Resizerresize an image without uploading it anywhereImage Metadata Removerremove metadata from an image

Sources