ALL VIDEO TOOLS23
Split Video
Split Video Online — Free, No Re-Encode
Cut a clip into equal parts, fixed lengths, or at times you type, and download them all as one ZIP.
About Split Video
Splitting a video normally means decoding every frame and encoding it again, which is slow and costs quality on every part. This does not do that. Each part is one FFmpeg run that copies the compressed picture and sound straight across, so a part holds the same bytes the source did and the whole job finishes in a fraction of the time a re-render would take. There are three ways to say where the cuts go: a number of equal parts, a fixed length for every part, or a list of times you type in seconds or minutes and seconds — where each time is the point one part ends and the next begins, so three times give four parts. The price of copying rather than re-encoding is the one thing this page repeats, because it is the tool's only real surprise: a stream copy can only cut at a keyframe. A boundary that falls between keyframes moves back to the nearest one, so a part starts a little earlier than you asked and runs a little longer. Measured on this engine with a 2.09-second clip, a part asked to be 1.000 second came out at 1.022, and one asked to start at 0.5 seconds and run for 1.0 came out at 1.510 because the seek snapped back to the keyframe at the start of the file. The table on screen therefore has two length columns — what was asked for, and what the written file actually measures, read back off each finished part. A page that showed only the first would be describing files that do not exist. Every part keeps the original format and quality, and they arrive together in one ZIP, because browsers cancel most of a burst of separate downloads. At most a hundred parts in one go: each one is its own pass through the engine.
Questions
Are the parts exactly the lengths I asked for?
Not quite, and the tool shows you both numbers. A stream copy can only cut at a keyframe, so each boundary moves back to the nearest one and a part starts a little earlier and runs a little longer than requested. Measured on this engine with a 2.09-second clip, a part asked to be 1.000 second came out at 1.022, and one asked to start at 0.5 seconds came out at 1.510 because the seek snapped back to the keyframe at the start.
Does splitting lose quality?
No. Nothing is decoded and nothing is re-encoded — the compressed picture and sound are copied straight across, so each part holds the same bytes the source did and keeps its original format. That is also why it is fast.
How do I choose where the cuts go?
Three ways. Equal parts divides the clip into a number of parts of the same length; Every N sec cuts at a fixed length, and whatever is left at the end becomes a final shorter part of its own — a 100-second clip cut every 30 seconds gives 30, 30, 30 and 10 — with only a remainder under 0.05 seconds, too short to write as a playable file, folded into the part before it; At times takes a comma-separated list in seconds (90) or minutes and seconds (1:30), where each time is where one part ends and the next begins, so three times give four parts.
Why is the download a ZIP instead of separate files?
Browsers cancel most of a burst of separate downloads, so a single archive is the only way every part actually arrives. One run produces at most a hundred parts, because each part is its own pass through the engine.
Which column should I trust for a part's length?
The ACTUAL one. It is read back off each finished file rather than copied from the request, so it describes what you are about to download. The ASKED column is there to show you how far the keyframe moved the boundary.
Is my file uploaded to a server?
No. Transmute processes everything locally in your browser using JavaScript and WebAssembly. Your files never leave your device — there is no server, no upload, no cloud processing.