How to cut a video on a Chromebook

Chromebooks are a genuinely awkward place to edit video, and not for the reason people assume. The hardware is usually adequate for a short clip. The problem is that ChromeOS ships almost no editing software, and the three usual escape hatches — the Play Store, the Linux container, and desktop applications — are exactly the things a school or workplace Chromebook has locked down.

Here is an honest map of the options.

What the built-in Gallery app can do

ChromeOS has a Gallery app (it may be called Media or Gallery depending on your version) that opens photos and videos from the Files app. Recent versions include a small video editor with trim, crop, rotate and mute.

Open the video from Files, and if your version has it, you will get a trim bar with a handle at each end. Drag them inward and save.

That covers one job well: shortening a clip from the front and the back. What it does not cover is everything else — removing a section from the middle, changing the speed of a section, or making more than one cut. As with the iPhone’s Photos app, the range selector defines what you keep, not what you delete.

ChromeOS versions differ quite a bit here, and features have arrived and moved around across releases. If the trim bar is not where this describes, that is a version difference rather than a mistake — check what your Gallery app actually offers before assuming a feature is missing.

Why the usual escape hatches often are not available

Android apps. A Chromebook with the Play Store can install a mobile video editor, and several are decent. But managed Chromebooks — the ones handed out by schools and employers — very often have the Play Store disabled by policy, and you cannot turn it back on. On top of that, most capable Android editors are subscription apps that watermark the free tier.

Linux (Crostini). If you can enable Linux, sudo apt install ffmpeg gives you the most powerful video tool there is, and the commands for a lossless trim are here. Two problems: Linux is also commonly disabled on managed devices, and the container gets its own slice of an already-modest amount of RAM. It is a great answer if you have it and a non-answer if you do not.

Desktop software. There is none. ChromeOS does not run Windows or macOS applications, and that is the entire premise of the platform.

Server-based online editors. These work, and they are what most people land on. The cost is that you upload the file — which on a school network is often slow, sometimes blocked, and always means handing a recording to a third party — and free tiers typically add a watermark, a length cap, or a sign-up wall.

The option that fits ChromeOS best

A Chromebook is a browser. So the tool that fits the machine best is one that runs entirely inside the browser, with no install, no account and no upload.

That is what this editor is. FFmpeg — the same library nearly all video software is built on — is compiled to WebAssembly and runs inside the tab. Your file is read off local storage into the page, edited there, and written back out as a download.

To remove a section from the middle:

1. Open the editor and drop your video onto the drop zone, or click to browse the Files app.
2. Scrub the player to where the unwanted section starts.
3. Right-click the timeline and choose Cut, or press + Add edit.
4. Drag the handles to cover exactly what should disappear, or type the start and end seconds.
5. Add more cuts if you need them. You can also mix in speed-ups and slow-downs on the same timeline.
6. Press Apply All Edits and download the result.

Every edit you stacked is applied in one pass, so the footage is re-encoded once no matter how many changes you made.

Three things that specifically matter on a Chromebook:

• Nothing is uploaded, so a slow or filtered school network does not slow the edit down, and the recording never leaves the device. You can verify that yourself in DevTools.
• Nothing is installed, so no policy blocks it.
• It keeps working offline once the page and the WebAssembly engine are in your browser cache.

Being realistic about Chromebook hardware

This is the part most articles skip. Encoding video is genuinely demanding, and a lot of Chromebooks are built around a modest processor and 4 GB of RAM.

What follows from that:

• The whole file lives in memory. The input, the working buffers and the output all sit in the tab’s heap at the same time. On a 4 GB machine, comfortable is measured in hundreds of megabytes, not gigabytes. More on the ceiling here.
• Close other tabs before a long encode. This makes a bigger difference on a Chromebook than on any other kind of machine.
• Cap the output resolution. Setting max resolution to 720p is the single most effective thing you can do. The encoder deals with roughly a ninth of the pixels of a 4K source, so it finishes far sooner and the file lands much smaller. It only ever scales down.
• Choose MP4, not WebM. WebM output has to use VP8, which encodes noticeably slower in WebAssembly than H.264 does. Unless you specifically need a WebM file, MP4 is faster and plays in more places.
• Expect the first run to be slow to start. About 32 MB of WebAssembly engine is downloaded the first time you apply an edit, then cached.

A one-minute 1080p clip is unremarkable on a modest Chromebook. A forty-minute 4K screen recording is not, and no amount of software will change that — the arithmetic is the same whether the encoder is in a browser or not.

Which to choose

If you want to know exactly what the browser is doing with your file before you trust it with a recording, the full pipeline is documented, and the privacy page states precisely what does and does not leave the device.