Online Video Joining Tool
Merge Videos Online into One MP4
Combine multiple video clips into one continuous MP4 without opening a full desktop editor. CyberTools lets you add two or more supported videos, arrange their sequence, choose 360p, 720p or 1080p output and decide whether to include audio. The current browser pipeline uses FFmpeg WebAssembly to normalize the clips before concatenation: each video is scaled to fit the selected target frame, padded when necessary to preserve its aspect ratio, converted to 30 frames per second and assigned square pixels. When audio is enabled, each audio stream is normalized to 44.1 kHz stereo before the streams are concatenated. The merged result is then encoded as H.264 video in an MP4 container, with AAC audio when requested.
Merge Videos
Reorder Clips
720p Output
1080p Output
Optional Audio
H.264 MP4
Browser Processing
Quick Answer
How do I merge videos online?
Upload at least two supported video files, arrange them in the order they should play, choose 360p, 720p or 1080p, decide whether to include audio and start the merge. CyberTools writes the source clips into the browser FFmpeg file system, normalizes their video streams to a common size and frame rate, optionally normalizes their audio streams, concatenates them in the selected sequence and exports one MP4 file. Because the current workflow uses filtering and re-encoding, this is not a lossless byte-for-byte join or stream-copy operation.
Common Uses
Common Online Video Merging Tasks
A sequential video merger is useful when several separate clips belong in one continuous file and do not require a complex editing timeline. The order shown in the clip list determines the order used by the FFmpeg concat pipeline.
Combine Phone Video Clips
Join separate clips recorded on a phone into one continuous video. If the clips have different dimensions, CyberTools scales each source to fit the selected output frame and adds padding where required instead of stretching the image.
Join Short Social Video Segments
Put a sequence of short recorded segments into one MP4 before uploading or performing further editing. Reorder the clips first because the merger follows the visible top-to-bottom sequence.
Combine Screen Recordings
Join multiple compatible screen-recording segments into one file. Choosing a target resolution gives the output a consistent frame size even when the original captures differ.
Merge Presentation or Tutorial Sections
Place an introduction, demonstration, explanation and closing clip in sequence to create one continuous tutorial without rebuilding the project in a full nonlinear editor.
Create One Video from Separate Camera Clips
Combine separate camera recordings when they should play one after another. This tool performs sequential concatenation; it does not create split-screen, overlays or simultaneous multi-camera playback.
Merge Video Without Audio
Turn off Include Audio Tracks when you want a silent result or when one or more source clips do not provide a usable audio stream. The video-only pipeline concatenates normalized video streams and writes the MP4 without an audio track.
Resolution Comparison
360p vs 720p vs 1080p for Merged Video
The target resolution controls the frame dimensions used for every clip before concatenation. The merger does not simply preserve each source frame size independently; it creates a common output geometry so the streams can be joined reliably. Higher resolution can retain more visible detail when the source supports it, but it also increases the number of pixels that FFmpeg must process and can increase processing time, memory demand and output size.
| Setting |
Frame Size |
Processing Demand |
Best Fit |
| 360p |
640 × 360 |
Lowest of the three presets |
Small previews, lightweight sharing and lower-resource devices |
| 720p HD |
1280 × 720 |
Moderate |
General web video and a practical balance of clarity and processing cost |
| 1080p Full HD |
1920 × 1080 |
Highest of the three presets |
Sources with enough detail where Full HD output is useful |
| Landscape source matching target ratio |
Scaled to fit target |
Depends on selected preset |
Minimal or no visible side/top padding when aspect ratios closely match |
| Portrait or different-ratio source |
Scaled and padded |
Depends on selected preset |
Preserves the original picture proportions inside the common landscape frame |
| Mixed source resolutions |
Normalized to one target size |
Higher because all clips are filtered |
Combining clips that need a consistent frame geometry before concatenation |
How It Works
How CyberTools Merges Video Clips
The current Video Merger does more than append source files. FFmpeg must first create compatible video and, when enabled, audio streams for every input. This normalization is important because the concat filter expects streams with compatible characteristics. After normalization, the streams are concatenated in the exact clip order selected in the interface and encoded into a new MP4 file.
1
Load Each Source into FFmpeg
Every selected file is written into the FFmpeg WebAssembly virtual file system inside the browser and added as a separate FFmpeg input.
2
Normalize Video Geometry
Each video stream is scaled to fit the chosen width and height using force_original_aspect_ratio=decrease. Padding is then added to center the picture inside the target frame when the aspect ratio does not match.
3
Normalize Frame Rate and Pixel Shape
The current filter forces each video stream to 30 FPS and applies setsar=1 so the normalized inputs use square pixels before concatenation.
4
Normalize Audio When Enabled
For every input, the audio path uses aformat with floating-point samples, a 44.1 kHz sample rate and stereo channel layout. If a source lacks the expected audio stream, an audio-enabled merge can fail; disabling audio provides a video-only path.
5
Concatenate the Normalized Streams
FFmpeg builds a filter_complex chain and applies concat with one video output and either one audio output or no audio output, depending on the Include Audio Tracks setting.
6
Encode and Finalize the MP4
The merged video is encoded with libx264 using the ultrafast preset and CRF 28. When audio is enabled, AAC at 128 kbps is used. The MP4 is finalized with +faststart before the browser exposes it for preview and download.
Choose the Right Settings
Which Video Merge Settings Should You Use?
Choose settings according to the source clips, the intended playback environment and your device resources. Upscaling a low-resolution source does not create genuine detail, while selecting a larger frame increases the amount of video data FFmpeg has to process.
| Goal |
Setting |
Why |
| General web video |
720p with audio |
720p is a practical middle ground for many web videos and requires fewer pixels to process than 1080p. |
| Full HD source clips |
1080p |
Use Full HD when the source material contains enough detail and the device has sufficient memory and processing capacity. |
| Faster or lighter processing |
360p |
The smaller frame contains far fewer pixels, which can reduce the workload compared with 720p or 1080p. |
| Clips with complete audio streams |
Include Audio Tracks |
The audio-enabled pipeline normalizes every source to 44.1 kHz stereo and concatenates the audio together with the video. |
| One or more clips have no audio |
Disable Include Audio Tracks |
The current audio filter references an audio stream for every input. Turning audio off avoids that dependency and produces a silent MP4. |
| Specific storytelling sequence |
Reorder clips before merging |
The concat chain uses the same order as the clip list. Changing sequence after export requires another merge. |
Quality, Frame Rate and Re-Encoding
How Merging Affects Video Quality, Size and Duration
The current implementation re-encodes the normalized streams, so the merged result is not identical to the original compressed video data. Resolution, scaling, frame-rate normalization, CRF and source quality all influence the final appearance. The duration is approximately the combined playable duration of the successfully processed clips, while output size depends on content complexity, duration, resolution and the H.264 encoding result rather than a fixed size formula.
The Video Is Re-Encoded
Because scaling, padding, FPS normalization and concat filtering are applied, the pipeline encodes a new H.264 stream instead of copying the original compressed video packets.
CRF 28 Controls H.264 Quality
The current libx264 path uses CRF 28. CRF is a quality-oriented rate-control method; the resulting bitrate varies with the visual complexity of the merged content.
30 FPS Is the Common Output Frame Rate
Every input passes through fps=30 before concatenation. Source clips recorded at other frame rates are normalized to this common rate.
Aspect Ratio Is Preserved with Padding
The scale filter decreases the source to fit inside the target frame without stretching it, then pad fills the remaining area. Portrait clips can therefore appear with empty side regions in the landscape output frame.
Upscaling Does Not Create Missing Detail
Selecting 1080p for a low-resolution source increases the output frame dimensions but cannot restore detail that was never captured in the original clip.
Audio Is Re-Encoded When Included
Enabled audio is normalized before concat and the final audio stream is encoded to AAC at 128 kbps. It is not copied bit-for-bit from the sources.
Processing and Privacy
Where Are Your Videos Processed?
The main CyberTools Video Merger pipeline currently runs with FFmpeg WebAssembly in your browser. Source files are written into FFmpeg’s virtual file system for processing, and the resulting MP4 is read from FFmpeg memory and exposed through a browser object URL. This architecture keeps the core merge workflow on the device, but it also means performance is constrained by the browser, available RAM, processor speed and the codecs supported by the bundled FFmpeg build.
- Selected source clips are written to the FFmpeg virtual file system inside the browser during processing.
- Scaling, padding, frame-rate normalization, audio normalization, concatenation and encoding use your device CPU and memory.
- The completed MP4 is read from FFmpeg memory and made available for browser preview and download.
- Large files, long durations, high resolutions or many clips can exceed practical browser or device resource limits.
Important Limitations
What an Online Video Merger Cannot Do
This tool is designed for ordered sequential joining, not full timeline editing. Understanding that boundary helps you choose the correct tool and prevents incorrect assumptions about lossless joining, transitions or automatic media repair.
- The current merger does not perform lossless stream copy; video is normalized and re-encoded before export.
- It does not create transitions, fades, crossfades, picture-in-picture layouts, overlays or simultaneous multi-track compositions.
- It does not trim individual clips, remove unwanted sections or choose edit points automatically before merging.
- When audio is enabled, every source is expected to provide a usable audio stream. A missing audio stream can require disabling audio for the merge.
- The tool cannot recover detail lost in a low-quality recording, repair corrupted frames, stabilize shaky footage or enhance video using AI.
- Unsupported codecs, very large files, long videos or high-memory workloads can fail because browser FFmpeg processing is resource intensive.
Video Concepts
Video Merging, H.264, AAC, FFmpeg Concat and CRF Explained
These technical concepts explain why a reliable video merge often requires more than placing files next to each other. The source streams must have compatible characteristics before FFmpeg can concatenate them into one normalized output.
Video merger
A tool that combines multiple video clips into one output file, normally in a defined playback order.
FFmpeg concat filter
An FFmpeg filter that joins normalized video and optional audio streams sequentially into combined output streams.
H.264
The video compression format used by the current output path through the libx264 encoder.
AAC
The audio codec used for the final merged audio stream when Include Audio Tracks is enabled.
CRF
Constant Rate Factor, a quality-oriented x264 rate-control value. The current merger uses CRF 28.
Frame rate
The number of video frames displayed per second. The merger normalizes source clips to 30 FPS before concat.
Resolution
The pixel dimensions of the video frame. Available target presets are 640×360, 1280×720 and 1920×1080.
Aspect ratio
The proportional relationship between frame width and height. The scale-and-pad workflow preserves source proportions instead of stretching the picture.
Padding
Extra frame area added around a scaled source when its aspect ratio differs from the selected output frame.
FFmpeg WebAssembly
A browser-capable build of FFmpeg that performs decoding, filtering, concatenation and encoding within the web application.
Frequently Asked Questions
Video Merger FAQ
Answers about merging videos, clip order, resolution, aspect ratio, 30 FPS normalization, H.264, AAC, quality, browser processing and clips without audio.
How do I merge videos online?
Upload at least two supported videos, arrange the clips in the desired order, choose 360p, 720p or 1080p, decide whether to include audio and start the merge. The tool normalizes and concatenates the streams before exporting one MP4.
Can I change the order of videos before merging?
Yes. Move clips up or down in the list before processing. The FFmpeg concat chain follows the same top-to-bottom order.
Does the Video Merger preserve the original resolution?
Not necessarily. Every clip is scaled and padded into the target resolution selected in the interface: 360p, 720p or 1080p.
What happens if my videos have different aspect ratios?
Each source is scaled to fit inside the chosen frame while preserving its aspect ratio. Padding fills unused frame space so the picture is not stretched.
Does merging videos reduce quality?
The current implementation re-encodes the video using libx264 with CRF 28, so the output is not bit-for-bit identical to the sources. Final appearance depends on source quality, scaling and encoding.
What frame rate does the merged video use?
The current FFmpeg filter normalizes every input video to 30 frames per second before concatenation.
What format is the merged video?
The current tool exports an MP4 containing H.264 video. If audio is enabled, the merged audio is encoded as AAC at 128 kbps.
Why can merging fail when one video has no audio?
When Include Audio Tracks is enabled, the current filter expects an audio stream from each input. If a clip has no usable audio stream, disable audio and try a video-only merge.
Are my videos uploaded to a conversion server?
The main processing workflow currently runs in the browser through FFmpeg WebAssembly. Source files are written temporarily to FFmpeg’s virtual file system while the merge is processed.
Why can a large video merge fail in the browser?
FFmpeg needs memory and CPU for decoding every source, scaling and padding frames, normalizing streams, concatenating them and encoding the final MP4. Large or long clips can exceed available browser or device resources.