No upload is not infinite capacity
The tool does not send the source to our server or enforce a server upload limit. The browser must still read the source, run the conversion engine, retain generated segments, and assemble a ZIP.
A file can therefore be too demanding for one tab even though no network upload occurs. Available memory, free disk space, browser limits, and CPU all matter.
Why output can need extra space
During conversion, source data, decoder and encoder state, segments, and the final ZIP may overlap in memory or temporary storage. The peak requirement can be substantially larger than the source file alone.
Transcoding a high-resolution MOV or WebM normally needs more resources than repackaging a compatible MP4.
- Longer duration means more segments
- Higher resolution increases frame memory
- Re-encoding increases CPU work
- ZIP creation needs room for generated output
Prepare for a large source
Use a current 64-bit desktop browser, connect the device to power, close memory-heavy applications, and keep ample free storage. Prevent sleep and leave the converter tab open.
First convert a short representative clip. It reveals codec and workflow problems before committing to the complete recording.
Recover from a failed attempt
Reload the tab to release the failed job, close other demanding tabs, and retry with a trimmed or lower-resolution source. If the same point fails repeatedly, use a native desktop encoding workflow with explicit resource control.
A browser crash does not upload or preserve the source on our server, so keep your original file separately.
Ready to create your HLS package?
Return to the converter. Your source file stays inside your browser.
Open converter