Images are often among the largest resources on a webpage. VergeCloud can optimize supported images at the edge and generate resized versions from the same source image, helping reduce image transfer size and avoid serving unnecessarily large dimensions.
Use image optimization when supported images should be delivered in an optimized format, and image resize when the same source image needs to be served at different dimensions.
This guide explains how to enable both features, configure resize parameters, keep resized variants correctly cached, verify the output, and exclude images that should remain unchanged.
Image Optimization and Image Resize process the image delivered through VergeCloud without requiring you to manually create every optimized or resized version at the origin.
With Image Compression enabled, VergeCloud can optimize supported JPEG, PNG, and GIF image requests and deliver optimized responses as WebP.
During validation, supported source images were returned as WebP after Image Compression was enabled.
Source Format | Original Size | Optimized Size |
JPEG | 107.68KB | 58.13KB |
PNG | 170.71KB | 28.00KB |
GIF | 1.41MB | 495.84KB |
The exact reduction depends on the source image and its contents.
Image Resize allows different image dimensions to be requested through URL parameters.
For example:
https://example.com/images/product.jpg?width=300
and:
https://example.com/images/product.jpg?width=600
Both requests can use the same original source image while returning different resized outputs.
Before enabling optimization, measure the images currently being transferred to visitors.
In browser Developer Tools:
Open the webpage.
Open Developer Tools → Network.
Filter requests by image type.
Reload the page.
Note the format and transferred size of the larger images.
This provides a baseline that you can compare with the optimized result.
Image optimization is available from the Boost settings for the selected domain.
In the panel, Image Compression is enabled as a feature toggle.
After enabling compression, compare the visual quality and transferred size of your images before applying the configuration broadly to image-heavy pages.
The tested Image Compression configuration processed:
JPG
PNG
GIF
The optimized responses observed during validation were delivered as WebP.
For other delivery optimizations, see Webpage Boost.
Image Resize allows different dimensions to be generated from one source image.
The validated Image Resize configuration supports width and height parameters.
Examples:
https://example.com/images/product.jpg?width=300
https://example.com/images/product.jpg?width=600
You can also request width and height together where both dimensions are required.
Different requested dimensions produced different resized outputs during validation.
A single source image can be reused at multiple dimensions.
For example:
Smaller layout: ?width=300
Larger layout: ?width=600
This can help prevent a smaller device or component from receiving a much larger image than necessary.
Resize parameters must remain part of the cache key when they change the generated image.
With Include QueryString, URLs such as:
image.jpg?width=300
and:
image.jpg?width=600
can be stored as separate cache variants.
Do not use Ignore QueryString when the query parameters change the required image dimensions. Otherwise, different resize requests may share one cache entry.
For related settings, see edge caching.
Optimized and resized images can be cached at the VergeCloud edge like other eligible resources.
Each resize URL can create a separate cache variant when the query string is included in the cache key.
For example:
image.jpg?width=300
and:
image.jpg?width=600
represent two different outputs.
Use a practical set of image dimensions instead of generating unnecessary variations. A large number of different resize values can create additional cache variants for the same source image.
If a source image is replaced, resized versions may already exist in cache.
With Include QueryString, selectively purging:
https://example.com/images/product.jpg
does not clear separate variants such as:
https://example.com/images/product.jpg?width=300
and:
https://example.com/images/product.jpg?width=600
To refresh one resized version, purge its complete URL including the query string.
Use Purge All when a broader refresh of the domain cache is required.
Check the actual Network response after enabling Image Compression or Image Resize.
Open Developer Tools → Network and reload the page.
Check the image request for:
source filename
response type
transferred size
requested URL
query-string parameters
returned dimensions where applicable
The filename can retain its original .jpg, .png, or .gif extension while the Type column shows that the delivered response is WebP.
For example:
File | Type |
image-1.png | webp |
image-2.gif | webp |
image-3.jpeg | webp |
Compare the same image requests before and after Image Compression is enabled.
For example, a JPEG image can reduce from approximately:
107.68 KB → 58.13 KB
The exact reduction varies by image.
When reviewing an image-heavy page, compare several of the larger assets to understand the overall reduction in transferred data.
Some images may need to remain in their original format.
A specific image or image path can be excluded from Boost processing using a Page Rule.
To exclude a specific image:
Open Page Rules for the required domain.
Create a new Page Rule.
Match the required image URL or path.
Disable Boost for the matching request.
Save and activate the rule.
Purge the affected image.
Reload the image and check its response type in Developer Tools.
For example:
https://example.com/images/product.jpg
When Boost is disabled for the matching image, the image can continue to be delivered in its original format while Image Compression remains enabled for other images.
Image Optimization works best alongside the rest of the website's caching and delivery configuration.
Combine it with:
appropriate edge caching
suitable Cache Max Age values
correct query-string handling
responsive image dimensions
selective cache purging
CSS and JavaScript optimization where required
Image Compression reduces the transferred size of supported images, while Image Resize allows the same source file to serve different layout requirements.
Together, these features help reduce unnecessary image transfer while keeping image management at the origin simpler.
No. Image optimization is applied during edge delivery and does not modify the original source image stored at the origin.
Image Compression supports JPG, PNG, and GIF images and delivers optimized versions in WebP format.
Browser compatibility depends on the browsers supported by the website or application. Review the browser requirements of your application when compatibility with older clients is required.
With Include QueryString, resize URLs such as ?width=300 and ?width=600 are treated as separate variants because the requested output is different.
Create a Page Rule matching the required image path and disable Boost for that rule.
Use a specific path pattern so that only the intended images are excluded from optimization.