{"id":15028,"date":"2026-10-26T16:08:13","date_gmt":"2026-10-26T14:08:13","guid":{"rendered":"https:\/\/shortpixel.com/blog\/?p=15028"},"modified":"2026-10-26T16:08:15","modified_gmt":"2026-10-26T14:08:15","slug":"how-to-compress-screenshots-without-making-text-blurry","status":"publish","type":"post","link":"https:\/\/shortpixel.com\/blog\/how-to-compress-screenshots-without-making-text-blurry\/","title":{"rendered":"How to Compress Screenshots Without Making Text Blurry"},"content":{"rendered":"\n

A screenshot looks perfect on your screen, you run it through a compressor, and the text comes out smudged. You can still read it, technically. You just wouldn\u2019t want to.<\/p>\n\n\n\n

Screenshots are hard on compression. Tiny text, one-pixel lines and hard edges leave nowhere to hide, so whatever the algorithm gets wrong shows up right away. Photos are far more forgiving.<\/p>\n\n\n\n

The good news is that you can usually cut the file size by a good margin and keep the text readable. With ShortPixel, it mostly comes down to picking the right level out of three, then checking the result at 100% before you publish.<\/p>\n\n\n\n

Why screenshots are harder than photos<\/strong><\/h3>\n\n\n\n

A photo is mostly soft transitions: sky, skin, a blurry background. You can squeeze those areas and nobody notices.<\/p>\n\n\n\n

A screenshot is a grey 11px label next to a button, a hairline border, an icon with sharp corners. Add a little noise around a letter and the eye catches it immediately.<\/p>\n\n\n\n

Format and compression level are not the same thing<\/strong><\/h3>\n\n\n\n

Two things decide how your text ends up looking: the format you save in (PNG, JPEG, WebP, AVIF) and the compression level you choose in ShortPixel (Lossless, Glossy or Lossy). It\u2019s easy to blame the format when the level was the problem, or the other way around.<\/p>\n\n\n\n

PNG is where I\u2019d start for anything with small text or interface elements. It keeps edges crisp<\/a>, and that\u2019s exactly what screenshots need. JPEG can leave a faint haze around letters, so I\u2019d skip it for text-heavy images.<\/p>\n\n\n\n

WebP and AVIF are a different story. Both can be lossy or lossless, so the text can come out perfect or soft depending on how the file was made. They\u2019re also not accepted everywhere, so check the upload requirements first. If you need a refresher on what suits what, the guide to the best image file types<\/a> covers it.<\/p>\n\n\n\n

Step-by-step: how to compress a screenshot with ShortPixel<\/strong><\/h3>\n\n\n\n

Nothing to install here. ShortPixel\u2019s online image compressor<\/a> is free and runs in your browser.<\/p>\n\n\n\n

Step 1: Open the compressor<\/strong><\/h4>\n\n\n\n

Head to the online compressor page. Settings and uploads both happen there.<\/p>\n\n\n\n

Step 2: Choose the compression level<\/strong><\/h4>\n\n\n\n

Pick Lossy, Glossy or Lossless, then click Settings<\/strong>. Lossy is preselected, so change it first if your screenshot has small text. If you\u2019re unsure which one, skip to the next section and come back.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Step 3: Check the output options<\/strong><\/h4>\n\n\n\n

Under Settings you\u2019ll find toggles called Generate WebP<\/strong> and Generate Avif<\/strong>. Both start off. Switch them on only if the place you\u2019re uploading to accepts them. When in doubt, leave them off and stick with PNG.<\/p>\n\n\n\n

Step 4: Check the metadata setting<\/strong><\/h4>\n\n\n\n

Keep Exif<\/strong> is already off by default, so just leave it. Most screenshots carry little or no metadata, so you probably won\u2019t save much, but there\u2019s no reason to hold on to it either.<\/p>\n\n\n\n

Step 5: Upload and download<\/strong><\/h4>\n\n\n\n

Drop your files in, give it a few seconds, and download the optimized images.<\/p>\n\n\n\n

Step 6: Zoom in and check<\/strong><\/h4>\n\n\n\n

Don\u2019t judge the result at \u201cfit to screen.\u201d Open it at 100% and go looking for trouble: the smallest text, the thinnest line, the edge of a button. Keep the original open next to it, and look at the colors too.<\/p>\n\n\n\n

Which compression level should you use?<\/strong><\/h3>\n\n\n\n

ShortPixel\u2019s own description is simple. Lossy gives the smallest files, Glossy stays very close to the original, and Lossless is pixel-by-pixel identical<\/a> but saves the least.<\/p>\n\n\n\n

For screenshots, I\u2019d go from gentle to aggressive. Start with Lossless: it preserves the original pixels, which makes it the safest starting point when the text is small. (Resizing or converting to a lossy format are separate steps, and they can still change the result.) Not small enough? Move to Glossy. Still too heavy? Try Lossy, but zoom in before you trust it.<\/p>\n\n\n\n

The goal isn\u2019t the tiniest file. It\u2019s the smallest file where the text still reads comfortably.<\/p>\n\n\n\n

The easiest way to decide is to judge by eye<\/a>. Run one screenshot through all three levels, open each result at 100%, and compare the smallest text. It takes a couple of minutes.<\/p>\n\n\n\n

Colors deserve a look too. In rare cases, PNGs with gradients can look washed out after lossy optimization<\/a>. If that happens, compare against the Lossless version.<\/p>\n\n\n\n

Resize with care<\/strong><\/h3>\n\n\n\n

Resizing is one of the quickest ways to shrink a file, and also the riskiest for text. When an image is scaled down, neighboring pixels get blended, and thin strokes are the first thing to go soft. Even halving the resolution doesn\u2019t guarantee that small text stays crisp.<\/p>\n\n\n\n

So compress first, at the original size. Resize only if the file is still too big, or if you know exactly how wide the image will be displayed. The impact of image dimensions on performance<\/a> is worth reading before you pick a number. Avoid upscaling, since a bigger version doesn\u2019t add real detail and small text can look softer. And check the result at 100%, ideally on the kind of screen your readers use.<\/p>\n\n\n\n

In ShortPixel\u2019s Settings, the Resize to maximum<\/strong> fields take a width and a height, and the image is resized and compressed in one go. If you\u2019re up against a strict size limit, the same resize-then-compress approach is covered in how to shrink an image from 5MB to 100KB<\/a>. Just check the text carefully afterward.<\/p>\n\n\n\n

Compressing many screenshots at once<\/strong><\/h3>\n\n\n\n

Uploading a hundred screenshots one by one gets old fast. The online compressor takes up to 50 files at a time, so a big folder means a few rounds.<\/p>\n\n\n\n

On WordPress, ShortPixel Image Optimizer<\/a> compresses new uploads automatically and can bulk-optimize what\u2019s already in your media library. One setting to look at for screenshots: the option that converts PNG to JPG when it makes the file smaller. It suits photos, but for text-heavy screenshots, test it or keep it off.<\/p>\n\n\n\n

Outside WordPress, the ShortPixel CLI<\/a> works through a folder and its subfolders from the command line. By default, optimized files go into an optimized\/ subfolder, so your originals stay untouched. This example uses Glossy compression, creates WebP versions, and sends the results to a separate .\/out folder:<\/p>\n\n\n\n

.\/shortpixel-optimize.sh -k YOUR_KEY -l 2 -o .\/out –convertto +webp .\/images<\/p>\n\n\n\n

A small tip: because the results go to their own folder, your original screenshots stay as they are. That makes it easy to run the same batch at different levels and keep whichever version holds up best at 100%.<\/p>\n\n\n\n

Quick checklist<\/strong><\/h3>\n\n\n\n