Image compression plugins
An image optimizer can send your media library to an outside service
Some image optimizers compress files on your WordPress server. Others upload original images to an outside compression service. Compare the documented setups below; your settings can change which path runs.
Based on plugin documentation, not tests of your site. Your settings can change which checks run. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor’s browser. It cannot check image uploads from your server to a compression service.
How we group image optimizers
We separate compression on your WordPress server from original image files sent by your server to a vendor API. Uploading an image for compression does not by itself show that browsing history was collected. Photos can contain camera details and GPS location. Sending a photo to a compression service can send those details too. Metadata removal from the optimized image does not prove removal before upload. An optional image CDN rewrite is a visitor browser request and is a different step. Consent timing has not been tested, and data retention has not been assessed unless a source states a retention window.
How an image optimizer handles your media
Compressed on your WordPress server
EWWW Image Optimizer in local mode runs compression tools on your WordPress server. Original media files are not sent to a vendor compression API in this setup. The listing states metadata removal is on by default and can be turned off. Optional cloud API and Easy IO CDN paths are outside this local-mode group.
Sent to an outside compression service
Imagify, ShortPixel, Smush, and TinyPNG send original image files from your WordPress server to their compression APIs. Uploading an image for compression does not by itself show that browsing history was collected. Photos can contain camera details and GPS location. Sending a photo to a compression service can send those details too. Metadata removal from the optimized image does not prove removal before upload. Plugin rows state only what each listing documents about keeping or removing metadata. An optional Smush Pro image CDN can rewrite visitor image URLs; that visitor browser path is a different step. The host column covers documented browser requests only.
Before consent
Consent timing is not tested here. A consent checkbox or cookie modal in a plugin is not a test of your site. The Before consent column is not a scan finding.
Image optimizer plugins
No paid placement. Plugins that compress on your WordPress server appear first, then outside compression services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Documented outside browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| EWWW Image Optimizer This row covers EWWW Image Optimizer in local mode. Compression runs with tools on your WordPress server (jpegtran, optipng, and related binaries named in the listing). Original media files are not sent to a vendor compression API in this setup. The listing states metadata removal is on by default and can be turned off. An optional Compress API and Easy IO CDN path send work to api.exactlywww.net or rewrite visitor image URLs; those paths are outside this local-mode row. Consent timing is not tested here. | Compressed on your WordPress server | No outside browser host documented for this setup. Server compression API calls are a different step. | Not assessed | Not tested |
| |
| Imagify This row covers Imagify when media library images are optimized. Your WordPress server uploads image files to app.imagify.io/api/ for compression and receives optimized files back. The listing states optimization runs on Imagify servers and that EXIF data is not removed. Uploading an image for compression does not by itself show that browsing history was collected. No visitor browser host is cited for this compression step. Consent timing is not tested here. | Images sent to an outside compression service | Outside browser hosts not verified | Not assessed | Not tested |
| |
| ShortPixel This row covers ShortPixel when images are optimized through the Image Optimization Cloud. Your WordPress server sends original images to api.shortpixel.com (v2/reducer.php) and downloads optimized versions. The listing states all optimization runs in ShortPixel’s cloud and that EXIF can be kept or removed. Uploading an image for compression does not by itself show that browsing history was collected. No visitor browser host is cited for this compression step. Consent timing is not tested here. | Images sent to an outside compression service | Outside browser hosts not verified | Not assessed | Not tested |
| |
| Smush This row covers Smush when images are optimized through the Smush API. Your WordPress server posts image data to wpmudev.com/api/smush/ for compression. Uploading an image for compression does not by itself show that browsing history was collected. An optional Smush Pro image CDN can rewrite visitor image URLs to a CDN host; that visitor browser path is a different step and is not cited as a compression-API host here. Consent timing is not tested here. | Images sent to an outside compression service | Outside browser hosts not verified | Not assessed | Not tested |
| |
| TinyPNG This row covers TinyPNG (Compress JPEG & PNG images) when media is compressed through Tinify. Your WordPress server sends image files to api.tinify.com. The listing states you can choose to retain copyright metadata, creation date, and GPS location in original images. The listing also states uploaded images are stored for a maximum of 48 hours — that is a vendor claim, not a measured deletion guarantee. Uploading an image for compression does not by itself show that browsing history was collected. No visitor browser host is cited for this compression step. Consent timing is not tested here. | Images sent to an outside compression service | Outside browser hosts not verified | Vendor states: up to 48 hours | Not tested |
|
What this table does and does not prove
This table describes the named image-optimizer setups, not requests measured on your site. Uploading an image for compression does not by itself show that browsing history was collected. Photos can contain camera details and GPS location. Sending a photo to a compression service can send those details too. Metadata removal from the optimized image does not prove removal before upload. The host column covers documented visitor browser requests, not every server compression API call. Other page requests are not covered. Caching CDNs and gallery embeds have separate pages. Plugins marked Not reviewed have not been assessed. Consent timing has not been tested, and vendor data retention has not been assessed unless a source states a retention window.
Documentation snapshot: Oct 7, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-image-optimizer-privacy