Browser Merging Limits and Performance

AVMergePro runs entirely inside your browser, which means performance depends on your device and memory limits. This guide helps you avoid slow or failed merges.

Key limits to know

• Memory: Browsers cap available memory for WebAssembly.
• File size: Very large files can fail or take a long time.
• CPU: Re-encoding is expensive on laptops and low-power devices.

Practical recommendations

• Keep each file under 2 GB when possible.
• Close other heavy tabs during merging.
• Use Copy mode for the fastest results.

Signs you are hitting limits

• Processing stalls at “Preparing files”.
• The browser tab becomes unresponsive.
• Out-of-memory warnings appear.

When to split files

• If the merge takes more than 10–15 minutes.
• If the browser crashes or reloads.
• If memory warnings appear repeatedly.

Best workflow for large files

1. Start with Copy mode and MP4 output.
2. Test a shorter clip to confirm settings.
3. Only re-encode if playback fails.