A practical guide to trimming video without uploading it
Video Trim is a free online video trimmer that cuts footage inside your browser. Choose a file, mark the part you want to keep, select Lossless or Accurate, and export an MP4. There is no account to create, no watermark added to the result, and no application server receiving your video.
That last point matters when the source is more than a disposable social clip. It may be an unreleased product demo, a recording of a client call, a family video, classroom footage, or material covered by a confidentiality agreement. A conventional cloud editor must receive the file before it can do any work. This tool uses FFmpeg compiled to WebAssembly, so the editing engine runs on your device instead.
The trimmer is intentionally focused. It does not pretend to replace a multi-track editor. Its job is to remove an unwanted beginning or ending, extract one useful section, and give you a downloadable clip with as little friction as possible. The guide below explains how to get a clean result, which export mode to choose, what the format labels really mean, and what to try if a file does not work.
Implementation reviewed by the Video Trim Editorial Team on 6 November 2026. Read our editorial and testing policy.
Quick technical specifications
| Specification | Details |
|---|---|
| Processing architecture | 100% client-side in-browser execution via FFmpeg 0.12.6 compiled to WebAssembly (ffmpeg.wasm) |
| Server upload & storage | None — source files are read via local Blob URLs and never leave your device |
| Accepted input containers | MP4, M4V, MOV, WebM, MKV, OGG, AVI (verified by file magic bytes) |
| Export modes | Lossless (-c copy stream copy, zero quality loss) or Accurate (libx264 CRF 20, veryfast preset + AAC 192 kbps) |
| Audio controls | Keep original audio, transcode to AAC 192 kbps, or strip audio completely (-an mute) |
| File size ceiling | No server cap; bounded by 32-bit browser WebAssembly memory (typically 500 MB–2 GB on desktop, lower on mobile) |
| Cost, watermark & signup | 100% free, no watermark added, no account required |
How local browser trimming compares to cloud and desktop editors
| Feature | Video Trim (Local Browser) | Typical Cloud Online Trimmers | Desktop NLE Software |
|---|---|---|---|
| File upload required | No (0 bytes uploaded) | Yes (full video uploaded to remote servers) | No (runs locally) |
| Installation required | No (runs in Chrome, Firefox, Safari, Edge) | No | Yes (hundreds of MB to several GB) |
Lossless stream copy (-c copy) | Yes (instant cut on keyframes) | Rare (most re-encode every export) | Varies (often requires full render) |
| Free-tier watermark | Never | Common on free tiers or above 720p/1080p | None on free tools (QuickTime, DaVinci) |
| Practical file size limit | Browser RAM ceiling | Often capped at 50 MB–500 MB on free plans | Unlimited (disk space only) |
How to trim a video online in four steps
- Choose a video. Select the upload area or drag a file onto it. The initial file check recognises MP4, M4V, MOV, WebM, MKV, OGG and AVI containers. A recognised container can still hold an unsupported codec, so this is a safety check rather than a guarantee that every file will decode.
- Set the start and end. Drag the two timeline handles to surround the section you want to keep. For a precise time, enter seconds in the Start and End fields. Decimal values such as
12.5are accepted. - Preview the selection. Move the playhead and use the play button to check the opening and closing moments. Playback stops at the end marker and returns to the selected start, which is useful when checking a short transition more than once.
- Choose a mode and export. Use Lossless when speed and preserving the original encoded streams matter most. Use Accurate when the clip must begin on the selected frame. Select Trim Video, wait for local processing to finish, then select Download.
The downloaded filename is trimmed_video.mp4. Play it before deleting or moving the source. Check the first second, the last second, picture orientation and audio. That ten-second review catches the problems that matter: a keyframe appearing before the desired start, missing audio, a source that the browser could preview but the exporter could not handle correctly, or a clip boundary that was set too tightly.
Lossless or Accurate: choose the mode that fits the cut
The two modes are not vague quality presets. They use different FFmpeg operations and solve different problems.
| Decision | Lossless | Accurate |
|---|---|---|
| Best for | Fast rough cuts, removing dead air, preserving the existing compressed streams | Exact opening frames, dialogue cues, slides or actions that must begin at a specific moment |
| What happens | Video and audio streams are copied into a new MP4 without re-encoding | Video is encoded as H.264 and audio as AAC |
| Speed | Usually faster | Usually slower because every kept frame must be decoded and encoded |
| Quality | No additional compression generation | One additional compression generation |
| Main limitation | The start can move to a nearby keyframe; some source codecs cannot be copied into MP4 | Needs more processing time and memory; an unusual source codec may still be impossible to decode |
Why a lossless cut can start early
Most compressed video is not a collection of complete, independent pictures. Encoders store occasional complete frames—called keyframes—and describe many of the frames between them as changes. To decode a predicted frame, a player may need information from an earlier keyframe.
Lossless mode uses stream copy. Because it does not rebuild the frames, the playable cut may need to begin at a keyframe before the time you chose. The difference may be invisible, or it may expose a brief piece of footage you intended to remove. This behaviour is part of compressed video structure, not a broken timeline control.
Use Lossless first when you are removing several seconds of silence from the beginning of a screen recording, shortening the end of a phone clip, or extracting a segment where an extra fraction of a second is harmless. You keep the source picture and audio streams intact, and the export usually completes quickly.
When frame accuracy is worth re-encoding
Choose Accurate mode when the first visible frame matters: a speaker begins mid-sentence, a title needs to appear immediately, a slide changes at an exact moment, or a shot must start on an action. Accurate mode decodes and rebuilds the selected section, allowing the cut to land on the chosen frame.
The current export settings are H.264 video at CRF 20 with the veryfast preset and AAC audio at 192 kbps. CRF controls the balance between compressed size and visual fidelity; it is not a target file size. The result may be smaller or larger than the source depending on its resolution, frame rate, complexity and original bitrate. If avoiding any additional compression is more important than an exact boundary, return to Lossless.
For a deeper explanation, read why keyframes affect lossless trimming.
What “processed locally” means—and how to verify it
When you select a file, the browser creates a temporary local blob: address so the page can preview it. The editing engine writes the source into an in-memory workspace, runs the trim, builds the output and deletes its temporary input and output files after the operation. The final download link also points to a browser-created blob until you save the file or leave the page.
The first export downloads the site’s FFmpeg WebAssembly engine from the same website. That engine is application code, not your footage. It is roughly 31 MB after decompression, so the first run can appear slower than a later run in the same session. There is deliberately no third-party CDN fallback for this executable component.
You do not have to rely on a privacy slogan. To inspect the behaviour yourself:
- Open your browser’s developer tools and select the Network panel.
- Clear the request list, then choose a non-sensitive test video.
- Set a short range and export it.
- Inspect the requests. You may see the page assets and the processing engine, but you should not see your selected media posted to an application endpoint.
- After the engine has loaded, disconnect from the internet and make another cut. The local operation can continue in the open tab.
Local processing limits who receives the file, but it is not a substitute for device security. Browser extensions, malware, shared user accounts and an unlocked computer are outside this site’s control. For sensitive work, use a trusted, updated browser profile and store the downloaded result appropriately.
Containers, codecs and why an MP4 can still fail
A file extension describes a container—the wrapper holding video, audio, timing and metadata. It does not identify every stream inside. Two files named .mp4 can use different video or audio codecs and behave differently in the same browser.
Video Trim checks the file’s signature rather than trusting a renamed extension. It recognises these input containers:
| Container | What to expect |
|---|---|
| MP4, M4V and MOV | Common inputs, but preview and export still depend on the internal codecs. |
| WebM and MKV | Often preview correctly in modern browsers. Lossless MP4 export can fail if their existing streams are not valid inside MP4. |
| OGG | Browser preview support varies, and direct stream copy to MP4 is limited. |
| AVI | Older codecs are common in AVI files; Accurate mode may help if the bundled engine can decode them. |
Every successful trim is delivered as MP4. In Lossless mode, that MP4 contains the original copied streams, so compatibility depends on whether those streams belong in the output container. In Accurate mode, the output contains H.264 video and AAC audio, a combination supported by a broad range of current devices and services.
If Lossless reports that a codec cannot be copied into MP4, switch to Accurate. If Accurate also fails, the engine could not decode the source. Converting the original to a conventional H.264/AAC MP4 in a trusted desktop application is the most reliable fallback. Our format compatibility notes describe the current browser and engine requirements without claiming universal support.
Useful trimming workflows
Remove dead air from a screen recording
Screen recordings—whether captured with system utilities or browser capture tools like OnlineScreencast—often begin with cursor movement, window arrangement or a pause before speaking. Move the start marker to just before the first useful action. Leave a small lead-in rather than cutting directly on the first spoken sound; a clip feels abrupt when the first syllable begins at time zero. At the end, leave enough room for the final sentence to finish naturally. Lossless mode is normally the right first attempt because a tiny variation at the boundary rarely matters.
If the screen recorder uses long gaps between keyframes, the Lossless result may show an earlier desktop frame. Use Accurate mode when that frame contains private information or makes the edit look unfinished. Always check the first second of the downloaded file rather than relying only on the in-page preview.
Extract one moment from a phone video
Play through the action once, place the start a little before it begins, and set the end after the motion settles. This preserves context and prevents an accidental jump cut. Phone footage is frequently high resolution, so a long source can put pressure on browser memory even when the selected clip is short. If the tab closes or the operation stalls, use a desktop browser, close other memory-heavy tabs, or shorten the source with the phone’s built-in editor before making the final cut.
Orientation is stored differently across cameras and containers. Preview the downloaded result on the device where it will be used. Trimming changes time boundaries; it does not provide a rotation control or redesign vertical footage for a horizontal canvas.
Prepare a clip for messaging or email
Trimming can reduce size because the output contains less duration, but it does not guarantee a particular number of megabytes. A 20-second 4K clip can still be too large for an attachment limit. Make the meaningful cut first, download it, and inspect its size. If it remains too large, use the video compressor as a separate step. Keeping trimming and compression separate lets you decide where quality loss is acceptable instead of applying it automatically.
Cut a clean excerpt for social media
Find the shortest section that still makes sense without the original context. Avoid opening on a pronoun, reaction or conclusion that depends on something the viewer cannot see. Add a brief visual beat before speech and do not cut the final word’s audio tail. Accurate mode is helpful when a platform clip must start on a specific expression or action.
This tool does not add captions, change aspect ratio, combine shots or insert music. Finish those tasks in an editor designed for composition. If you are creating social media memes or personalized reaction clips from a trimmed excerpt, browser tools like Free GIF Face Swap allow swapping faces directly within animated GIFs without uploading your media. A clean trim is still a useful first step because it removes unused footage before another application has to import or upload it.
File size, speed and browser memory
There is no account-level file-size or duration cap imposed by Video Trim. There is, however, a practical limit: your browser needs memory for the selected file, the WebAssembly engine, working data and the finished output. A file can fit on disk but still be too large to process in a browser tab. Mobile browsers generally have less memory available than desktop browsers.
Processing speed depends on the device and the chosen mode. Lossless work mostly copies streams and is usually quick. Accurate mode decodes and encodes video on the CPU through WebAssembly; it does not use the same hardware-encoding path a native desktop editor might use. Resolution, frame rate, clip duration and scene complexity all affect the wait. Promising a universal “seconds” estimate would be misleading.
For a large file, improve the odds of a successful export by closing other heavy tabs, keeping the browser in the foreground, preventing the device from sleeping and using a laptop or desktop when possible. Do not repeatedly press the export button while processing. If the source is irreplaceable, keep the original untouched until you have played and backed up the finished clip.
Troubleshooting a video that will not trim
The file is rejected immediately. The signature does not match one of the recognised video containers, the file is empty, or the file is not really a video despite its extension. Renaming a file does not convert it. Open it in a trusted media player and export or convert it to a standard MP4.
The file is accepted but no preview appears. The browser probably cannot decode the internal video or audio codec. Try a current version of Chrome, Firefox or Safari. If the footage is important, check the codec in a desktop media-information utility and convert a copy rather than altering the original.
Lossless export fails. The existing streams may not be valid in an MP4 container. Choose Accurate so the tool can attempt to create H.264 video and AAC audio instead.
The Lossless clip begins before the start marker. The cut has moved to a nearby keyframe. This is expected for stream copy. Choose Accurate when the extra frames matter.
Accurate export is slow. Re-encoding is computationally expensive, especially for long, high-resolution or high-frame-rate video. Keep the tab active and let the operation finish. For very large projects, a native editor is a better fit.
The tab reloads, freezes or runs out of memory. Close other tabs and applications, restart the browser, and try a shorter or lower-resolution copy. Moving from a phone to a computer often helps. Because the processing is local, the site cannot add server memory to the task.
The processing engine does not load. JavaScript and WebAssembly must be available, and loading the compressed engine requires DecompressionStream. The implementation targets Chrome 80+, Firefox 113+ and Safari 16.4+ for that feature. Network filters, strict extensions or an interrupted first download can also block the engine; refresh once and check the error shown.
When reporting a repeatable problem, send the browser version, operating system, container, video codec, audio codec and exact error through the contact page. Do not send private footage. A short synthetic or non-sensitive sample is enough if a file is needed to reproduce the issue.
What this video trimmer does—and what it does not
Use Video Trim when you need one continuous section from one source file. It is suitable for cutting a highlight, turning long recordings into shareable clips, preparing video evidence for warranty claims and returns, or isolating a demonstration. See our step-by-step Video Trim tutorial, our comparison of lossless vs. re-encode workflows, and our troubleshooting guide to fixing common video playback and export problems.
It does not join multiple clips, remove a section from the middle while keeping both sides, add transitions, change playback speed, grade colour, mix audio tracks, create captions or upscale footage. If your workflow requires improving resolution or picture clarity after trimming, browser-based tools like Veedz AI can upscale video up to 4K locally on device without cloud uploads. Once your clip is ready to publish, read our guide on how to write video titles for SEO and CTR. For multi-track timelines with layers and complex effects, use a full desktop video editor. For a private start-to-end cut, choose your file above and keep the original until you have verified the download.