head to head · open source

LosslessCut vs imgproxy

LosslessCut has 43,902 GitHub stars, 2,177 forks, 300 open issues and last shipped 6 days ago. imgproxy has 11,080 stars, 776 forks, 67 open issues and last shipped 5 days ago. LosslessCut leads on adoption by 296% (43,902 vs 11,080 stars). LosslessCut is written in TypeScript under GPL-2.0; imgproxy is written in Go under Apache-2.0. LosslessCut has attracted 5% 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.

LosslessCut ★ 44K imgproxy ★ 11K category Miscellaneous

← all 20902 open source comparisons

Side by side

LosslessCut imgproxy
GitHub stars ★ 44K ★ 11K
License GPL-2.0 Apache-2.0
Written in TypeScript Go
Last push 2026-09-14 2026-09-15
Forks ⑂ 2.2K ⑂ 776
Self-hosting Yes Yes
Data ownership Your server Your server

pick LosslessCut if

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

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

LosslessCut is a cross platform desktop application for lossless editing of video, audio, and subtitle files. Built with Electron and TypeScript, it serves as a graphical interface to FFmpeg, enabling users to perform precise cuts, trims, merges, and track manipulations without re encoding, thus preserving original quality. It targets users who need to rapidly process media files—such as raw footage from cameras, drones, or smartphones—where re encoding would be time consuming and degrade fidelity.

read the full LosslessCut 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 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.

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

Frequently asked questions

Is LosslessCut or imgproxy more popular?

LosslessCut has 43,902 GitHub stars and imgproxy has 11,080. LosslessCut has the larger community by that measure.

Are LosslessCut and imgproxy free?

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

What is the difference between LosslessCut and imgproxy?

LosslessCut 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, LosslessCut or imgproxy?

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