Android does not have one built-in video editor. It has whichever gallery app your phone’s manufacturer shipped, and on most phones that means one of two things: Google Photos (Pixels and nearly everything that is not a Samsung) or Samsung Gallery. Both can shorten a clip from the ends. Removing a section from the middle — the fumbled sentence, the thirty seconds of nothing — is the operation both of them either dodge or bury, and it is the one people actually search for.
Here is what each built-in editor really does, why the middle cut is the hard case, and how to do it in Chrome on the phone without installing anything.
What Google Photos can do
The Photos trimmer is quick and it does not destroy your original:
- Open the video in Google Photos and tap Edit.
- A filmstrip appears with a handle at each end. Drag the left handle in to cut the beginning, the right handle in to cut the end.
- Tap Save copy. Photos writes a new file and leaves the original alone.
The same screen also has stabilisation, a mute toggle, rotate and crop, and an export-frame option. The exact tab layout moves around between versions, so look for the filmstrip rather than a specific menu name.
What is not there: a split control. There is one range with two handles, and it defines what you keep. There is no way to select a second range, and no way to mark a stretch in the middle for deletion.
What Samsung Gallery can do
Samsung’s editor is more capable than Photos. Beyond the same two-handle trim it offers a playback-speed control, text and stickers, and on recent versions of One UI a way to split the clip and delete pieces, which is the thing you need. Whether your phone has that depends on the One UI version and sometimes the region, so check the editor’s toolbar for a split or scissors control rather than assuming.
Two honest notes if you go that way. Samsung’s speed control applies to the whole clip rather than a section, so it is the wrong tool for “speed up just the boring bit”. And every save is a fresh encode at whatever settings Samsung chooses, which you cannot see or change.
Why the middle is the case built-in editors dodge
Shortening the ends is one operation: pick a start, pick an end, throw away everything outside. Removing a section from the middle is a different shape. The clip has to be cut into two pieces, the piece you do not want discarded, and the remaining two joined so the video simply gets shorter with no gap or freeze where the join was.
That needs a timeline model with more than one range on it, and it needs the join to be frame-accurate on both sides or the edit is visible. Gallery apps are photo libraries with an editor bolted on; they offer the easy operation and leave the harder one to the Play Store, where it is usually behind a subscription and a watermark.
There is a second reason it is harder, and it is about the file rather than the interface. A compressed video is mostly frames that describe changes since the previous frame; only occasional keyframes stand alone. A cut that lands between keyframes has to decode and rebuild the frames around it, which means re-encoding. Ends-only trimming can dodge that by snapping to a keyframe. A middle cut with two boundaries usually cannot. The trade-off is explained properly here.
The workaround people find, and what it costs
The usual advice: trim a copy to keep the first part, trim another copy to keep the second part, then join them in some third app. It works. It also puts the footage through three encodes to remove five seconds, and the third app is exactly the install you were trying to avoid.
Doing it in Chrome on the phone
A section removal is one operation if the tool is built around it. You can do it in Chrome on the phone itself:
- Open the cut tool in Chrome.
- Tap the drop zone. Android’s picker offers your gallery, Files, or Photos — choose the clip.
- Scrub to where the unwanted part begins and add a Cut.
- Drag the two handles to cover exactly the section you want gone, or type the start and end in seconds.
- Add more cuts if there are more bad patches. They are all applied together.
- Tap Apply All Edits. The result lands in your Downloads folder.
The part before the cut and the part after it are joined, so the video gets shorter with no gap, freeze or black flash. Because every cut goes into a single pass, the file is re-encoded once no matter how many sections you removed.
Nothing is uploaded. The file is read from your storage into the browser tab, FFmpeg compiled to WebAssembly does the work in that tab, and the output is handed back as a download. You can verify that yourself with Chrome’s developer tools, and it is why there is no upload wait, no account and no watermark.
Chrome is the browser this has been tested in. Other Chromium-based browsers on Android will generally behave the same, but Chrome is the one to reach for if something is odd.
Honest notes about doing this on a phone
Memory is the real ceiling. The input file, the working buffers and the output all live in the tab’s memory at once. Android is less aggressive than iOS about killing tabs, but Chrome will still discard a tab that asks for more than the phone can give. A clip of a minute or two is comfortable. A twenty-minute 4K recording is where you should move to a laptop, and this guide covers where the limit actually sits.
It is slower than a desktop. Encoding runs on the phone’s CPU inside the browser, and a phone CPU in a WebAssembly sandbox is a long way behind a laptop. Expect the encode to take longer than the clip lasts, sometimes several times longer on a mid-range phone. Keep the screen on and stay in Chrome while it runs; Android may suspend a background tab and lose the work.
The first run fetches the engine. About 32 MB of WebAssembly downloads the first time you apply an edit. On Wi-Fi that is a few seconds; on cellular it is a real wait. It is cached afterwards.
Cap the resolution. If the clip is 4K and the destination is a chat or a social post, setting the max resolution to 720p makes the encode dramatically faster and the file much smaller. It only ever scales down.
File sizes are not what you expect. Phones record at high bitrates, often in HEVC. The output here is H.264 at a fast preset that spends bits rather than time, so a shorter output is sometimes larger than the input. That is a property of the encoder settings, not a sign that anything went wrong. Capping the resolution is the lever that reliably shrinks it.
What else you can do in the same session
Because the timeline treats every edit as a range, the same pass can speed up a slow stretch, slow one down, or drop the audio entirely. Mixing them on one clip still costs a single encode.
If you are on an iPhone instead, the iPhone version of this guide covers the Photos app’s equivalent limits and the Safari file picker. And if you want to understand the machinery before trusting it with a recording, how browser video editing works walks through every stage from the file picker to the download.