LosslessCut is a cross-platform graphical front end for FFmpeg, built around a single idea: trimming, cutting, splitting, merging and remuxing video and audio files without re-encoding them. Its author, Mikael Finstad (mifi, Norway), calls it “the swiss army knife of lossless video/audio editing”. The repository has been on GitHub since 30 October 2016 and by mid-October 2026 had around 44,600 stars and 2,200 forks. The application is written in TypeScript and packaged with Electron, so preview uses Chromium’s HTML5 player while FFmpeg does the real work: an export is an almost direct data copy of the selected streams, which is why a trim that takes a conventional editor minutes to render finishes in well under a second.
The scope is deliberately narrow. A normal video editor re-encodes every frame it touches — slow, and slightly lossy every time. LosslessCut instead copies the compressed packets of the parts you keep, so a 40 GB card dump can be rough-cut down to the good 300 MB with no generation loss at all. That makes it the quickest way to throw away the boring parts of footage from a camera, phone, GoPro or drone before any serious editing happens elsewhere — the official site’s pitch is “shave gigabytes off video and audio files in seconds without loss of quality”.
It is not a non-linear editor. LosslessCut’s model is the segment: you mark start and end points on a zoomable timeline with video thumbnails and an audio waveform, and those segments are what get exported — either as one file per segment or merged into a single output, in whatever order you arrange them. The author says plainly that editing several files together on one timeline is a job for a different tool. What it does have is an unusually complete set of stream-surgery tools: cutting every track equally, enabling or disabling individual tracks, adding audio or subtitle tracks from other files, extracting all tracks from a file into separate outputs, rewriting container formats and metadata, and pruning all non-keyframes for an instant timelapse.
.llc (JSON5) file so a session can be resumed later, with undo/redo via keyboard shortcuts and fully customisable hotkeys.export-start and export-complete API events added in 3.69.0..m3u8), display an embedded DJI GPS track on a map, and strip every non-keyframe to produce a timelapse almost instantly.Speed and integrity. A lossless export writes only the selected packets, so the practical cost is disk I/O rather than CPU — cutting a segment out of a multi-gigabyte recording is effectively instantaneous and needs no GPU. Because nothing is re-encoded, the output has exactly the source’s image quality, so it can be used as a first-pass cutter ahead of a heavier editor with no generation loss. The site’s own users make the point bluntly: one testimonial describes spending 45 minutes exporting 1.5 seconds of video in a normal editor, against under a second here.
The second reason is that it is free, open source (GPL-2.0), local and offline. No account, no upload, no subscription, no watermark and no telemetry — the footage never leaves the machine. The author states the project “will always remain free and open source” and funds it through donations and paid store editions rather than feature locks.
The honest caveats are worth knowing before you start. A truly lossless cut can only begin at a keyframe, so each segment’s start time is normally rounded back to the preceding keyframe — often a few frames earlier than you marked — and the documented workaround is to nudge start points forward, or to try the experimental Smart Cut mode, which works only for some files. Lossy operations are intentionally absent: no resize, watermark, blur, redaction, colour grading, GIF or audio mixing. There is no mass/batch export, so multi-file work is done in separate passes. MPEG-TS (.ts/.mts) footage is better remuxed to MP4/MKV first. FFmpeg does not always preserve metadata perfectly — the docs suggest running exiftool over the result — and there are proprietary data tracks (GoPro’s gpmd, tmcd, fdsc) that can be extracted but not cut. Merging files over ~10 GB can sit at 100% for several minutes before finishing, and the source file is never modified in place by design.
.m3u8) stream without re-encoding.LosslessCut previews through Chromium’s HTML5 player, so the working set is: containers MP4, MOV, WebM, Matroska, OGG and WAV; audio codecs FLAC, MP3, Opus, PCM, Vorbis and AAC; video codecs H.264, AV1, Theora, VP8, VP9 and H.265 (with a hardware decoder). Anything else can still be opened by letting FFmpeg create a low-quality proxy for playback — the actual cut is still performed on the original file, so the export stays lossless.
Cross-platform desktop application: Windows (x64 and ARM64), macOS (Intel and Apple Silicon) and Linux (x64, ARM64 and armv7l for the Raspberry Pi). Official downloads are the GitHub release builds — a .7z for Windows, a .dmg for macOS, AppImage or .tar.bz2 for Linux — alongside the Snap Store on Linux, the Mac App Store and the Microsoft Store. The store editions cost money and are typically a few versions behind the GitHub builds: the author treats the newest GitHub builds as a public beta and moves a release to the stores once he is confident it is solid, so the store version buys convenience, sandboxing and frictionless automatic updates rather than extra features. An unofficial community build exists on Flathub (no.mifi.losslesscut) and is not maintained by the author, who asks people to use only the official sources. Official builds ship their own FFmpeg binary. Older operating systems are only served by older releases — macOS 11 support ended with v3.66, macOS 10.14 and older with v3.58.0, Windows 8.1 and older with v3.52.0, and 32-bit Linux with v3.48.2.
GNU General Public License v2.0 (GPL-2.0). The LICENSE file in the repository is the text of the GNU GPL version 2 (June 1991), and package.json declares "license": "GPL-2.0-only"; GitHub reports the repository licence as GPL-2.0. The software is free of charge with full source available, and the paid App Store and Microsoft Store editions exist because the author asks those who can afford it to pay for a smoother installation and update path — not because any feature is held back.
losslesscut.app · source on GitHub · releases · documentation · Snap Store · nightly builds