ShortPixel lossy vs glossy is a decision about how much visual data you will throw away so a page can load a smaller file. Lossy takes the most. Glossy still discards data, but it is tuned to keep more of the detail a photographer or product page actually needs. Lossless sits off to the side: the pixels stay the same as the original, and the file usually shrinks much less.
If you already installed the plugin and only need the rest of the dashboard, use ShortPixel WordPress Plugin: Setup, Settings. Plan cost belongs in ShortPixel Pricing Explained: Free, Unlimited, or One-Time Credits?.
What Lossy and Glossy actually change
Both Lossy and Glossy are lossy algorithms. That sentence is easy to skip, and it is the whole point. Glossy is not a lossless preset with a prettier name. ShortPixel built it as a milder lossy method after photographers said ordinary Lossy was too blunt for the files they publish. The plugin listing still describes Glossy as high-quality JPEG compression aimed at photographs and product pictures. Treat it that way: still compressed, just less hungry.
Lossy is the default ShortPixel recommends for most sites. Official guidance is blunt about the trade. You get the smallest optimized files the service will give you. ShortPixel still presents Lossy as the strongest compression rate, and the option it recommends for most users. If page weight is the problem you are trying to fix, start here. Do not start here because the word “lossy” sounds reckless. Start here because most blog photos, featured images, and marketing shots are viewed at a few hundred pixels on a phone, not as prints on a wall.
Glossy is for the people who will notice the missing grain. ShortPixel’s own comparison says to pick it when you still care about speed tests, but you will accept a slightly heavier page to keep the picture closer to the original. That is a real trade, not a slogan. The extra kilobytes are the cost of keeping more texture in skin, fabric, foliage, and product edges.
Lossless is the conservative option. The optimized file is described as pixel-by-pixel identical to the original. The size drop is smaller than either Lossy or Glossy, sometimes almost nothing on a file that was already saved tightly. Use it when a wrong pixel is worse than a slow request: logos, icons, UI chrome, diagrams, screenshots with small type, anything with hard edges and flat color.
One official example, not a promise
ShortPixel published one worked example when Glossy launched. On that photograph, the original sat at 2.32 MB. Lossless came back at 2.30 MB. Glossy landed at 514.4 kB. Lossy landed at 407.9 kB. Those numbers belong to that file. They are not a typical saving rate, and they are not a reason to skip your own test. They do show the shape of the ladder: Lossless barely moved the original, Glossy cut hard, Lossy cut harder.
If your library is full of already-exported web JPEGs, the gap between Glossy and Lossy may be smaller than that example. If you upload camera originals, the gap can be larger. The only honest method is to pick a few of your files and look at them at the size they actually appear on the site.
Pick by image type, not by habit
Ordinary blog and marketing photos
Lossy is usually enough. A travel photo used at 800 pixels wide does not need the same treatment as a gallery print. Banding in a soft sky or a little mush in distant trees is annoying in a zoomed crop. It is often invisible in the layout. If a hero image still looks cheap after Lossy, move that one file to Glossy instead of converting the whole library.
Photography portfolios and retouched work
Glossy is the mode ShortPixel built for this job. Photographers asked for it because they could see what Lossy removed. That does not mean Glossy is magic. It means you should compare Lossy and Glossy on a high-ISO frame, a dark scene, and a file with fine fabric or hair. If Lossy flattens the grain into plastic, Glossy is the next stop. If even Glossy looks wrong, Lossless is the remaining option, and you should expect the page to carry more weight.
Product photos
Jewelry, watches, stitching, wood grain, and food texture are the cases where Glossy is usually the better match. A customer pinching a phone screen is looking for scratches, weave, and color, not for a smaller transfer size. Run Lossy on a representative SKU first. If the edge of a logo on the product or the specular highlight on metal turns noisy, switch that class of images to Glossy. Keep Lossy for secondary shots that never appear large: badges, tiny category thumbs, decorative backgrounds.
Logos, screenshots, and text
Do not put these through Lossy as a default. JPEG-style smearing around letters is the usual failure. Charts, annotated screenshots, and transparent PNG icons want Lossless, or they want to stay in a format that keeps sharp edges. If a PNG has already been through another optimizer, another Lossy pass can make the damage obvious. Restore if you still have a backup, then use Lossless or leave the file alone.
Already-compressed JPEGs are a trap
A file exported from Photoshop, Lightroom, or a phone at a low quality setting has already thrown data away. Sending that file through Lossy again is a second round of guessing. Blocking, muddy reds, and ringing around contrast edges show up more often on these than on a full-quality original. Glossy is the safer ShortPixel pass when you cannot get a better source. Lossless is safer still if the image is a graphic rather than a photograph. The real fix is a better export, not a more aggressive plugin setting.
Double optimization from two plugins is the same trap with extra steps. If Jetpack, a host optimizer, or a CDN is already recompressing the public file, ShortPixel Lossy on top can look worse than either tool alone. Pick one optimizer for the file that WordPress stores. Then check what the CDN actually serves.
How to test the three modes without wrecking the library
Do not bulk-run a guess. ShortPixel can generate Lossy, Glossy, and Lossless versions from the Media Library so you can look at the same image under each setting. Use List view, pick four or five files that represent the site, and compare them at the width they use on the front end, not at 100 percent zoom unless that is how readers see them.
A usable test set is boring on purpose:
- a bright outdoor photo
- a dark indoor photo
- a product or portrait with fine texture
- an image that contains text or a hard edge
- a transparent PNG if the site uses any
Look at the live page after cache is cleared. A dashboard thumbnail lies. So does a crop opened in a new tab at full size when the theme never displays that size. Check mobile and desktop. If Lossy fails on one class of images, change the mode for that class. You do not owe the whole library a single setting.
Keep image backup on before you test in earnest. ShortPixel stores originals locally when that option is enabled, and it is on by default. Without a backup, you cannot return a file to the original and try a different mode. The original is what the plugin needs if you later move from Lossy to Glossy, or the other way around.
How to switch later
Saving a new compression type does not rewrite files you already processed. If the library ran as Lossy and you now want Glossy, change the setting under Settings, ShortPixel, Image Optimization. Then restore from Settings, ShortPixel, Tools with Bulk Restore. After the restore finishes, run Bulk ShortPixel again. That second run uses more credits unless the account is on Unlimited. Credits already spent on the first pass are not returned.
Restore a single file the same way if only a handful look wrong: Media Library, List view, the restore backup control on that item. If the control is missing, that file has no backup. Leave it, or replace it with a fresh original from disk.
Test a small batch after the switch before you restore thousands of files. A full restore cannot be undone from the plugin, and it is a poor way to discover that Glossy was never the problem. Sometimes the source is small, the theme asks for a large display size, or another service is compressing the public copy. Fix that first.
A mixed library is allowed
One site can use more than one mode. A news blog can keep Lossy for article photos and Lossless for author headshots that look waxy. A shop can keep Glossy for the catalog and Lossy for blog posts. The cost of that mix is operational, not moral. You have to remember which folders or upload habits use which setting, and you have to avoid a later bulk job that paints Lossy over everything.
If you change the global default, assume future uploads follow that default. Process exceptions by hand, or restore those files and send them through the mode you actually want. Do not rely on memory six months later.
A mixed setup also fails when editors upload from phones at whatever quality the camera app chose that day. Lossy on a 400 KB social export is not the same job as Lossy on a 6 MB camera JPEG. If the team cannot control export quality, Glossy is a safer house default for photos, and Lossless remains the rule for graphics. Write that down somewhere the next person will see it.
A practical verdict
For ShortPixel lossy vs glossy, the useful answer is narrower than a ranking. Lossy is the right first setting for most photographs that appear at ordinary web sizes. Glossy is the right next setting when those photographs are the product, or when Lossy visibly damages texture. Lossless is for files where a changed pixel is a defect.
Official guidance still points most people at Lossy, and it points photographers and other high-detail work at Glossy. That split holds up if you test it on your own images instead of copying a default from a tutorial. Keep backups. Compare at display size. Switch with a restore, not by stacking another pass on an already-crushed JPEG.
For ShortPixel’s own wording on the default, read the Lossy, Glossy or Lossless comparison. For how Glossy was defined and the one published file-size example, read Glossy image optimization for photographers.