Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

ShortPixel Lossy vs Glossy vs Lossless: Which Should You Use?

Short answer

Use Lossy for most WordPress images because it gives the smallest files with little visible change. Use Glossy for photos and product images where detail matters more than the last bit of speed. Use Lossless only when every pixel must stay the same, such as logos, screenshots, and images you will edit again.

Key takeaways

  • Lossy gives the smallest ShortPixel files and is the default choice for most WordPress images.
  • Glossy is still a lossy method, but it keeps more detail and suits photos and product images.
  • Lossless output is pixel-by-pixel identical to the original, so its file size saving is the smallest.
  • ShortPixel charges a credit only when an image or thumbnail shrinks by at least 5%.
  • Keep the Image backup option on if you may want to restore an image or change its level later.
  • Format and compression level are separate choices, so WebP or AVIF does not replace picking a level.

What is the difference between lossy, glossy and lossless in ShortPixel?

Lossy gives the smallest files, Glossy keeps more detail at a slightly larger size, and Lossless keeps every pixel the same.

ShortPixel offers 3 levels, and each one trades file size against image detail in a different way. Lossy removes some image data to cut the file size as far as it can.

Glossy also removes data, so it is a lossy method, but it is tuned to keep more detail. Lossless removes no pixel data at all.

ShortPixel's own FAQ puts it plainly: Lossy gives the smallest optimized images, Glossy trades a little speed for top-notch quality, and Lossless images are pixel-by-pixel identical to the originals. That FAQ is the clearest starting point, and it is the source for the definitions in this guide (ShortPixel FAQ).

The WordPress.org plugin page gives the same 3-way choice in practical terms. It says to choose Lossless for pixel-perfect quality, Glossy for an excellent balance between quality and compression, or Lossy for maximum file size reductions (ShortPixel Image Optimizer).

A compression level is a setting, not a file format. ShortPixel works with JPEG, PNG, GIF, and PDF files, and it can also create WebP or AVIF versions. The level you pick applies on top of the format, so you still need to choose both.

How much smaller are files with each ShortPixel level?

Lossy saves the most, Glossy saves less than Lossy, and Lossless saves the least, but the exact saving depends on the image.

ShortPixel says lossy compression can cut file sizes by up to 90% while keeping a high-quality appearance. That is a ceiling, not a promise for every image. A photo with smooth tones compresses far better than a busy image with fine detail (ShortPixel lossy vs lossless guide).

The same ShortPixel article gives one worked example. Its original image was 1.18 MB. Lossy cut it to 199 KB, an 83.51% reduction.

Lossless cut the same image to 1.10 MB, a 9.26% reduction. That gap shows why the level matters more than any single setting.

ShortPixel also reports a larger batch result. When it compressed 11,000 mixed photographic images with standard Lossy settings, the set fell 46.5%, from 536.6 MB to 287.2 MB. A mixed library saves less than a single clean photo, so expect a range, not one number (ShortPixel Drupal announcement).

ShortPixel levelFile sizeQualityBest for
LossySmallestSmall visible change possible at full zoomMost blog and site images
GlossyMiddleVery close to the originalPhotos and product images
LosslessLargest of the 3Pixel-by-pixel identicalLogos, screenshots, and images to edit later

Use the table as a guide, not a guarantee. Your own images will land somewhere inside the ranges above, and only a side-by-side look at full size tells you if a level is right for a specific image. For the Smush comparison, see Smush vs ShortPixel.

Which ShortPixel level should you use for photos?

Use Lossy for most photos, and Glossy when the photo is the main subject and detail matters.

Most photos on a WordPress site are viewed at post width, not at full resolution. Lossy is the right default there because it gives the smallest files with little visible change at that size.

ShortPixel's FAQ says Lossy is the best option for most users, and that advice fits blog photos, news images, and general site photos.

Glossy fits photos where a visitor will look closely. ShortPixel describes Glossy as a high-quality lossy method designed especially for photographers and sites with high-quality product pictures. That covers portfolio work, hero photos, and product shots where soft detail would be noticed.

Web.dev gives the same general rule for photos. It says to use JPEG, lossy WebP, or AVIF for a photo, and to try several quality levels to find the best trade-off between quality and file size (Choose the right image format). ShortPixel's level is the place where you make that trade-off in WordPress.

