head to head · open source

imgproxy vs OpenShot

imgproxy has 11,080 GitHub stars, 776 forks, 67 open issues and last shipped 5 days ago. OpenShot has 6,523 stars, 812 forks, 418 open issues and last shipped today. imgproxy leads on adoption by 70% (11,080 vs 6,523 stars). imgproxy is written in Go under Apache-2.0; OpenShot is written in Python under a custom or non-standard licence. imgproxy has attracted 7% as many forks as stars, OpenShot 12%. OpenShot was the more recently maintained of the two, and both are self-hostable with no licence fee.

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

imgproxy ★ 11K OpenShot ★ 6.5K category Miscellaneous

← all 20902 open source comparisons

Side by side

imgproxy OpenShot
GitHub stars ★ 11K ★ 6.5K
License Apache-2.0 Custom / other
Written in Go Python
Last push 2026-09-15 2026-09-20
Forks ⑂ 776 ⑂ 812
Self-hosting Yes Yes
Data ownership Your server Your server

pick imgproxy if

  • You weight community size — 11K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full imgproxy profile →

pick OpenShot if

  • You want the OpenShot feature set and don't need the biggest community
  • You prefer the Custom / other license terms
  • Your stack matches Python
  • You evaluated both and OpenShot fits your workflow better

full OpenShot profile →

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 →

About OpenShot

OpenShot Video Editor is a free, cross platform, open source video editor for Linux, Mac, and Windows, built for hobbyists, educators, and small production teams who want timeline based editing and animation without a commercial subscription.

read the full OpenShot 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 sharp opencut vs rembg 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.

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

Frequently asked questions

Is imgproxy or OpenShot more popular?

imgproxy has 11,080 GitHub stars and OpenShot has 6,523. imgproxy has the larger community by that measure.

Are imgproxy and OpenShot free?

Both are open source. imgproxy is licensed under Apache-2.0, and OpenShot has no licence declared in this registry. Both are free to self-host.

What is the difference between imgproxy and OpenShot?

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

Which should I choose, imgproxy or OpenShot?

Choose imgproxy if you want the larger community (11,080 stars) or its Apache-2.0 licence terms. Choose OpenShot if its feature set, stack or Custom / other licence fits better. Both are self-hostable.