Join early. Pay less. Shape what’s next.
buff.ly/KThe99s
18.02.2026 14:15
👍 1
🔁 0
💬 0
📌 0
Join early. Pay less. Shape what’s next.
buff.ly/KThe99s
Early access includes:
• pre-release imgproxy Pro v4 builds
• a direct feedback channel with the team
• early adopter pricing
Rolling out in batches.
imgproxy v4 is almost here.
We’re looking for teams ready to test v4 before the public release and share feedback. So we’re opening early access for the Pro version.
buff.ly/KThe99s
Curious what imgproxy actually is and when it makes sense to use it?
We wrote a short overview for SourceForge that explains the core ideas.
Huge thank you to the miro.com team for trusting imgproxy with their production image pipeline.
We almost forgot to celebrate this one — but hey, 10K GitHub stars! Thanks to everyone who helped us get here. Now… let’s make it 20K, shall we?
Excellent breakdown of modern image optimization strategies — especially for teams dealing with high volumes of user-generated media.
The author walks through all the classic dead-ends… and ends up with a client-intelligent, cache-first architecture where imgproxy plays a key role.
New patch release: v3.30.1
Recommended for an update to imgproxy Pro v3.30.0 users.
Release notes:
We’re this 🤏 close to 10K GitHub stars!
If imgproxy ever saved you from writing your own image pipeline, now’s the time to smash that ⭐
Help us cross the line: buff.ly/lDxSKoB
London meets imgproxy! Our long-time friend, Olga Rusakova , dropped knowledge bombs about open source promotion at @openuk.bsky.social meetup, sharing real-world imgproxy insights and golden tips!
Pro users can also set a compression preset dynamically via the webp_options processing option.
buff.ly/FOvE5TF
New WebP compression configs in imgproxy v3.29.0:
• IMGPROXY_WEBP_EFFORT — balance compression speed vs compression ratio
• IMGPROXY_WEBP_PRESET — choose a compression preset like photo, drawing, icon, etc.
buff.ly/sSglR2p
Need to feed your image to a system that only accepts PDFs?
imgproxy Pro can cover you back here! Just set the output format to `pdf` and imgproxy will create a PDF file with your image embedded in it.
New in imgproxy Pro: `crop_aspect_ratio`
You’ve got saved crop coordinates, but need them in different aspect ratios for different layouts? Now you can tweak the ratio on the fly—no recalculations, no new data.
Docs buff.ly/8oCzGLT
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.
Better observability in imgproxy 🔭
We already play nicely with major monitoring and error trackers out of the box. The latest release makes signals richer and incidents faster to untangle.
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
New security measures in imgproxy 🔐
Signed URLs remain best practice. But if you can’t use them (hello, frontend-only flows), we’ve added guardrails so your instance stays tight. Jump into the thread.
