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
| Container | Accepted by file check | Important limitation |
|---|---|---|
| MP4 / M4V / MOV | Yes | Preview and export still depend on the video and audio codecs inside. |
| WebM / MKV | Yes | Lossless trimming to MP4 may fail when a stream is not valid in an MP4 container. |
| OGG | Yes | Browser preview support varies; MP4 stream-copy compatibility is limited. |
| AVI | Yes | Older 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
- Use a non-sensitive sample. Record your browser version, operating system, source size, duration, resolution and codecs.
- Check preview picture and sound, then export the same short range in Lossless and Accurate modes separately.
- Play both downloads in the intended destination player. Check the first and last frames, sound, orientation and file size.
- For an offline check, finish an export so the processing engine has loaded. Disconnect and repeat the export in the same open tab.
- 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
- MDN media container guide: container recognition is separate from codec support.
- MDN DecompressionStream: browser support for loading the compressed engine.
- FFmpeg metadata options: metadata can be copied independently of re-encoding.
- ffmpeg.wasm FAQ: engine performance and memory constraints.