imgproxy vs ImageFlow
Image processing and delivery projects compared
imgproxy is an HTTP service that transforms images on demand from URL-based instructions. ImageFlow is a self-hosted platform for managing image collections and delivering optimized versions, with a web interface, tagging, and storage options.
imgproxy: Resize and Convert Images on Demand
imgproxy is a standalone HTTP server that resizes, transforms, and converts images when requested. It suits teams that want to move image processing out of their application and serve optimized images through a URL-based API.
ImageFlow: Manage and Distribute Optimized Images
ImageFlow is a self-hosted image management and delivery platform with a Go backend and Next.js interface. It converts images to modern formats, serves them based on browser and device preferences, and supports local or S3-compatible storage.
| imgproxy | ImageFlow | |
|---|---|---|
| Language | Go | TypeScript |
| License | Apache-2.0 | MIT |
| Stars | 11.1k | 611 |
| Forks | 777 | 57 |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- imgproxy focuses on resizing, cropping, filtering, and converting images per request; ImageFlow adds uploads, collection management, tags, and filtering.
- imgproxy accepts processing options in request URLs; ImageFlow negotiates formats and orientation based on browser and device preferences.
- imgproxy is written in Go; ImageFlow uses a Go backend and Next.js interface, while its repository metadata lists TypeScript.
- imgproxy is licensed under Apache-2.0; ImageFlow is licensed under MIT.
- imgproxy recommends Docker and can sit behind a CDN, load balancer, or reverse proxy; ImageFlow documents Docker Compose for its frontend, backend, and Redis services.
- imgproxy has 11.1k stars and 777 forks; ImageFlow has 611 stars and 57 forks.
Choose imgproxy if you…
- need an HTTP endpoint for on-demand image transformations from URL instructions.
- want controls such as signed URLs, source restrictions, and processing limits.
- need to offload image processing from application code or deliver converted image formats.
Choose ImageFlow if you…
- want a self-hosted image library with a browser interface for uploads and browsing.
- need tagging, filtering, and local or S3-compatible image storage.
- want image delivery that negotiates formats and orientation based on client preferences.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.