[00] Subset Sizes, User guide
Imagify
Last updated
How Subset Sizes sends sizes it makes on demand to Imagify, which images and sizes Imagify takes, and what happens when Imagify is busy.
Subset Sizes works with Imagify with nothing to set up on the Subset side. Imagify compresses images at upload. When Subset Sizes later makes a size a page asks for, it adds that size to Imagify’s background queue at the same compression level as the rest of the image.
What works
- New sizes join Imagify’s queue. Subset Sizes passes the new sizes to Imagify’s optimisation process for that image, and Imagify compresses the files in the background, not during the page request.
- The image’s level is kept. A new size is compressed at the level Imagify used for that image’s original.
- Busy images are retried. Imagify locks an image while an earlier job for it is running. When that happens, Subset Sizes tries again one minute later, then two minutes after that, and gives up after three attempts.
- One hand-over per image. All the sizes one page view creates for an image are sent together at the end of the request.
- Imagify errors stay in Imagify. If the hand-over fails, the image is still served.
What needs a setting
Nothing extra. Two Imagify settings decide what gets compressed, both described in Imagify’s recommended settings (opens in a new tab):
- Auto-Optimize Images on Upload decides whether originals are compressed when you upload them. Subset Sizes only sends new sizes for images Imagify has already compressed.
- Files Optimization lists the registered sizes. A size you haven’t ticked there isn’t compressed when Subset Sizes makes it.
Known limits
- Images Imagify hasn’t compressed are left alone. Subset Sizes sends nothing for them. When Imagify compresses one later, from its bulk tool or the media library, it includes the sizes that exist by then.
- Only registered sizes are compressed. Imagify works from the sizes WordPress, your theme and your plugins register. A size made for custom dimensions your code asked for isn’t in that list, so Imagify skips it.
- Retries need WP-Cron. On a site with little traffic, a retry can run later than one minute.
- The first visitor gets the uncompressed file. Compression happens after the request ends.