OSS Tanbou

offload application image processing to a standalone HTTP service

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
11,101
Primary language
Go
License
Apache-2.0
Repository last updated
Sep 28, 2026
On this page

Overview

imgproxy accepts URLs containing a source image and processing options, then performs resizing, cropping, rotation, format conversion, and optimization on demand. Its Go and libvips architecture moves image-processing workloads out of application code.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Express resize, crop, and format conversion through URLs

Applications generate imgproxy URLs with the desired processing options while the service handles fetching, processing, and serving the image.

Sources: [2]

Use libvips for fast, memory-efficient processing

libvips provides a high-performance processing engine suitable for concentrating large image workloads in a dedicated service.

Sources: [2]

Best fit

Fits applications that want image processing outside the main codebase

It works well for shared thumbnailing, responsive-image generation, and format optimization across multiple applications.

Sources: [2]

Before adoption

Public endpoints should use URL signing and resource limits

The README recommends signed URLs, source restrictions, maximum file sizes and dimensions, authorization headers, and related controls against abuse and image bombs.

Sources: [2]

The OSS and Pro editions have different feature sets

Video, PDF, and Photoshop previews, advanced smart cropping, and some advanced compression features are listed under the Pro edition.

Sources: [2]

Official sources

  1. [1]imgproxy/imgproxy repository(2026-09-30)
  2. [2]imgproxy README(2026-09-30)
  3. [3]imgproxy Apache-2.0 license(2026-09-30)
  4. [4]imgproxy v4.0.16 release(2026-09-30)
Supplemental curator note

imgproxy moves application image processing into a standalone Go HTTP service. The OSS edition is Apache-2.0, while imgproxy Pro adds features such as video and PDF previews and advanced smart cropping. Production deployments should use signed URLs, source restrictions, size and dimension limits, and a CDN or reverse proxy.

Try it in 3 steps

  1. 1

    Pull the imgproxy v4.0.16 image

    Get the container image pinned to the release version.

    docker pull ghcr.io/imgproxy/imgproxy:v4.0.16
  2. 2

    Start imgproxy

    Run the standalone image-processing server on local port 8080.

    docker run -d --rm --name imgproxy -p 8080:8080 ghcr.io/imgproxy/imgproxy:v4.0.16
  3. 3

    Check the health endpoint

    A response of imgproxy is running confirms startup. Configure URL signing and source restrictions before public deployment.

    curl -fsS http://localhost:8080/health
Check the official README

Growth

Growth trends · Last 30 days

11,101 Stars

Trend data is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • avif
  • crop-image
  • docker
  • golang
  • image
  • image-processing
  • image-server
  • jpeg
  • jpeg-xl
  • jxl
  • libvips
  • microservice
Stars
11,101
Forks
777
Watchers
73
Open issues
68
Owner type
Organization
Primary language
Go
License
Apache-2.0
Repository last updated
Sep 28, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?