mifi/lossless-cut

The problem

Cutting a clip out of a GoPro, drone or screen-recording file usually means loading it into a timeline editor, which re-encodes the whole output: slow, quality-losing, and wasteful when you only want to throw away the boring 90 percent. LosslessCut wraps FFmpeg in a desktop GUI so you can set in/out points and write only the segments you keep, copying the compressed stream straight through.

What's different

The usual route is a full NLE (Premiere, DaVinci Resolve, Kdenlive) or hand-written FFmpeg commands. NLEs give you compositing and effects but pay for it with a re-encode and a heavy project model; raw FFmpeg is fast and exact but has a steep command-line learning curve. LosslessCut sits in between: a player with segment markers on top of stream-copy. The parts that actually set it apart are the remux and track operations (convert container, add/remove/extract audio and subtitle tracks without re-encoding) and the metadata layer around segments — chapters, CSV/EDL import-export, plus a CLI and HTTP API for scripting.

Who it's for

People with lots of raw footage who need rough cuts fast: videographers, drone and action-cam users, podcasters stripping audio, archivists remuxing containers. Also useful for developers who want FFmpeg's lossless operations without memorising flags. Look elsewhere if you need transitions, colour grading, multi-track compositing or frame-accurate cuts on codecs with long GOPs — stream copy can only cut at keyframes, so the cut point is approximate. For precise frame-level edits you need a real editor and a re-encode.

Cost of adoption

Download a desktop build for macOS, Windows or Linux; the README only vouches for its own releases and app-store versions, and flags Flathub as unofficial. A Raspberry Pi armv7l build ships without FFmpeg. Playback relies on Chromium's HTML5 player for common formats and falls back to FFmpeg-assisted playback otherwise, so exotic codecs may preview poorly even though export stays lossless. The project is GPL-2.0 — fine for personal and internal use, a constraint if you plan to bundle or redistribute it commercially. The README is a feature-and-download page; troubleshooting, limitations and requirements live on the external docs site, so read those before committing.

Verdict

LosslessCut is not a new project riding a spike: created in 2016, roughly 45k stars, a 417-point Hacker News thread in 2024, and it still picked up about 526 weekly stars on the TypeScript board in October 2026. That longevity with continuing attention suggests a stable, well-understood tool rather than a fad. It is maintained by one person, which is the main risk to weigh against its maturity. If your job is trimming and remuxing rather than editing, it removes a lot of friction at almost no cost; if your job is actual editing, it is the wrong tool.