Pro users can also set a compression preset dynamically via the webp_options processing option.
buff.ly/FOvE5TF

Fewer blind spots. Faster RCA. Smarter scaling. Update imgproxy and let your dashboards do the talking.
Check out our docs for more info about monitoring!
buff.ly/C2zS12L

The new "Source Image Origin" attribute is now set for error reports to the supported error trackers to speed up debugging of download issues.

The `workers` and `workers_utilization` metrics are now sent to all supported metric systems — perfect for autoscaling and capacity planning.

We also added the `source_image_url` attribute to the `downloading_image` tracing spans and `processing_options` to the `processing_image` spans. Both attributes were previously available only in root spans.

We added the `source_image_origin` attribute to the root and `downloading_image` tracing spans for easier tracking of problematic image sources.

Reality check
These features are defense-in-depth, not a free pass. If you can sign URLs—do it. If you can’t, these rails keep the train on the tracks.

Recommended baseline (when running unsigned)
Choose limits that match your app: restrict allowed image sources, set a ceiling on result dimensions, allow only the URL options you rely on, and restrict pipeline chaining. Small surface, big safety.

Break the chain
Limit how many pipelines a single URL can stack. This shuts down “matryoshka” chains that waste CPU and invite abuse.
Docs buff.ly/BgO99ig

Presets still win
You can still use “forbidden” options inside presets. Expose a small, safe public API; keep complex pipelines behind the curtain.

Allow only what you trust
Whitelist which processing and info options are valid in the URL. Anything else is rejected. Keep the public surface tiny; keep power server-side.
Docs buff.ly/TSQdDem

Cap the size
Set a hard ceiling for the resulting image’s largest side. Anything bigger is automatically downscaled. No surprise mega-bitmaps.
Docs buff.ly/Rbr7WlM