head to head · open source

rembg vs imgproxy

rembg has 24,813 GitHub stars, 2,422 forks, 3 open issues and last shipped 12 days ago. imgproxy has 11,080 stars, 776 forks, 67 open issues and last shipped 5 days ago. rembg leads on adoption by 124% (24,813 vs 11,080 stars). rembg is written in Python under MIT; imgproxy is written in Go under Apache-2.0. rembg has attracted 10% as many forks as stars, imgproxy 7%. imgproxy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (image-processing), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

rembg ★ 25K imgproxy ★ 11K category Miscellaneous

← all 20902 open source comparisons

Side by side

rembg imgproxy
GitHub stars ★ 25K ★ 11K
License MIT Apache-2.0
Written in Python Go
Last push 2026-09-08 2026-09-15
Forks ⑂ 2.4K ⑂ 776
Self-hosting Yes Yes
Data ownership Your server Your server

pick rembg if

  • You weight community size — 25K stars and counting
  • You want the MIT license terms
  • Your stack matches Python
  • You value the larger contributor base for long-term maintenance

full rembg profile →

pick imgproxy if

  • You want the imgproxy feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Go
  • You evaluated both and imgproxy fits your workflow better

full imgproxy profile →

About rembg

Rembg is an MIT licensed Python tool for removing image backgrounds, usable as a CLI, a Python library, an HTTP server, or a Docker container, and aimed at developers, designers, and automated image pipelines that need background removal without depending on a hosted service.

read the full rembg overview →

About imgproxy

imgproxy is a fast, secure standalone HTTP server, written in Go and released under the Apache 2.0 licence, that resizes, processes, and converts images on the fly for web developers, platform engineers, and teams that want image processing to live in a dedicated service instead of inside their applications.

read the full imgproxy overview →

More in Miscellaneous

firecrawl ★ 182K Godot ★ 117K three.js ★ 116K ant-design ★ 100K open-design ★ 97K manim ★ 94K

Related comparisons

opencut vs rembg opencut vs losslesscut opencut vs sharp opencut vs audacity opencut vs filepond opencut vs shotcut opencut vs imagetoolbox opencut vs palmier-pro firecrawl vs godot godot vs three-js firecrawl vs gdevelop firecrawl vs monogame godot vs imgui three-js vs imgui firecrawl vs sbox godot vs bevy firecrawl vs playwright firecrawl vs crawl4ai firecrawl vs novu firecrawl vs searxng firecrawl vs postiz firecrawl vs cap firecrawl vs openseo firecrawl vs keploy

More Photo & Video Editors projects

Compare either of these against the rest of the Photo & Video Editors field.

rembg vs OpenCut rembg vs LosslessCut rembg vs sharp rembg vs Audacity rembg vs filepond rembg vs Shotcut rembg vs ImageToolbox rembg vs palmier-pro rembg vs Darktable rembg vs libvips rembg vs Krita rembg vs TagStudio

Frequently asked questions

Is rembg or imgproxy more popular?

rembg has 24,813 GitHub stars and imgproxy has 11,080. rembg has the larger community by that measure.

Are rembg and imgproxy free?

Both are open source. rembg is licensed under MIT and imgproxy under Apache-2.0. Neither carries a licence fee.

What is the difference between rembg and imgproxy?

rembg is written in Python and imgproxy in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, rembg or imgproxy?

Choose rembg if you want the larger community (24,813 stars) or its MIT licence terms. Choose imgproxy if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.