head to head · open source

rembg vs libvips

rembg has 24,800 GitHub stars, 2,422 forks, 3 open issues and last shipped 11 days ago. libvips has 11,655 stars, 797 forks, 78 open issues and last shipped 3 days ago. rembg leads on adoption by 113% (24,800 vs 11,655 stars). rembg is written in Python under MIT; libvips is written in C under LGPL-2.1. rembg has attracted 10% as many forks as stars, libvips 7%. libvips 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 libvips ★ 12K category Miscellaneous

← all 15422 open source comparisons

Side by side

rembg libvips
GitHub stars ★ 25K ★ 12K
License MIT LGPL-2.1
Written in Python C
Last push 2026-09-08 2026-09-16
Forks ⑂ 2.4K ⑂ 797
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 libvips if

  • You want the libvips feature set and don't need the biggest community
  • You prefer the LGPL-2.1 license terms
  • Your stack matches C
  • You evaluated both and libvips fits your workflow better

full libvips 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 libvips

libvips is a demand driven, horizontally threaded image processing library in C, licensed LGPL 2.1 or later, for developers who need to resize, convert and analyse large images quickly without exhausting memory.

read the full libvips overview →

More in Miscellaneous

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

Related comparisons

opencut vs losslesscut opencut vs audacity opencut vs shotcut opencut vs darktable opencut vs krita opencut vs openshot opencut vs gimp opencut vs kdenlive firecrawl vs godot firecrawl vs gdevelop godot vs home-assistant firecrawl vs monogame firecrawl vs sbox godot vs gdevelop godot vs monogame godot vs sbox firecrawl vs home-assistant firecrawl vs cratedb firecrawl vs gladys-assistant home-assistant vs opencut godot vs cratedb godot vs gladys-assistant home-assistant vs cratedb opencut vs cratedb

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 Krita rembg vs TagStudio rembg vs photoview

Frequently asked questions

Is rembg or libvips more popular?

rembg has 24,800 GitHub stars and libvips has 11,655. rembg has the larger community by that measure.

Are rembg and libvips free?

Both are open source. rembg is licensed under MIT and libvips under LGPL-2.1. Neither carries a licence fee.

What is the difference between rembg and libvips?

rembg is written in Python and libvips in C. 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 libvips?

Choose rembg if you want the larger community (24,800 stars) or its MIT licence terms. Choose libvips if its feature set, stack or LGPL-2.1 licence fits better. Both are self-hostable.