Video Trim

Video Format Compatibility

Implementation notes updated: 13 October 2026

Video compatibility has two separate layers: your browser must be able to preview the selected file, and the bundled FFmpeg engine must be able to read its streams and write the requested output. A recognised container does not guarantee that every codec inside it will work.

These notes describe the current file checks and export settings. They are not a browser benchmark or a tested guarantee for every device and codec combination.

Current input checks

ContainerAccepted by file checkImportant limitation
MP4 / M4V / MOVYesPreview and export still depend on the video and audio codecs inside.
WebM / MKVYesLossless trimming to MP4 may fail when a stream is not valid in an MP4 container.
OGGYesBrowser preview support varies; MP4 stream-copy compatibility is limited.
AVIYesOlder codecs often cannot be copied directly into MP4.

What each trim mode does

Lossless in our Video Trimmer uses FFmpeg stream copy. It is fast and does not recompress the picture, but the start can move to a nearby keyframe and the existing streams must be valid in the MP4 output container. See why keyframes affect cut boundaries for technical details.

Accurate re-encodes video as H.264 and audio as AAC so the cut can land on the selected frame and the result has broadly compatible MP4 streams. A source can still fail if the bundled engine cannot decode one of its streams. Check our guide on when to trim losslessly vs re-encode.

Browser requirements

  • JavaScript and WebAssembly must be enabled.
  • The browser needs enough free memory for the input, processing engine and output.
  • Loading the compressed processing engine requires DecompressionStream: Chrome 80+, Firefox 113+ or Safari 16.4+.
  • Large or long files are more likely to fail on phones because mobile browsers have lower memory ceilings.

How to report a failure

Email hello@trimvideoonline.com with the browser version, device, container, video codec, audio codec and the error shown. Do not send private footage. A short synthetic or non-sensitive sample is enough when a reproducible file is needed.

Read the editorial and testing policy for how compatibility claims are reviewed.

Check a file on your own device

  1. Use a non-sensitive sample. Record your browser version, operating system, source size, duration, resolution and codecs.
  2. Check preview picture and sound, then export the same short range in Lossless and Accurate modes separately.
  3. Play both downloads in the intended destination player. Check the first and last frames, sound, orientation and file size.
  4. For an offline check, finish an export so the processing engine has loaded. Disconnect and repeat the export in the same open tab.
  5. Record the result and exact error, if any. A success for one sample establishes support for that sample on that device, rather than every file with the same extension.

Metadata and location privacy

Neither trim mode guarantees removal of camera metadata or GPS tags. Re-encoding should not be treated as metadata sanitization. If those tags matter, inspect and remove them with a dedicated metadata tool before sharing the download.

Technical references

Format & Compatibility Questions

Why can my browser preview a video that fails during export?

Browser preview uses your operating system's native media player hardware decoders, which may handle formats that the bundled FFmpeg WebAssembly engine cannot decode or remux into an MP4 container. Switching to Accurate mode often resolves export issues for supported codecs.

Why does a WebM or MKV file fail when using Lossless mode?

Lossless mode copies the source streams into MP4. Some codec combinations cannot be written by the bundled engine or played by the destination player. Try Accurate mode to convert decodable sources to H.264 video and AAC audio, then check the saved file.

Can I trim Apple ProRes or HEVC (H.265) videos?

Preview depends on the browser and operating system; export depends separately on the bundled engine. Accurate mode can convert a source only when the engine can decode its streams. HEVC or ProRes support is not guaranteed, and large files may exceed available memory.

Why does processing fail on mobile browsers for large 4K files?

The input, processing engine, working data and output all need browser memory. The available memory varies by device and browser. Large sources can fail even with a short selected range; try a shorter source file or a desktop browser.

What should I do if an AVI or OGG file shows an unsupported codec error?

Older AVI files frequently use legacy DivX, Xvid, or DV codecs, while OGG files use Theora. These codecs cannot be losslessly packaged into MP4. If Accurate mode cannot decode the streams, convert the file to H.264 MP4 first using desktop VLC or HandBrake.

Browser Tool Suite

100% private and client-side. Zero cloud uploads, no watermarks, and no signups required.