Imageoptim cli how to#

In this example, we map some precomposed IO queries to general labels like 'large', 'medium', and 'small', so that the image request from the client is ?class=large rather than ?crop=16:9,smart&width=640. Instead, consider implementing transform classes. For example, allowing raw image transform parameters to be accepted on inbound client requests may allow an end users to gain access to a higher resolution of your source images than you had intended. You may prefer not to expose image optimization parameters publicly. The following error scenarios will prevent the image from being processed: If an error occurs during image processing, a fastly-io-warning or fastly-io-error header is added to the response.

Imageoptim cli how to#

In this demo, we also show how to calculate the size ratio between the original image and the transformed image by post processing the fastly-io-info header, dividing ofsz by ifsz, and multiplying by 100 to yield a percentage. This header provides detail on the input format ( ifmt), dimensions ( idim), and size in bytes ( ifsz), and also the output format ( ofmt), dimensions ( odim), and size in bytes ( ofsz).Ĭlick 'RUN' on the interactive demo below to create an ephemeral Fastly service and make a request through it for an image of former US president Barack Obama. These requests are considered to be different for the purposes of caching transformed images and will result in different cache objects, but the request to origin is image.png (with no query params).įastly-io-info : ifsz=108501 idim=827x788 ifmt=jpeg ofsz=13066 odim=300x286 ofmt=jpeg The original image is only requested and cached once, even if distinct requests might demand versions of the image that are transformed differently.įor example, a user on a desktop device triggers a request for image.png?width=1600, while a different user on a mobile device requests image.png?width=400. If an x-fastly-imageopto-montage header is specified, all other IO params and headers are ignored. format auto optimize quality profile level.width height dpr fit resize-filter disable enable.Overlay one image on top of another image.Īlthough the parameters can be specified in any order, we normalize the transformation sequence within our system to the following order: Specify the resize filter used when resizing images.Ĭombine up to four images into a single displayed image. Optimize the image to the given compression level for lossy file formatted images. Specify the profile class of application when converting to video. Remove pixels from an image before any other transformations occur. Specify the level constraints when converting to video.Īutomatically apply optimal quality compression.Ĭhange the cardinal orientation of the image. Specify the output format to convert the image to.Įxtract the first frame from an animated image sequence.

Set how the image will fit within the size bounds provided. Serve correctly sized images for devices that expose a device pixel ratio.Įnable functionality that is disabled by default. Increase the size of the canvas around an image.ĭisable functionality that is enabled by default. For example, the following query string will direct the IO processor to resize the image to 300 pixels wide and crop it to a 16:9 ratio, centered on the most important visual content, including the detection of faces:Įnable optimization features automatically. Often the default transformations will save a significant amount of data without any further effort, but you can customize the behavior with query parameters and headers. The original Vary response header from origins will be removed by IO.If the source image contains orientation metadata, this orientation will be applied directly to the image data and metadata will be removed.If the image doesn't contain an ICC profile, a default profile is added. If the image contains an ICC profile, the data will be applied directly to the image to ensure color output is correct.All metadata (for example, EXIF, XMP, or ICC) will be removed.The quality of jpg, pjpg, or webp images will be set to the value specified in the IO web interface.Many of these can be overridden or further customized by providing explicit configuration directives as query params or headers: Default behaviorĮnabling IO will activate a set of standard transformations and filters intended to provide 'good defaults' that will not change the image's dimensions or visual fidelity.

WARNING: IO will only process requests that are eligible for caching.