Discofork
Repository brief

mifi/lossless-cut

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T19:51:25.653Z
1mo ago

mifi/lossless-cut

LosslessCut is a large, active, non-archived Electron/TypeScript desktop app for extremely fast, lossless video and audio editing built around FFmpeg. It is widely adopted (39,451 stars, 1,916 forks) and still seeing frequent commits as of 2026-03-29, so forks are most interesting if you want to extend a mature media tool with a strong existing user base and documentation footprint.

GitHub
Loading tags...
Stars39,451
Forks1,916
Default branchmaster
Last pushed2026-03-29T15:51:52Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if its added segment-editing and workflow tweaks are more valuable to you than staying current with upstream. For most users, upstream is the safer default because this fork is materially behind and appears maintenance-heavy.

Choose this fork if you want a mostly upstream LosslessCut with a few concrete quality-of-life and platform tweaks. Choose upstream if you want the broadest feature set, freshest fixes, and the least maintenance risk.

Choose this fork only if the segment-shifting workflow changes are exactly what you need and you are willing to give up years of upstream fixes and updates. For most adopters, current upstream is the safer choice.

Prefer upstream unless you specifically need one of the fork’s niche workflow tweaks. This fork looks like a customization branch, not a modernized alternative, and its long inactivity plus large behind count make it a poor default choice for new adopters.

Choose this fork only if localization or downstream translation maintenance is the main goal. If you want the newest LosslessCut features and fixes, upstream is the safer choice.

Prefer upstream unless you specifically need this exact snapshot as a starting point. It adds no visible capabilities, while trailing upstream by 79 commits creates real lag risk.

Adopt this fork only if its specific tweaks solve a real pain point for you; otherwise upstream is the safer choice because it is much more current and likely better supported.

Prefer this fork only if you need its specific custom runtime/package behavior and are willing to own a stale, highly diverged codebase. For most adopters, active upstream is the safer choice.

Choose this fork only if its custom abort/progress/stream-handling behavior matches a concrete need. If you want a current, well-maintained LosslessCut, upstream is the safer choice.

Choose the fork only if you need a legacy branch with a few downstream packaging tweaks. For normal use, upstream is the better choice because it is much more current, actively maintained, and far richer in recent fixes and compatibility work.