The architecture targets 12–24-hour workflows, but no 12-hour or 24-hour endurance result is claimed. A session writes encoded chunks sequentially to disk instead of retaining the full recording in a Blob array. The application queue includes the in-flight write and is limited to 32 MiB.
How to use it
- Prefer a powered desktop with enough disk space. Make a short test using the intended settings and source.
- Choose 15, 30 or 60-minute segments; 30 minutes is the default. Each segment stops its own MediaRecorder, drains final data, closes the file and then starts another recorder.
- Keep the tab open. Watch the queue and committed segment list. At high queue levels encoding pauses; a 15-second write deadline or queue overflow stops the session.
Limits and safety
Segment transitions have gaps, and a browser may internally buffer a large delayed chunk before JavaScript can reject it. A bounded application queue does not bound browser encoder memory. Wake Lock is best effort, not protection against OS sleep, crashes or power loss. Previously committed segments are separate; the active segment may be lost.
References
Check the result, not just the controls
A practical test
Test at least one automatic segment boundary before a long session. Open the earlier finalized file while the later segment is still being recorded, then stop normally and inspect the final file too. This checks both rotation and the last save. It does not prove that the same device can run unattended overnight; sleep, disk pressure and browser scheduling remain separate risks.