Simple Video Editor
Sequence, crossfade, or combine two clips side by side or picture-in-picture, with a text banner and logo watermark. Your files are never uploaded to our servers. ToolkitPoint processes them on your own computer, so confidential documents stay with you.
Processed in your browser. Your files are not uploaded.
How to use Simple Video Editor
- Add clips with "Add video clips". Each clip becomes a card with a timeline bar, start and end sliders and number boxes, speed, volume, mute and rotate. Clips with or without sound, in any shape, can be mixed.
- Press "Preview" on a clip, move the video to a moment, then use "Set start at playhead", "Set end at playhead" or "Split clip at playhead"; reorder with Up and Down or Remove.
- Under "Layout and frame" choose how clips are joined (cuts, crossfade, side by side, picture-in-picture), the frame shape (16:9, 9:16, 1:1, 4:5), size, and whether unmatched clips get a blurred background, solid bars or a crop.
- Optionally add background music, a text banner, a logo, and subtitles from an SRT/VTT file or auto-captions with a local Whisper model.
- Choose MP4, WebM or GIF and a CRF or target file size (or tick Fast join for a lossless copy), press "Build video", and download edited-video plus captions.srt when auto-captions were used.
Worked example
Add trip.mp4 (landscape, with sound) and a silent vertical clip. Choose 9:16, 720 px, "blurred background", split trip.mp4 at 4.2 s, set the second half to 2x, tick "Loop the music" with a track at 60% volume, and press Build video. The status shows a 720 x 1280 MP4 whose length is the two clip sections plus the sped-up half; the silent clip gets generated silence under the music.
When to use this tool
- Cutting a screen recording and joining a few clips without a watermark.
- Making a vertical Reels or Shorts video from landscape and portrait clips with a blurred background.
- Adding background music and burned-in captions to a short clip on a phone-sized frame.
- Joining clips from one camera instantly with Fast join, with no re-encode.
Important limitations
A browser editor, not a full non-linear editor: no multi-track timeline, transitions other than crossfade, or keyframes. Clips are limited to 250 MB each and everything is rendered in memory by FFmpeg, so long 1080p edits are slow. Subtitles are drawn as pictures (up to 120 cues), the timeline uses sliders and a playhead preview rather than drag handles on a filmstrip, and Fast join only works when clips share codec, size and audio format.
Comparing alternatives
Other options for simple video editor include CapCut, Clipchamp, Kapwing.
ToolkitPoint is not affiliated with those services.
Frequently asked questions
Do clips without audio work now?
Yes. Silence is generated for a clip that has no sound so it can be joined with clips that do. If every clip is muted or silent and there is no music, the result has no audio track at all.
Are clips of different shapes stretched?
No. Every clip is fitted into one frame: whole picture with a blurred background or solid bars, or filled and cropped, as you choose. The frame shape defaults to that of the first clip.
Does the export have a watermark or a length limit?
No watermark is added and there is no account or length cap; the limits are 250 MB per clip and your device memory. Nothing is uploaded.
How do the auto-captions work?
The finished video is rendered, its sound is transcribed on your device with a Whisper model (the first use downloads it from a public model host and caches it), and the text is burned in and offered as captions.srt. Recognition can make mistakes, so review them; it needs speech in the audio and is not available for GIF.
What is Fast join?
It joins clips by copying their streams, so it is instant and lossless, but only when every clip has the same codec, size and audio format. Cuts snap to the nearest earlier keyframe, so the real length can differ slightly, and effects are switched off. If clips differ you get a message saying how.
How accurate are the time and size estimates?
The length and frame size are exact. File size is only predicted when you choose "Target file size" (checked afterwards and re-encoded if over). Render time is shown after your first render, based on how fast your own device ran it.