imgproxy

A fast and secure standalone server for resizing, processing, and converting images on the fly.

  • Media Applications
  • Other
  • Productivity
  • Tools & Utilities
A fast and secure standalone server for resizing, processing, and converting images on the fly. It works as a drop-in replacement for in-app image processing code, so web applications and media stacks can serve resized and optimized images on demand, with all configuration handled via environment variables.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

82/100 Excellent

Maintained
100last commit 26 days ago
Popular
8111,165 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM
Security check
78no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 5.5/10

Availability: platform listings confirmed today, links checked 8 days ago

GitHub stars
11,165
Open issues
73
Last commit
2026-10-26
Latest release
v4.0.20
License
Apache-2.0
Activity
steady

Checked 21 days ago - source: GitHub (imgproxy/imgproxy)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Choose the port imgproxy listens on Choose the network port (the numbered line other devices connect to) that imgproxy uses to accept requests, then allow it in your router or firewall. Other apps can't ask for resized images if that port is wrong or blocked. source
  • Set imgproxy's startup settings Put the settings imgproxy needs, such as where to listen and where your images come from, into environment variables (name-and-value pairs the app reads at startup) before you start it. If these are missing or wrong, it may use unexpected defaults or fail to serve your images. source
  • Cap the largest source image Set a maximum size for source images, for example 50 MB, when imgproxy downloads them. Without a limit, one very large image can use a lot of memory or make processing slow. source

Fetched 54 days ago - each note links to its source

Alternatives (1)

  • Cloudinary - Image and video API platform for developers, covering uploads, storage, AI-powered transformations, optimization, and delivery for web and…

Checked 51 days ago - source: AlternativeTo

Common questions

Which port should self-hosters expose for imgproxy?

Choose the network port that imgproxy listens on in its configuration, then allow that port in the router or firewall. If the port is wrong or blocked, other apps cannot request processed images.

How should imgproxy startup settings be supplied?

Set the startup settings, such as where to listen and where images come from, as environment variables before starting imgproxy. Missing or wrong values can make it use unexpected defaults or fail to serve images.

Should I limit the size of source images imgproxy downloads?

Yes, set a maximum source image size, for example 50 MB, when imgproxy downloads images. Without a limit, one very large image can use a lot of memory or make processing slow.

How does an imgproxy request work?

Send imgproxy a specially crafted URL containing the source image URL and the desired processing options. It fetches the image, processes it, and serves the resulting image.

Answers sourced from docs.imgproxy.net, github.com, github.com, github.com

Community

Collected 49 days ago - public community threads