If you want faster pages overall, start with Lossy on photos and move only the images that look soft to Glossy. That keeps most of the saving while protecting the few images that carry the page. For a wider speed plan, see how to speed up WordPress.

Which ShortPixel level should you use for logos, screenshots and text?

Use Lossless first for logos, screenshots, and any image with small text or sharp edges.

Lossy compression can blur edges and add halos around text. That damage is easy to see on a screenshot, a diagram, or a logo with clean lines. Lossless keeps every pixel, so edges stay sharp and text stays readable.

ShortPixel gives the same advice for screenshots. Its screenshot guide says format and compression level are not the same thing, and it advises starting with Lossless because it preserves the original pixels. That makes Lossless the safest starting point when text is small (How to compress screenshots).

Web.dev agrees on the principle. It says to use PNG or lossless WebP when you need to preserve fine detail at the highest resolution. A ShortPixel Lossless setting does the same job inside WordPress, whatever format the file ends up in.

If Lossless leaves a file too large, try Glossy next, then Lossy, and check the text at 100% zoom after each step. Stop at the first level where the text still looks clean. Do not jump straight to Lossy for a screenshot just because it is the default.

How do you pick a level and apply it in WordPress?

Pick the level in Settings > ShortPixel, save it, then apply it to new uploads first and to old images in bulk. For every setting on that screen, see ShortPixel settings explained.

You need the ShortPixel Image Optimizer plugin installed and active, plus an API key from your ShortPixel account. The plugin sends original images to ShortPixel's cloud service for compression, then returns the optimized versions to your site. That cloud step is why an API key is required (ShortPixel FAQ).

Follow these steps to set a level:

  1. Open your WordPress admin and go to Settings > ShortPixel.
  2. Add your API key if the plugin asks for it, then save.
  3. Find the Compression type setting and choose Lossy, Glossy, or Lossless.
  4. Turn on the Image backup option in the same settings screen, so you can restore an original later.
  5. Save the settings, then upload 3 to 5 test images of different types.
  6. Open each test image at full size and check faces, text, edges, and gradients.
  7. If the tests look good, use the Bulk ShortPixel option to apply the same level to your existing Media Library.

Allow a few minutes for the test images, and longer for a large library. Bulk work runs through the cloud, so the time depends on how many images and thumbnails you have, not on a fixed number of minutes.

The backup step matters. The WordPress.org plugin page says the original is needed if you want to restore an image, or to convert an image from lossy or glossy to lossless, or the other way round. Without a backup, you cannot switch levels cleanly later.

How does the level affect WebP and AVIF versions?

The level still matters after conversion, because WebP and AVIF can each be lossy or lossless.

A modern format does not replace the level choice. ShortPixel can create WebP or AVIF versions of your images, but it still applies Lossy, Glossy, or Lossless when it makes them. A lossy WebP file and a lossless WebP file can look very different at the same size.

Google's WebP documentation gives useful context for the format side. It says lossy WebP images are 25-34% smaller than comparable JPEG images at the same quality, and lossless WebP images are 26% smaller than PNG images (WebP format guide). Those are format savings, on top of the saving from the ShortPixel level.

Web.dev also says WebP and AVIF generally give better compression than older formats, and should be used where possible, with JPEG or PNG as a fallback. That advice is about format, not about how hard to compress. Pick the format for compatibility, then pick the level for quality.

Keep the two choices separate in your notes. If an image looks bad, check whether the format or the level caused it. Changing the format will not fix a level that is too harsh, and changing the level will not fix a format that a visitor's browser cannot show well.

How many credits does each level use?

ShortPixel charges by result, not by level, and a credit is used only when an image or thumbnail shrinks by at least 5%.

That 5% rule comes from ShortPixel's FAQ, and the WordPress.org plugin page repeats it. If an image does not shrink by at least 5% with Lossy, no credit is used for it. That protects you from paying for work that did not help.

The free plan gives 100 free credits per month as of November 2026. ShortPixel also lists an unlimited monthly plan at $9.99 and one-time credit packs from $19.99 as of November 2026. Check the current plugin page before you plan a large bulk job, because prices change.

