--- title: Optimize with Workers description: Use the Images binding to optimize, resize, and manipulate images directly in a Worker from any source. image: https://developers.cloudflare.com/dev-products-preview.png --- > Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/images/llms.txt > Use this file to discover all available pages before exploring further. [Skip to content](#%5Ftop) # Optimize with Workers A [binding](https://developers.cloudflare.com/workers/runtime-apis/bindings/) connects your [Worker](https://developers.cloudflare.com/workers/) to external resources on the Developer Platform, like [Images](https://developers.cloudflare.com/images/), [R2 buckets](https://developers.cloudflare.com/r2/buckets/), or [KV namespaces](https://developers.cloudflare.com/kv/concepts/kv-namespaces/). The Images binding lets you optimize and manipulate images directly in a Worker. Unlike the [URL interface](https://developers.cloudflare.com/images/optimization/transformations/overview/), which requires images to be accessible through a URL, the binding works with raw image bytes. You can pass images from any source, including [Images](https://developers.cloudflare.com/images/storage/upload-images/methods/), [R2](https://developers.cloudflare.com/r2/), a `fetch()` response, or a request body. With the Images binding, you can: * Optimize an image stored in Images or R2 by passing the bytes directly, instead of fetching through a public URL. * Resize an image, overlay a watermark, then resize the combined output into a final result — all in a single chain of operations. * Control the order of operations for optimization parameters. When you use the URL interface, the optimization parameters follow a fixed order of operations. Bindings can be configured in the Cloudflare dashboard for your Worker or in the Wrangler configuration file in your project's directory. Billing Every call to the Images binding counts as one unique transformation. Refer to [Images pricing](https://developers.cloudflare.com/images/pricing/) for more information about billing. ## Setup The Images binding is enabled on a per-Worker basis. You can define variables in the Wrangler configuration file of your Worker project's directory. These variables are bound to external resources at runtime, and you can then interact with them through this variable. To bind Images to your Worker, add the following to the end of your Wrangler configuration file: * [ wrangler.jsonc ](#tab-panel-8631) * [ wrangler.toml ](#tab-panel-8632) JSONC ``` { "images": { "binding": "IMAGES", // i.e. available in your Worker on env.IMAGES }, } ``` TOML ``` [images] binding = "IMAGES" ``` Within your Worker code, use `env.IMAGES.input()` to build an object that can manipulate the image (passed as a `ReadableStream`). ## Methods Note Responses from the Images binding are not automatically cached. Workers lets you interact directly with the [Cache API](https://developers.cloudflare.com/workers/runtime-apis/cache/) to customize cache behavior. You can implement logic in your script to store transformations in Cloudflare's cache. ### `.input(stream)` Creates an optimization handle for an image. All operations begin with this method. Accepts image bytes from any source, including [Images](https://developers.cloudflare.com/images/storage/upload-images/methods/), [R2](https://developers.cloudflare.com/r2/), a `fetch()` response, or a request body. Returns a handle that you can use to chain `.transform()`, `.draw()`, and `.output()` calls. * [ JavaScript ](#tab-panel-8637) * [ TypeScript ](#tab-panel-8638) JavaScript ``` export default { async fetch(request, env) { const imageURL = "https://example.com/photo.jpg"; const response = await fetch(imageURL); return ( await env.IMAGES.input(response.body) .transform({ width: 800 }) .output({ format: "image/webp" }) ).response(); }, }; ``` TypeScript ``` export default { async fetch(request, env) { const imageURL = "https://example.com/photo.jpg"; const response = await fetch(imageURL); return ( await env.IMAGES .input(response.body) .transform({ width: 800 }) .output({ format: "image/webp" }) ).response(); }, }; ``` ### `.transform(options)` Applies optimization parameters to the image, such as `width`, `height`, or `blur`. You can chain multiple `.transform()` calls to control the order that parameters will be applied. For the full list of parameters, refer to [Features](https://developers.cloudflare.com/images/optimization/features/). The example below shows how you can resize an image that is [stored in Images](https://developers.cloudflare.com/images/storage/binding/) by getting the image bytes: * [ JavaScript ](#tab-panel-8633) * [ TypeScript ](#tab-panel-8634) JavaScript ``` // Get the raw bytes of a hosted image const bytes = await env.IMAGES.hosted.image("IMAGE_ID").bytes(); // Resize and transcode the image const response = ( await env.IMAGES.input(bytes) .transform({ width: 400 }) .output({ format: "image/webp" }) ).response(); return response; ``` TypeScript ``` // Get the raw bytes of a hosted image const bytes = await env.IMAGES.hosted.image("IMAGE_ID").bytes(); // Resize and transcode the image const response = ( await env.IMAGES.input(bytes) .transform({ width: 400 }) .output({ format: "image/webp" }) ).response(); return response; ``` ### `.draw(image, options)` Draws an overlay image over another image. The overlay can be a stream of image bytes or another `.input()` chain. You can pass a child `.transform()` function inside this method to resize or manipulate the overlay before drawing it. Accepts `opacity`, `repeat`, and a side (`left`, `right`, `top`, `bottom`). For the full list of draw options and examples, refer to [Draw overlays and watermarks](https://developers.cloudflare.com/images/optimization/transformations/draw-overlays/#options). ### `.output(options)` Generates the final image with the specified output options. Accepts the following options: * `format` — Encodes the image in [a supported format](https://developers.cloudflare.com/images/get-started/limits/#output-formats), such as AVIF, WebP, or JPEG. This method is required — there is no default output format. * `quality` — Specifies the output [quality](https://developers.cloudflare.com/images/optimization/features/#quality--q) of an image for JPEG, WebP, and AVIF formats, expressed as a fixed value or perceptual quality level. * `anim` — Specifies whether to [preserve animation frames](https://developers.cloudflare.com/images/optimization/features/#anim) from input files. Set `anim:false` to convert animations to still images. * [ JavaScript ](#tab-panel-8635) * [ TypeScript ](#tab-panel-8636) JavaScript ``` const response = ( await env.IMAGES.input(stream) .transform({ rotate: 90 }) .transform({ width: 128 }) .transform({ blur: 20 }) .output({ format: "image/avif" }) ).response(); return response; ``` TypeScript ``` const response = ( await env.IMAGES.input(stream) .transform({ rotate: 90 }) .transform({ width: 128 }) .transform({ blur: 20 }) .output({ format: "image/avif" }) ).response(); return response; ``` ### `.info(stream)` Outputs information about the image, such as `format`, `fileSize`, `width`, and `height`. ## Interact with your Images binding locally The Images API can be used in local development through [Wrangler](https://developers.cloudflare.com/workers/wrangler/install-and-update/), the command-line interface for Workers. Using the Images binding in local development will not incur usage charges. Wrangler supports two different versions of the Images API: * A high-fidelity version that supports all features that are available through the Images API. This is the same version that Cloudflare runs globally in production. * A low-fidelity offline version that supports only a subset of features, such as resizing and rotation. To test the low-fidelity version of Images, you can run `wrangler dev`: ``` npx wrangler dev ``` Currently, this version supports only `width`, `height`, `rotate`, and `format`. To test the high-fidelity remote version of Images, you can use the `--remote` flag: ``` npx wrangler dev --remote ``` When testing with the [Workers Vitest integration](https://developers.cloudflare.com/workers/testing/vitest-integration/), the low-fidelity offline version is used by default, to avoid hitting the Cloudflare API in tests. ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/images/","name":"Cloudflare Images"}},{"@type":"ListItem","position":3,"item":{"@id":"/images/optimization/","name":"Optimization"}},{"@type":"ListItem","position":4,"item":{"@id":"/images/optimization/binding/","name":"Optimize with Workers"}}]} ```