VIP Go uses a service similar to Photon, so the core image processing is the same with (roughly) the same filters. Similar to Photon, there is the ability to handle image resizing, cropping, process successive transformation functions. For example, you are now able to perform a crop followed by a resize function with a filter tacked on the end, as well as many other combinations.
That same base image can be easily transformed into a smaller full-color version:
An important reason for always using transformations is to reduce the bandwidth especially for mobile customers. There’s no need to serve a 5000×3000 image when it will be displayed in a 500×300 area. Adding the width or height parameter allows mobile users to see the image more quickly, and saves on the mobile users’ data allocation. Instead of a 28MB download that takes 20s they get a 200kB download in 100ms.
It’s very important to always support this, especially in native mobile apps. If your JSON payload to a mobile app contains just a single original sized image URL, be sure to add the query parameters you need inside the application when using that URL to display the image.
Using image sizes
the_post_thumbnail() function in your templates, you can set a specific image size in order to customize the output of the image src. For example, if you have a
custom-size image size, you can pass it in with
the_post_thumbnail( 'custom-size' ); and your image will output at your desired size.
If you don’t specify an image size, VIP will default to:
content-widthset by your theme (see Theme Handbook Functions)
- If no
content-widthis set, the default width will be set to
For more information take a look at the
image_resize() function which handles the output sizes.
Transformation functions only operate on files in the