Each image can use more than 1 credit. ShortPixel counts the original and its thumbnails, and any extra WebP or AVIF versions, as separate items. A single upload with many thumbnail sizes can therefore use several credits, even on the free plan.

Lossless often uses credits for less saving, because its files shrink less. That is normal.

You are paying for pixel-perfect output, not for the biggest saving. If credit use is tight, keep Lossless for the few images that need it, and use Lossy or Glossy for the rest.

How do you check that the level you picked worked?

Compare file size and visual quality at full size, then check page speed on a real page.

Start with the file. Note the size of an original image before optimization, then compare it with the optimized version in your Media Library or uploads folder. A Lossy image should be much smaller, a Glossy image should be smaller but closer to the original, and a Lossless image should be only a little smaller.

Then check the picture itself. Open the optimized image at 100% zoom and look at faces, hair, gradients, text, and hard edges.

Zooming in is where lossy damage shows first. If you only check a small thumbnail, you will miss the problems that a visitor sees on a large screen.

Finally, check the page, not just the file. Load a page that uses the images and run it through a speed check, such as the WordPress speed test. If the page still loads slowly, the problem may be image size, image count, or another factor, not the compression level alone.

Keep 2 or 3 original test images in a folder outside WordPress, with their sizes noted. That gives you a fixed reference when you change levels later.

If you made the images with AI, the same check applies, so see how to generate images with AI in WordPress for the creation step, then use the steps above to judge the result.

What mistakes should you avoid?

Do not set a level, run bulk optimization on your whole library, and only then look at the results.

The most common mistakes are easy to avoid:

  • Picking Lossy for every image, including logos and screenshots with small text.
  • Running bulk optimization before testing 3 to 5 images at full size.
  • Turning off Image backup, then finding you cannot restore an original or switch levels.
  • Judging quality only from a small thumbnail, where lossy damage is hard to see.
  • Treating WebP or AVIF as a fix for a level that is too harsh.
  • Changing the level after a bulk run and expecting the old images to change on their own.

A level change applies to images you optimize after the change. Images already optimized stay at their old level until you restore them from backup and optimize them again. That is why the test step and the backup step come before the bulk step.

For a full picture of the plugin itself, including its other features, see the ShortPixel review. Keep this guide focused on the level choice, and use that review for the wider plugin decision.

Frequently asked questions

Is Glossy the same as Lossless in ShortPixel?

No. Glossy is a lossy method, so it removes some image data, but it is tuned to keep more detail than Lossy. Lossless removes no pixel data, so its output is pixel-by-pixel identical to the original. Glossy gives smaller files than Lossless, but larger files than Lossy.

Can I change from Lossy to Lossless later?

Yes, but only if you kept the original image. Turn on the Image backup option in Settings > ShortPixel before you optimize, so the original is saved. You can then restore the original and optimize it again at the new level. Without a backup, you cannot rebuild the lost pixel data.

Does Lossy always make images look worse?

Not always. At normal viewing size, many Lossy images look the same as the original, and the file is much smaller. Damage shows first at full zoom, on faces, gradients, text, and sharp edges. That is why you should check test images at 100% zoom before you run a bulk job.

Should I use Lossless for every image to be safe?

No, because Lossless saves the least space and can use credits for a small saving. Most blog photos and general site images do not need pixel-perfect output. Save Lossless for logos, screenshots, diagrams, and images you plan to edit again, and use Lossy or Glossy for the rest.

Does the compression level change how many credits I use?

ShortPixel charges by result, not directly by level. A credit is used when an image or thumbnail shrinks by at least 5%. Lossless files shrink less, so you may get less saving per credit, but the level itself does not set a different credit price. Extra WebP or AVIF versions can add credits.

Sources

  1. Frequently Asked Questions (FAQ) ShortPixel
  2. Lossy vs Lossless Compression: Comprehensive Analysis ShortPixel
  3. ShortPixel Image Optimizer – Optimize Images, Convert WebP & AVIF WordPress.org
  4. Choose the right image format web.dev
  5. An image format for the Web Google for Developers
  6. How to Compress Screenshots Without Making Text Blurry ShortPixel

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test