Paste a video share-page link or direct MP4 link, add a time range, and the tool downloads only the little piece you need and keeps it at the original quality (no re-encoding) — so there is no need to download the complete file, which can run to several GB.
A two-hour recording can run to several gigabytes when all you want is one minute of it. HTTP lets a client request just a range of bytes from a file, and that is exactly what this tool runs on: it reads the file header first to work out how timestamps map to byte positions, then fetches only the range you marked. What that saves is not only waiting time but bandwidth and disk space — pulling one minute on demand is usually a few dozen megabytes. The trade-off is that there has to be a reachable URL; with a local file there is nothing to skip.
Ordinary editing software decodes the picture and compresses it again, losing a little quality on the round trip and taking minutes or more on a long video. This tool copies the original bitstream straight through, so the result matches the source frame for frame and the processing time is essentially just the download time. The limitation you accept in return is that cut points cannot land anywhere you like: video can only start decoding at a keyframe, so the start is aligned to the nearest one and may land a fraction of a second earlier than the time you entered. For frame-accurate cuts, or for transcoding, subtitles or a resolution change, you need real editing software.
Drag the playhead to the spot you want in a player, read the time off it and type that in, as hours:minutes:seconds. It is worth leaving two or three seconds of slack at each end rather than cutting it fine: keyframe alignment already nudges the start earlier, and a moment of lead-in and follow-through makes the clip feel less abrupt. When you are unsure of the range, take a generous clip first, watch it, then trim again — each attempt only downloads its own range, so it costs very little.
It suits pulling clips out of long recordings: goals and good plays from a match recording, one speaker's segment from a full-event capture, evidence from CCTV playback, the key explanation from a lecture video. What it does not suit is equally clear: video sitting on your own hard drive (no address to request ranges from), stitching several sources together, changing resolution or bitrate, adding subtitles or transitions. Those belong in CapCut, Premiere or FFmpeg.
No. This tool needs aURL, because it works by requesting only part of the remote file — that is exactly what makes it faster than downloading everything and then cutting. A local file is already on your machine, so there is nothing left to save. To trim a local video, something like FFmpeg or a desktop editor is the better fit.
Only some of the frames in a video are “keyframes”; every other frame can be reconstructed only from the keyframe before it. Starting at an arbitrary instant would mean re-encoding, which costs quality and is far slower. This tool keeps the original quality instead, so the start time is snapped back to the nearest keyframe before the moment you asked for — usually a fraction of a second to a few seconds earlier, depending on the video's keyframe interval. The end time is unaffected.
Two kinds are supported at the moment: XbotGo share-page links (cloud.xbotgo.net/share?..., paste the whole thing in and the tool will find the video address inside it), plus a direct MP4 link — an .mp4 address that plays or downloads as soon as you paste it into your browser's address bar. Watch pages on sites such as YouTube and Bilibili return a web page rather than a video file, so they are not supported; neither are HLS (.m3u8) streams, which chop a video into hundreds or thousands of small segments, nor videos protected by DRM. If you would like another sharing site supported, do let us know.
Share links carry an expiry date of their own; once one lapses you need a new one from whoever shared it. And even while a share link is still valid, the video address the tool resolves from it usually only lives for a day — so if you analyse a video, leave the page for a long while and then cut, it may fail. Just press “Analyse video” again.
Direct video links on many platforms are signed and time-limited, and start returning 403 after a few hours or even a few dozen minutes. Go back to the source page and get a fresh link. A link that only works when you are logged in (because it relies on cookies or an authorisation header) is the same kind of problem — this tool cannot read it either.
No. Downloading, cutting, joining and saving all happen in your own browser, and no video content is stored by this site. The only intermediary is a forwarding proxy that exists to get around cross-origin restrictions — it passes byte ranges through from the original video server and keeps nothing. For genuinely sensitive files, download them first and use a local tool.
The estimate is simply the whole file's average bitrate multiplied by the duration you chose. Real videos are not encoded at an even rate: fast-moving passages take more bits and static shots take fewer, so picking a busy passage overshoots the estimate and a quiet one undershoots it. On top of that the tool rounds out to keyframe and sample boundaries so the result decodes cleanly, and merges neighbouring segments into one request — both add a few extra bytes.
Yes. Put one segment per line under “Bulk text” (for example 1:05 - 1:40 Question 3 walkthrough), and every segment is joined end to end in time order into a single MP4. Overlapping or adjacent segments are merged automatically and anything past the end of the video is trimmed away — every such adjustment is spelled out in the preview below.