Use Images in a real application path
Images bindings let Workers transform, resize, and encode images without public image URLs.
A compact Images recipe with config and worker usage in one application path.
Use this as the copyable starter before threading the feature into a larger application.
- Config focus
- bindings.images
- Runtime shape
- Best use
- image transformation/upload paths where the Worker calls the Images binding
Start by wiring the binding clearly in config
Smallest Images config
Build the application flow around the binding
Treat this as the app-level Images path: the route, event handler, or service module receives a real request and uses the binding to do useful work.
Keep product limits, remote ownership, and fallback behavior visible in the code around the binding instead of hiding everything behind a vague utility too early.
- Keep the first example short enough to paste into a new Worker.
- Cloudflare owns hosted image storage, variants, delivery rules, billing, and final transform fidelity.
Transform uploaded image bytes
Keep production boundaries visible
- Config focus: bindings.images.
- Runtime shape: .
- Best use: image transformation/upload paths where the Worker calls the Images binding.
Thread this into the next recipe
Once this smallest path works, add routing, generated types, and feature-specific abstraction in that order.
Previous
Testing Images
Test Images by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.
Next
Media Transformations
Add the Media Transformations config, call from worker code, and start with the local test path Devflare supports.