Browser Video Editing: Privacy, Formats, and Large Files

Test one short export before a long edit

VideoMultiCut reads and processes your selected video in the browser. The editor does not upload that video to a processing server. Before making a large clip list, open your file, check picture and sound, and export a short selection. That establishes whether this recording works on the device and browser you are using.

Local processing avoids a video upload, but your device still has to decode the source and create the output. A small page download does not make a demanding video export small. Treat playback and export as two separate checks.

What stays local

Choosing a file gives the editor access to that file for the current editing session. Preview uses a local browser URL, and export runs with FFmpeg in the browser. The finished clips are offered as downloads on your device.

The website still needs to load its pages and processing software. 'No video upload' describes the media workflow; it does not mean the website makes no network requests. Keep your source recording in its original location, and save any exported clips you need before closing the page.

Clip names and ranges in the current editor are not a saved project you can count on reopening later. If you need to return to a long edit, record the names and timestamps separately. Loading another source file clears the current clip list.

Why the extension does not settle compatibility

A filename such as recording.mp4 identifies a container. The audio and video inside it use codecs, and the browser must be able to decode those streams for preview. MDN's media format guide distinguishes container support from codec support. Two files with the same extension can therefore behave differently.

Check the actual preview instead of relying on the filename. Can you see movement, hear the expected sound, and seek to another part of the recording? If any of those fail, do not spend time building the whole clip list. Try the source in a local player to check the recording itself, then try another current browser or a compatible converted copy.

Renaming a file from .mov to .mp4 does not convert its contents. If conversion is necessary, use a tool that actually re-encodes or remuxes the media, and retain the original. After conversion, repeat the short playback and export check.

Large files need a smaller first step

Start with one short range from the large recording and export it individually. If it succeeds, open the download and check it. You can then decide whether to export the remaining selections individually or build a ZIP of the set.

The ffmpeg.wasm project documents browser processing limits and slower performance than native FFmpeg. There is no universal safe duration for every device. Resolution, the encoded media, available memory, and the amount you export all affect the work involved. VideoMultiCut does not promise that every large source will finish successfully.

Batch export keeps the produced clips available while preparing the ZIP. If a batch fails, try individual exports to reduce the amount of output held together. Avoid running several exports in separate tabs at once. For a source your browser cannot handle reliably, use a desktop workflow and keep the original recording intact.

Separate a playback problem from an export problem

If the source will not play, investigate its format first. If preview works but export fails, retry a short individual clip and note the visible error. An export that fails for a tiny selection needs a different investigation from one that fails only after a large batch.

When asking for help, record your browser, device, file extension, approximate file size, and whether preview or export failed. You can describe the failure without sending the recording itself. Open the file and try one short clip before committing time to the full edit.