A blog whose posts are mostly photographs pays for image optimization in a different currency than a text blog does. One gallery post becomes dozens of files on disk, each file becomes several registered sizes, and the options that decide how those files are written are usually set once and never revisited. The ShortPixel settings that matter on a photography, travel, or food blog come down to three decisions: what metadata survives compression, what dimensions a file is allowed to keep, and how many generated sizes you are willing to pay to process.
Metadata is the setting image-led blogs get wrong by default
ShortPixel Image Optimizer ships with a Remove EXIF option that is enabled by default, found in the WordPress dashboard by opening Settings > ShortPixel and scrolling the Image Optimization tab to EXIF Management. With it on, the camera-written metadata is stripped while the file is compressed. With it off, ShortPixel preserves the EXIF block together with image comments, IPTC markers, and XMP data.
Two details make this more than a checkbox. First, it is currently an all-or-nothing switch: you cannot keep the copyright fields and discard the shooting data through the plugin alone. Second, the ICC color profile is not part of the bargain at all. ShortPixel states that the ICC profile is never removed regardless of how Remove EXIF is configured, because dropping it would let software guess at the color mapping and shift the rendered result.
A text blog can ignore all of this. A blog built on photographs cannot, because that single switch decides two unrelated things at once: whether your attribution stays inside the file, and whether your location data does.
Photography blogs: keep the credit that travels inside the file
IPTC fields such as the copyright notice, creator, and credit line normally arrive from a preset in editing software rather than from the shutter press, so on most workflows someone has to put them there deliberately. Once written, they stay embedded when a file is downloaded and reposted elsewhere, which is the entire point of using them.
They also have a documented role in search. Google accepts either structured data on the page or IPTC photo metadata embedded in the image, and says one form is enough to be eligible for enhancements such as the Licensable badge. From IPTC it extracts fields including Copyright Notice, Creator, and Credit Line; when both sources are present and disagree, the structured data wins. Google also states plainly that it does not guarantee this information will appear in results.
The consequence for settings is narrow and concrete. If your attribution exists only inside the files, leaving Remove EXIF enabled deletes that copy of it during optimization. The structured-data route still works, because it lives in the page markup rather than the file. So a photography blog has two coherent positions: turn Remove EXIF off and accept that the shooting data rides along, or leave it on and supply the same credit through markup instead. What does not work is assuming the embedded credit survived a bulk run nobody inspected afterward.
Travel blogs: the GPS field decides this one
Location is the reason a travel blog should think about EXIF before it thinks about compression ratios. ShortPixel’s own note on the subject is blunt: GPS data travels with the image when it is uploaded, and anyone who downloads that photo and opens it in a metadata viewer can see where it was taken. Device model, software version, and timestamps sit in the same block.
For a blog that publishes photographs of homes, campsites, workplaces, or anywhere a writer returns to regularly, the default is also the safe answer: leave Remove EXIF enabled and the coordinates never reach the server copy that visitors can download.
The awkward case is a travel blog that also wants embedded attribution. Because the plugin toggle covers the whole metadata block, the cleaner sequence is to drop location at export time in whatever editor produces the JPEG, then decide the plugin setting purely on whether you want IPTC credit preserved. That keeps a privacy decision from being tangled up with a licensing one.
Food blogs: color is protected, texture is not
Food photography lives on smooth gradients and fine surface detail: the sheen on a sauce, steam over a bowl, the open crumb in a cut loaf. Those are exactly the regions where compression artifacts become visible first, and they are also the regions a thumbnail comparison at 25 percent zoom will never reveal.
The color side needs less worry than most people expect. Since the ICC profile is retained no matter how the metadata switch is set, an image edited in Display P3 or Adobe RGB keeps the mapping that tells a browser how to interpret its values. What the plugin cannot do is repair a mode chosen carelessly, so the compression level deserves a real test on a worst-case frame from your own library rather than a vendor sample. A separate comparison of the plugin’s Lossy and Glossy modes works through those trade-offs by image type.
Dimensions come before any compression setting
WordPress applies a ceiling of its own before a plugin sees the file. Core’s big-image handling uses a threshold of 2560 pixels as a maximum width and height; an upload past it is scaled down, and the scaled copy becomes the largest available size that the site serves. The threshold is filterable, which matters for a portfolio layout that genuinely renders images wider than that.
ShortPixel then offers its own Resize Images setting with two behaviors, and both preserve the original aspect ratio:
- Cover resizes the image so that its smallest side exactly meets the target dimension. ShortPixel’s documentation works through a 2445 × 1300 original with the setting at 1000 × 1200: the shorter 1300-pixel side becomes 1200, and the result is 2233 × 1200.
- Contain resizes so that the largest side exactly meets the target instead. Feed that identical file through Contain at that identical target and the 2445-pixel width becomes 1000, for a final 1000 × 533.
ShortPixel attaches one caution to this screen: the resized image should not be smaller than your largest thumbnail, because a smaller value leaves that thumbnail unable to be regenerated later. Two further habits are mine rather than the vendor’s. Keep the plugin’s image backup on while you are still testing values, and take the number from the widest slot your theme actually renders, with headroom for high-density displays, rather than from whatever size your camera happens to produce.
Derivative count is what a gallery-heavy blog really pays
ShortPixel bills per file processed rather than per post: a single credit whenever an image or one of its thumbnails comes back smaller by five percent or more, and next-generation copies are metered on top of that. For a photo-led blog the practical question is therefore how many registered sizes exist, because galleries, sliders, and portfolio themes frequently add their own on top of the core set.
That is what the exclusion controls are for. Under Settings > ShortPixel > Exclusions, the Exclude thumbnail sizes list lets you mark the sizes you do not want processed. Before a large run on an image-heavy site, it is worth listing which registered sizes your templates genuinely output and unchecking the rest. A size your theme registered years ago and never renders is pure cost on every single upload.
Three starting profiles
Each profile below fixes the same three ShortPixel settings in a different order. Treat them as starting points to test against your own library, not tuned recommendations:
- Photography blog. Remove EXIF off if your credit lives in IPTC, otherwise on with structured data supplying the credit. Generous resize ceiling matched to the widest rendered slot. Backup on. Thumbnail exclusions trimmed to the sizes the portfolio template really uses.
- Travel blog. Remove EXIF on, or location dropped at export if you also need embedded attribution. Tighter resize ceiling, since travel layouts rarely render full-width at portfolio scale. Aggressive thumbnail exclusion, because gallery posts multiply every registered size at once.
- Food blog. Compression mode chosen from a side-by-side test on your hardest gradient. Color profile left alone, as the plugin already protects it. Larger sizes preserved wherever recipe cards and hero shots display big.
Verify the run instead of trusting the settings screen
- Open one optimized original in a metadata viewer and confirm which blocks survived, rather than inferring it from the checkbox.
- Compare a full-bleed photograph against its backup at 100 percent zoom, on the detail you care about most.
- Check that credit consumption matches the number of derivatives you expected, not the number of posts you published.
- Confirm the sizes you excluded were actually skipped on a freshly uploaded file.
What these settings cannot do
No configuration rescues a 6000-pixel file dropped into a 900-pixel slot; that is a dimension problem, and compressing it merely yields a lighter file that is still far larger than the slot needs. Running a second lossy optimizer over an already-processed library is worth avoiding for the same reason, since each lossy pass discards data the previous one kept — that is general compression behaviour rather than a documented ShortPixel measurement. And an export already compressed hard in an editor has little left to give, which is exactly the case the five percent rule is written for. Configuring the ShortPixel settings carefully improves file delivery; it does not guarantee rankings, indexing, or traffic.
Frequently asked questions
Does keeping EXIF hurt image quality?
No. ShortPixel notes that EXIF is stored separately from the pixel data, so removing or keeping it changes file size slightly and leaves the visible image unchanged.
Can compression strip my color profile?
Not in ShortPixel. The company documents that the ICC profile is retained regardless of the Remove EXIF setting, specifically to avoid color shifts.
Do WebP or AVIF copies cost extra credits?
Yes. ShortPixel meters every next-generation counterpart separately, so each original and each thumbnail that gains one is charged again. That is why derivative count outweighs post count on an image-led blog.