3tej home
← All Files & Media tools

What is Video Trim?

A Video Trim computes video trim from the inputs you provide. It applies the standard formula to the values you enter and returns the result instantly, without sending any data to a server. Visual frame preview, set start and end points.

Video Trim

Trim a video by start and end seconds.

ℹ️ First use loads ffmpeg.wasm (~25 MB). After that, processing is fully in your browser - the file never uploads.
🎬
Drop video file
MP4, MOV, MKV, WebM. Max ~500 MB.

About this tool

Trimming video cuts off the start, end, or both of a video clip. Most common uses: removing the few seconds before "action" in a recording, cutting an outro card, or pulling a sub-clip from a long screen recording.

This tool runs in your browser. The video plays in a preview pane and you set start / end markers visually or by exact timestamp (HH:MM:SS.mmm). Output is delivered as MP4 H.264 by default for max compatibility.

How it works

  1. Open your video

    Drop an MP4 / MOV / WebM / AVI / MKV file.

  2. Set start and end

    Drag the markers on the timeline or type HH:MM:SS.mmm.

  3. Preview

    Play to confirm the trim region.

  4. Export and download

    Saves as MP4 H.264 to your device.

Use cases

Screen recordings

Cut the few seconds before clicking "Start recording" and the trailing "Stop" cursor.

Phone videos

Trim 2-3 seconds of shaky start to a clean opening frame.

Social media uploads

Trim long videos to the platform's 60-second / 90-second / 3-minute caps.

Reaction snippets

Pull a 15-second moment from a 10-minute interview for sharing.

Format and spec details

Source formatsMP4, MOV, WebM, AVI, MKV, FLV
OutputMP4 H.264 (universal compatibility)
ResolutionSource resolution preserved
AudioPreserved

Tips and best practices

  • Add a 0.5-1 second buffer at the start of any speaking video for a clean intro.
  • Trim before applying any heavy effect - re-encoding less footage is faster.
  • For social platforms with strict caps, trim to 1 second under the cap to leave room for the platform's re-encode.

How browser-based audio/video tools work

Modern browsers ship with Web Codecs API, MediaRecorder, and Web Audio API - enough to decode, manipulate, and re-encode most media formats client-side. This tool uses those APIs (with FFmpeg.wasm as a fallback for less common codecs).

The processing flow

  1. File is loaded as a binary Uint8Array.
  2. The codec is detected from the container (MP4 = MPEG-4, MKV = Matroska, WebM = WebM) and the codec atoms.
  3. Frames are decoded into raw audio samples (PCM) or video frames (YCbCr / RGB).
  4. The requested transformation (trim, convert, resize) is applied frame-by-frame.
  5. Frames are re-encoded into the output codec and packaged into the output container.

Common audio/video formats

ContainerCommon codecsBest for
MP4H.264 / H.265 video, AAC audioUniversal compatibility; default for web video
WebMVP9 / AV1 video, Opus audioOpen-source web standard; smaller than MP4
MKVAny codec (container only)High-quality archival; not browser-native
MOVProRes / H.264, PCM / AACApple ecosystem; ProRes for professional editing
MP3MP3 audio onlyUniversal audio; lossy
WAVPCM audio (lossless)Editing source; CD-quality archival
FLACLossless compressed audioMusic archival; ~50% of WAV size, perfect quality
AAC / M4AAdvanced Audio CodingiOS default; better quality than MP3 at same bitrate

Lossy vs lossless

  • Lossy (MP3, AAC, Opus, H.264): discards data the human ear/eye can't notice. 80-90% size reduction. Each re-encode loses more quality (generation loss).
  • Lossless (FLAC, WAV, ALAC, FFV1): bit-perfect reproduction. ~50% size of raw. Each re-encode is identical to the source.

Bitrate quick reference

Use caseAudio bitrateVideo bitrate (1080p)
Voice (phone, podcast)32-64 kbpsn/a
Music (mid-quality)128 kbps MP3n/a
Music (transparent)256-320 kbps MP3 or 128 kbps Opusn/a
Streaming HDn/a5,000-8,000 kbps
Streaming 4Kn/a15,000-25,000 kbps
ArchivalFLAC losslessProRes 422 or H.265 CRF 18

Privacy and offline operation

Every operation in this tool runs client-side using your browser's built-in APIs (Canvas, Web Audio, WebAssembly). No data is uploaded. After the initial page load you can disconnect from the internet and the tool keeps working.

We use Google Analytics and AdSense for the page itself, but neither sees the content of the files you process.

Frequently asked questions

Will trimming reduce video quality?

When the trim points are on keyframes, the operation is lossless. When they fall mid-GOP, the surrounding frames are re-encoded - usually negligible quality drop.

Can I trim multiple regions?

This tool trims start + end. For multiple cuts (remove a middle segment), trim into two halves and use Video Merge.

Why does the output start a half-second late?

The trim point may have snapped to the nearest keyframe. For frame-accurate trims, use a tool that re-encodes the boundary.

Is my video uploaded anywhere?

No. All processing happens in your browser using Web Codecs / FFmpeg.wasm. Files stay in your tab's memory. Disconnect from the internet after page load and the tool still works.

Why is conversion slow?

Video re-encoding is CPU-intensive. A 1-minute 1080p clip can take 30-90 seconds to encode in the browser - desktop apps with hardware acceleration are 5-10x faster. Use this tool for short clips; for hour-long footage use HandBrake or FFmpeg on your machine.

Will the converted file lose quality?

Yes, slightly, if the source and destination are both lossy formats. Going from H.264 to H.264 at the same bitrate adds a small amount of generation loss. Going from H.264 to a lossless codec preserves the existing quality but doesn't restore what was lost on the first encode.

Can I convert between any two formats?

Most common pairs (MP4 <-> WebM, MP3 <-> AAC, WAV <-> FLAC) work in any modern browser. Exotic codecs (ProRes, FFV1, JPEG 2000) may require FFmpeg.wasm and run slowly.

What's the maximum file size I can process?

Practical limit is your browser's available memory (typically 2-4 GB). 30-minute 1080p videos process fine. 2-hour 4K source files may crash the tab; use a desktop tool for those.

How accurate is the Video Trim?

It applies the standard formula. Accuracy is limited only by your input precision. For decisions with material consequences (taxes, medical, legal, structural), use the result as a starting point and verify with a qualified professional in the relevant field.

Is the Video Trim free to use?

Yes. 100% free, no signup, no payment, no API key. The site is funded by display ads around the tool but not inside the calculation flow.

Are my inputs saved anywhere?

No. All inputs stay in your browser tab. Closing the tab discards them. The site uses Google Analytics for traffic measurement (anonymized) but the analytics never see what you type into the form.

Can I use the Video Trim on my phone?

Yes. The tool is responsive and tested on iOS Safari, Android Chrome, and major desktop browsers. Touch targets meet Apple's 44pt and Google's 48dp minimum.

Does the Video Trim work offline?

Yes. Once the page has loaded, it works without internet. The calculation runs in JavaScript on your device.

How do I report a bug or suggest improvement to the Video Trim?

Email hi@3tej.com with the URL of this page and a description of what you saw vs expected. We typically respond within 72 hours.

Can I share results from the Video Trim?

Take a screenshot or copy the output. The page doesn't generate shareable URLs for specific calculations - inputs stay in your browser only.

Why are the results different from another video trim tool?

Most likely: different formula assumptions, different default values, different rounding rules, or different applicable rates. Check the methodology if both tools document it. Both can be valid for different scenarios.