超好用的图片处理工具,可配合minio实现如阿里云的图片处理查询

DarthSim 51ae5cbbb1 Update README 3 月之前
.github 7e66b63f35 Set GOFLAGS: -buildvcs=false for lint in CI 7 月之前
.lefthook cc5a45cb39 Fix pre-puch hook on macOS+brew 11 月之前
assets 51ae5cbbb1 Update README 3 月之前
bufpool f1230bf2bb Get rid of rand.Seed() (not needed since Go 1.20) 2 年之前
bufreader 7709b74a5e Bump version 4 年之前
config 7da78ef191 Add IMGPROXY_GRACEFUL_STOP_TIMEOUT config 5 月之前
cookies 3550042a16 Apply new errors processing to more code parts 1 年之前
docker f8d8d47b5b Update base Docker image 5 月之前
docs 92d88fbfbd Docs were moved to https://github.com/imgproxy/imgproxy-docs 2 年之前
errorreport 6b7b3e9179 Replace `*ierrors.Error` with actual data type in Sentry and Honeybadger integrations 1 年之前
etag e31b24931d Update linter and fix linting errors 1 年之前
examples e4bf5e93fb add javascript example for truncated signature (#163) 1 年之前
gliblog 7111083649 Use clang-format style in C files 2 年之前
heroku 5b8c8f2516 Move Docker images to GitHub Container Registry 1 年之前
httprange 95e7584c9a chore: fix some typos in comments (#1272) 1 年之前
ierrors 528ece8da1 Revised errors for better error reporting 1 年之前
imagedata 5257a0e7cf Respond with original 4xx status on 4xx image response; Respond with 502 on 5xx image response 3 月之前
imagemeta 43bd1d73e1 Migrate to golangci-lint v2 11 月之前
imagetype f50176f95b TIFF supports color profiles 6 月之前
imath 7d1f7c903a Use RoundToEven when calculating offsets and watermark size 2 年之前
k6 7f9ec5a5bd k6: Check that body size is not NaN before metering it 2 年之前
logger 46ba23a775 Sort log keys by both priority and name; Add priority for "source" key 6 月之前
memory 25ca0df955 Remove `+build` build constraints as they no longer needed 3 月之前
metrics 207532fe97 Format New Relic and OpenTelemetry metadata values that implement the `fmt.Stringer` interface as strings 5 月之前
options 05e8dd7e12 Add `flip` processing option 3 月之前
processing 05e8dd7e12 Add `flip` processing option 3 月之前
reuseport 25ca0df955 Remove `+build` build constraints as they no longer needed 3 月之前
router 528ece8da1 Revised errors for better error reporting 1 年之前
security a5a587eb39 Add `IMGPROXY_MAX_RESULT_DIMENSION` config and `max_result_dimension` processing option 8 月之前
structdiff 0bf347b1fe Refactor `structdiff` package 1 年之前
svg 6f52eca85e Fix possible infinite loop during SVG sanitization 5 月之前
testdata 810cad5d26 Calculate all sizes at the start of processing pipeline 9 月之前
transport 8a62a87978 Return 404 for missing GCS objects (#1576) 3 月之前
version 62224b4414 Bump version 4 月之前
vips 05e8dd7e12 Add `flip` processing option 3 月之前
.clang-format 7111083649 Use clang-format style in C files 2 年之前
.dockerignore 7e3b838c45 Use native Go in Docker build 4 年之前
.gitignore e5d528d60a Add Makefile 5 月之前
.golangci.yml 43bd1d73e1 Migrate to golangci-lint v2 11 月之前
BENCHMARK.md 40aaf353ac Replace old benchmark results with a link to the blog article with new results 1 年之前
CHANGELOG.md e853afd60e Update changelog 3 月之前
LICENSE 0c006ce61e Initial commit 8 年之前
Makefile 55aaa534cf Upgrade deps 5 月之前
NOTICE d1c607bdc1 Add Highway to NOTICE 2 年之前
README.md 51ae5cbbb1 Update README 3 月之前
SECURITY.md 947d65cf29 Create SECURITY.md (#1080) 3 年之前
app.json 5b8c8f2516 Move Docker images to GitHub Container Registry 1 年之前
build-docs-sitemap.sh b75b6cb5a2 Add robots.txt and sitemap.txt 4 年之前
errors.go 528ece8da1 Revised errors for better error reporting 1 年之前
fix_path.go 30f744e116 Try to fix path if signature is invalid 3 年之前
go.mod 1baa6b5bc9 Bump github.com/go-viper/mapstructure/v2 from 2.3.0 to 2.4.0 5 月之前
go.sum 1baa6b5bc9 Bump github.com/go-viper/mapstructure/v2 from 2.3.0 to 2.4.0 5 月之前
healthcheck.go aaaf1c706d Normalize IMGPROXY_PATH_PREFIX and IMGPROXY_HEALTH_CHECK_PATH 2 年之前
heroku.yml 6ce4201bb0 Add build arg to Heroku Dockerfile 6 年之前
landing.go 4c2e43c4f9 Update landing 9 月之前
lefthook.yml fa3b1d9c71 Exclude x.com from lychee check 1 年之前
logo.svg f0bd65aabf Optimize logo 6 年之前
main.go d02a678229 Call vips.Shutdown() as close to exit as possible 5 月之前
pprof.go 25ca0df955 Remove `+build` build constraints as they no longer needed 3 月之前
processing_handler.go 8967bf7f82 Fix Vary header when JPEG XL supoprt detection is enabled 7 月之前
processing_handler_test.go 43bd1d73e1 Migrate to golangci-lint v2 11 月之前
server.go 7da78ef191 Add IMGPROXY_GRACEFUL_STOP_TIMEOUT config 5 月之前
stream.go 4d19d89ac0 Ignore http.ErrBodyNotAllowed error during streaming 6 月之前

README.md

imgproxy logo

Website | Blog | Documentation | imgproxy Pro

Docker Bluesky X X Discord

CI


imgproxy is a fast and secure standalone server for resizing, processing, and converting images. The guiding principles behind imgproxy are speed, security, and simplicity.

imgproxy is able to quickly and easily resize, process, and optimize images on the fly, and it's well-equipped to handle a large amount of image processing. imgproxy is a drop-in replacement for all the image processing code inside your web application (such as using image processing libraries or calling command-line tools). With imgproxy, you don’t need to repeatedly re-prepare images to fit your design every time it changes, as imgproxy does this on demand.

To get an even better introduction and to dive deeper into the nitty-gritty details, check out this article by Evil Martians: imgproxy: Resize your images instantly and securely

imgproxy demo Photo by Joshua Patton

✨ Features

imgproxy is packed with features to the brim to cover all your image processing needs:

Feature imgproxy OSS imgproxy Pro
Image formats Basic formats: JPEG, PNG, GIF, WebP, AVIF, JPEG XL, and more Preview generation for video, PDF, and Photoshop documents
Processing Resizing, cropping, rotating, watermarking, filters Getting image info, advanced watermarking, color adjustment
Optimization Color profile and metadata stripping, PNG quantization Advanced compression settings, GIF to MP4 conversion, SVG minification
Smart features Simple smart cropping, auto-quality by file size Object detection, advanced smart cropping, auto-quality by SSIM, best format selection

Check out the full feature list for more details.

🛠️ How it works

imgproxy works as a standalone HTTP server. You provide it with a source image URL and a set of processing options via a specially crafted URL, and imgproxy fetches the image, processes it according to your specifications, and serves the resulting image back to you. You can use imgproxy URLs directly in your HTML, CSS, or JavaScript code, just like you would with any other image URL.

This way, imgproxy offloads all the image processing work from your application. The only thing your application needs to do is to generate imgproxy URLs with the desired processing options.

How imgproxy works scheme

⚖️ Main principles

Simplicity

Keep it simple, stupid!

We believe that software should be simple yet powerful. If your grandma can't get it up and running, you should make it simpler. That's why we designed imgproxy to be ready to use in a couple of minutes with minimal configuration. Check out the Getting Started guide to see how easy it is.

No code is better than no code.

We believe in the single responsibility principle. If something can be done better outside of imgproxy, we won't reinvent the wheel. As a couple of examples:

  • HTTPS support sounds like a must-have feature for a web server. However, imgproxy will live behind a CDN, a load balancer, or a reverse proxy in a production environment anyway, so there is no need to implement HTTPS support inside imgproxy itself.
  • Rounding image corners or applying masks sounds useful, but doing this with CSS is way easier and more flexible.

Speed

We strive to tune every little piece of imgproxy to make it as fast as possible.

imgproxy takes advantage of probably the most efficient image processing library out there – libvips. It’s scary fast and comes with a very low memory footprint. Our extensive experience with libvips has enabled us to optimize our image-processing pipeline to its maximum.

You can take a look at some benchmarking results and compare imgproxy with some well-known alternatives in our benchmark report.

Security

Image processing is a wide attack surface. That's why we treat security very seriously. imgproxy offers several security measures that enable you to strike the optimal balance between security and usability for your specific use case. For example:

  • imgproxy supports signing image URLs to prevent abusing your image processing server for denial-of-service attacks or simply using it for the attacker's own needs.
  • imgproxy checks the image type before fully downloading it to prevent unwanted resource consumption.
  • imgproxy checks the real image dimensions before decoding it to prevent so-called "image bombs", like those described in this doc.
  • imgproxy supports authorization by HTTP header to prevent direct access to it, bypassing your CDN or caching server.
  • imgproxy allows restricting image sources, maximum image file size, processing options, etc.

Check out our documentation for more details on security features.

🚀 Getting started

The easiest and recommended way to run imgproxy is using Docker. It's just a matter of a single command:

docker run -p 8080:8080 -it ghcr.io/imgproxy/imgproxy:latest

That's it! imgproxy is ready to accept image processing requests at http://localhost:8080.

Check out the Getting Started guide for a step-by-step tutorial on how to get your first image processed with imgproxy.

📚 Documentation

You can find the full documentation at docs.imgproxy.net.

💙 Supporting imgproxy

imgproxy is not a side project; it's what we do for a living. We work hard to make it better every day. If you find imgproxy useful and want to support its development, here are some ways you can do that:

  • imgproxy Pro subscription. imgproxy Pro is a more feature-rich version of imgproxy. By subscribing to imgproxy Pro, you not only support the development of imgproxy but also get access to advanced features and priority support.
  • Sponsorship. If you don't need the Pro features but still want to support the project, consider sponsoring us on GitHub Sponsors.
  • Spread the word. If you like imgproxy, give it a shoutout. We don't spend much on marketing, and imgproxy's popularity is primarily a result of our valued users sharing it on social media and blogs.

🙏 Special thanks

Many thanks to:

📄 License

imgproxy is licensed under the MIT license.

See LICENSE for the full license text.

⚠️ Security Contact

To report a security vulnerability, please contact us at security@imgproxy.net. We will coordinate the fix and disclosure.