imgproxy
Fast and secure standalone server for resizing and processing images.
Open the official app on imgproxy.net
This tool is hosted by its maintainers. Click below to open imgproxy.net in a new tab — it's their official demo.
Browse image & tools tools →What's next with imgproxy?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is imgproxy?
imgproxy is an open-source, self-hosted image processing server designed to resize, optimize, and convert images on-the-fly. It enables developers to dynamically adjust image dimensions, formats, and quality without pre-preparing multiple variants, streamlining workflows and reducing infrastructure costs. Targeted at developers, startups, and enterprises, imgproxy addresses the challenge of managing image variations across platforms, ensuring fast load times and secure handling of user-uploaded content. By eliminating reliance on third-party SaaS services, it provides control over data privacy and operational expenses while maintaining high performance. The tool excels in scenarios requiring real-time image manipulation, such as responsive web design, social media content delivery, and e-commerce product visualization. Its MIT license and Docker/ Linux package distribution model make it accessible for deployment on private servers or cloud environments. imgproxy’s focus on speed and security makes it ideal for applications where latency and data protection are critical, such as healthcare or financial platforms handling sensitive media.
How it works
imgproxy is a standalone server that processes images in real-time using URL parameters. It replaces custom image processing code in web applications by handling resizing, format conversion, and optimization through a single endpoint. Developers integrate imgproxy by appending parameters to image URLs, allowing dynamic adjustments without modifying backend logic. The tool is designed for use cases where image variants are needed on-demand, such as responsive web design or multi-device compatibility. It eliminates the need for pre-generated image sizes, reducing storage overhead and simplifying deployment. imgproxy supports resizing images to specified widths and heights, converting between JPEG, PNG, and WebP formats, and applying quality optimizations. It also provides secure handling of user-uploaded content through signed URLs and access controls. For example, an image URL like `https://example.com/image.jpg?w=300&h=200` would return a resized 300x200 version of the original.
How to use it
- 1Install imgproxy via Docker or Linux packages from its GitHub repository. 2. Configure the server to connect to your existing image storage (e.g., Amazon S3, local filesystem). 3. Generate processed image URLs by appending parameters like `w=width`, `h=height`, `q=quality`, and `f=format` to the original image URL. 4. Test the URLs in a browser or application to verify resizing and format conversion. Practical tips: Use Docker for quick local testing, enable HTTPS for secure data transfer, and leverage the built-in image optimization features to reduce file sizes without sacrificing quality.
What it can do
- image resizing proxy
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/imgproxy/imgproxy
- license: MIT — free to use
- privacy: Self-hosted — you control your data
Limitations
- Limited support for advanced image filters compared to commercial tools
- Requires manual configuration for complex processing pipelines
- No built-in caching mechanism for frequently accessed image variants
- Dependent on external storage solutions for original image files
- May introduce latency for extremely large image files
Understanding the result
Fast and secure standalone server for resizing and processing images.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (imgproxy/imgproxy)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with imgproxy/imgproxy. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- MIT License
Upstream project
Frequently asked
What is imgproxy used for?
imgproxy is used to dynamically resize, convert, and optimize images on-the-fly through URL parameters. It eliminates the need for pre-generated image variants by processing requests in real-time, reducing storage costs and simplifying deployment. Developers integrate it by replacing hardcoded image URLs with processed versions that adjust to user needs.
How does imgproxy handle image processing?
imgproxy processes images server-side using a combination of image manipulation libraries and optimized algorithms. When a request is made with parameters like `w=500` or `q=85`, the server retrieves the original image from configured storage, applies the requested transformations, and serves the result directly. All processing is done in-memory to minimize disk I/O, ensuring low-latency responses.
How do I resize an image using imgproxy?
To resize an image, append parameters to the original URL. For example, to resize an image to 800x600 pixels and convert it to WebP format, use `https://your-domain.com/image.jpg?w=800&h=600&f=webp`. Replace `your-domain.com` with your imgproxy server address. The server will process the request and return the modified image.
How does imgproxy compare to Cloudinary or Imgix?
Unlike Cloudinary or Imgix, imgproxy is self-hosted and open-source, giving full control over data and infrastructure. It offers similar resizing and format conversion capabilities but lacks some advanced features like AI-powered image enhancements or built-in CDN integration. imgproxy is ideal for organizations prioritizing privacy and customization over out-of-the-box features.
What should I do if imgproxy returns a 404 error?
A 404 error typically indicates the original image file is missing from the configured storage. Verify that the image path is correctly specified in your imgproxy configuration and that the file exists in the linked storage (e.g., S3 bucket or local directory). Check for typos in the URL and ensure the server has proper permissions to access the image files.