Client-side video editing constraints
Video files combine timed picture and (usually) sound inside a container such as MP4 or WebM. Editing in the browser means decoding what the engine can play, drawing frames to a canvas or capture stream, and re-encoding with MediaRecorder into a downloadable blob. That path suits short clips and privacy-sensitive material, and it is bounded by memory, codec support, and re-encode quality.
Output containers follow what the browser’s MediaRecorder.isTypeSupported() reports—commonly WebM (VP8/VP9) or MP4 depending on the engine.
To inspect duration and resolution before cutting a clip, open Get video info.
Containers, codecs, and what “convert” means
A container (MP4, WebM, QuickTime) packages elementary streams. A codec (H.264, VP9, AAC, Opus) defines compression. In the browser, available encode targets depend on the browser build and platform media stack. Re-encoding creates a new lossy generation; generic canvas-capture tools are not lossless remuxers.
Short social clips and screen recordings re-encode acceptably for chat and docs. Archival masters should stay in the original file. Audio may be dropped or omitted depending on the subtool. File size ceilings (for example ~100 MB) exist because full decode plus re-encode can exhaust a tab—trim first, then compress or convert.
Subtools in this family
- Get video info — duration, resolution, aspect ratio, MIME type, file size.
- Extract frame — seek to a timestamp; export PNG or JPEG stills.
- Trim video — keep the segment between start and end times.
- Mute video — re-encode without the audio track.
- Compress video — lower target bitrate (Kbps) to shrink size.
- Convert video — re-encode into a browser-supported output format.
- Video to GIF — sample a time range into an animated GIF.
- Resize video — scale width/height while preserving aspect ratio.
Trim, bitrate, and resolution
Bitrate and resolution both multiply with duration. Cutting a long recording to the seconds that matter often reduces size more than aggressive compression alone—and lowers encode time. Invalid start/end ranges should be rejected rather than producing empty output. Chain many re-encodes carefully; plan one encode when possible.
Bitrate budgets bits per second of video; lower means smaller files and more artifacts. Resolution sets how many pixels must be described. Downscaling before a moderate bitrate often looks better than starving a 4K buffer. Use Compress video and Resize video together thoughtfully: match display size, then pick a bitrate for that grid.
Frames, GIFs, audio, privacy
Frame export is seek + draw + image encode (PNG for lossless stills, JPEG for smaller thumbnails). Animated GIF uses indexed color and grows quickly at high FPS or wide dimensions—prefer short ranges and capped width. For longer motion with sound, keep a real video container.
Mute removes noise or copyright-sensitive audio and can shrink some outputs; it does not improve picture quality after re-encode.
Clips need not upload to Tool Plaza’s servers—the work happens in the page. The workstation remains the trust boundary: downloads, crash dumps, and shared machines can still leak media.
Limitations and workflows
Not every MP4 variant demuxes. Soft detail suffers across generations—do not replace camera originals. Multi-minute 4K sources may stall; trim and downscale first. No professional HDR/color-grading pipeline.
Thumbnail: info → Extract frame. Chat clip: Trim video → optional resize → compress. Silent loop: trim → Mute video. Docs preview: short Video to GIF. Format bridge: Convert video when the destination needs a container the browser can produce.
Summary
Browser video tools decode what the engine can play, then re-encode derivatives for trim, mute, compress, resize, convert, GIF, and still extraction. Ideal for short, local, privacy-sensitive jobs—not mastering. Trim early, match bitrate to resolution, and keep originals intact.