head to head · open source

Shotcut vs imgproxy

Shotcut has 15,242 GitHub stars, 1,510 forks, 52 open issues and last shipped 2 days ago. imgproxy has 11,080 stars, 776 forks, 67 open issues and last shipped 5 days ago. Shotcut leads on adoption by 38% (15,242 vs 11,080 stars). Shotcut is written in C++ under GPL-3.0; imgproxy is written in Go under Apache-2.0. Shotcut has attracted 10% as many forks as stars, imgproxy 7%. Shotcut 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.

Shotcut ★ 15K imgproxy ★ 11K category Miscellaneous

← all 20902 open source comparisons

Side by side

Shotcut imgproxy
GitHub stars ★ 15K ★ 11K
License GPL-3.0 Apache-2.0
Written in C++ Go
Last push 2026-09-18 2026-09-15
Forks ⑂ 1.5K ⑂ 776
Self-hosting Yes Yes
Data ownership Your server Your server

pick Shotcut if

  • You weight community size — 15K stars and counting
  • You want the GPL-3.0 license terms
  • Your stack matches C++
  • You value the larger contributor base for long-term maintenance

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

Shotcut is a free, open source, cross platform video editor written in C++ and released under the GPL 3.0 license. It lives in the Qt and MLT ecosystem, using Qt for its application and user interface and MLT as its multimedia authoring framework. It provides regularly built binaries for Linux, macOS, and Windows, and is positioned as an open alternative to Adobe Premiere Pro and DaVinci Resolve (Studio).

read the full Shotcut 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 shotcut opencut vs losslesscut opencut vs sharp opencut vs rembg opencut vs audacity opencut vs filepond 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.

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

Frequently asked questions

Is Shotcut or imgproxy more popular?

Shotcut has 15,242 GitHub stars and imgproxy has 11,080. Shotcut has the larger community by that measure.

Are Shotcut and imgproxy free?

Both are open source. Shotcut is licensed under GPL-3.0 and imgproxy under Apache-2.0. Neither carries a licence fee.

What is the difference between Shotcut and imgproxy?

Shotcut is written in C++ 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, Shotcut or imgproxy?

Choose Shotcut if you want the larger community (15,242 stars) or its GPL-3.0 licence terms. Choose imgproxy if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.