head to head · open source

OpenCut vs imgproxy

OpenCut has 89,891 GitHub stars, 8,880 forks, 378 open issues and last shipped 1 months ago. imgproxy has 11,080 stars, 776 forks, 67 open issues and last shipped 5 days ago. OpenCut leads on adoption by 711% (89,891 vs 11,080 stars). OpenCut is written in TypeScript under MIT; imgproxy is written in Go under Apache-2.0. OpenCut 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.

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

OpenCut ★ 90K imgproxy ★ 11K category Miscellaneous

← all 20902 open source comparisons

Side by side

OpenCut imgproxy
GitHub stars ★ 90K ★ 11K
License MIT Apache-2.0
Written in TypeScript Go
Last push 2026-08-10 2026-09-15
Forks ⑂ 8.9K ⑂ 776
Self-hosting Yes Yes
Data ownership Your server Your server

pick OpenCut if

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

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

OpenCut is a free, MIT licensed video editor that runs in the browser and is being rebuilt to serve web, desktop, and mobile from a single codebase, aimed at creators who want an open source alternative to CapCut.

read the full OpenCut 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 losslesscut opencut vs sharp opencut vs rembg opencut vs audacity opencut vs filepond opencut vs shotcut opencut vs imagetoolbox opencut vs palmier-pro home-assistant vs opencut opencut vs fleetbase 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

More Photo & Video Editors projects

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

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 OpenCut vs Darktable OpenCut vs libvips OpenCut vs Krita OpenCut vs TagStudio

Frequently asked questions

Is OpenCut or imgproxy more popular?

OpenCut has 89,891 GitHub stars and imgproxy has 11,080. OpenCut has the larger community by that measure.

Are OpenCut and imgproxy free?

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

What is the difference between OpenCut and imgproxy?

OpenCut is written in TypeScript 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, OpenCut or imgproxy?

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