How to use Video Merger: settings and output checks
Learn the real workflow, parameters, device limits, privacy, and checks before downloading from Video Merger.
When to use it
Normalize and join a small ordered set of decodable clips into one MP4. Clips with different dimensions, frame rates, orientations, and codecs cannot be concatenated reliably as-is. Normalization takes time and can reduce quality.
Practical example
For mixed portrait and landscape clips, normalize canvas and frame rate first. Contain mode adds bars, and source loudness is not professionally matched.
Steps
- Choose a small set of clips and drag them into order.
- Review duration, orientation, dimensions, and audio on each clip.
- Choose a common canvas, frame rate, and padding behavior.
- Inspect every join, audio level, and total duration after merge.
Choosing parameters
- Order and enabled clips
- Common dimensions and background padding
- Frame rate and quality
- Silent-track handling for clips without audio
Test a short or lower-resolution sample first. Do not raise bitrate, sample rate, frame rate, or resolution merely to look “clearer”; re-encoding cannot recover information missing from the source.
Checks before download
- Normalizes clips from different sources
- Media is read and transcoded in this browser tab and is not uploaded to FreeTool to perform the task.
Play the complete result and inspect first/last frame, sync, orientation, dimensions, sound, color, and duration. Retest formal deliverables on the target phone, browser, or platform.
Real limits and device requirements
- Total size and browser memory make many long clips unsuitable
- Different clip properties normally require re-encoding
- No transitions, timeline, multitrack mix, or subtitle editing
FFmpeg WebAssembly in a browser depends on device CPU, memory, and bundled codecs. It is not native desktop FFmpeg performance and does not support every codec sharing an extension. Keep the page active; phones, long/high-resolution media, and large files fail more easily.
Privacy and licensing
Media is read and transcoded in this browser tab and is not uploaded to FreeTool to perform the task.
The ffmpeg.wasm wrapper is MIT, while the bundled FFmpeg core for this release is distributed under GPL-2.0-or-later. License notices and corresponding source access must remain public. Process only media you are entitled to use.
Common questions
Why are there black bars?
Different aspect ratios need padding when the complete frame is preserved.
Why does volume change at a join?
Sources have different levels and sample settings; professional loudness normalization is not included.
Are videos uploaded?
Media is read and transcoded in this browser tab and is not uploaded to FreeTool to perform the task.