Desktop long recordings require HTTPS, MediaRecorder and directory writing. Recent desktop Chromium browsers are the primary target. Mobile supports microphone recording with browser-local saving and export; screen/shared audio is not offered in this mobile version.
Microphone recording on mobile
This mobile version records microphone audio only. For screen recording or shared/system audio, use a compatible desktop browser.
Audio is temporarily saved in this browser. Export each completed segment using Download or Share → Save to Files. Clearing site data or private browsing can remove recordings.
Keep this page visible and your device awake. Switching apps or locking the screen triggers a stop attempt, but may interrupt saving. Export promptly; browser storage is not a backup.
Desktop recording
Long recording needs all three capabilities together: media capture, MediaRecorder encoding and showDirectoryPicker with writable files. A browser that can capture a screen but cannot write to a selected directory cannot start this recorder.
How to use it
- Use HTTPS or localhost. Recent desktop Chrome and Edge are the main intended environments, subject to permissions and actual API checks.
- Open the app and check its compatibility notice. For audio only, microphone access is required unless a live shared-audio track is available.
- Test the exact browser, OS and source. Check microphone, shared audio and output playback before relying on a long session.
Limits and safety
Do not assume mobile Safari, Firefox, an embedded browser, or every Chromium variant supports this workflow. Screen capture and shared audio have additional restrictions. No full-recording in-memory download fallback is offered; using a native recorder may be more appropriate on unsupported devices.
References
Check the result, not just the controls
A practical test
Check three gates separately: permission to capture the intended source, support for encoding the chosen format and permission to save the file. Passing one does not imply the others. A desktop browser narrowed to a phone-sized window is still different from a mobile device. When the required API is unavailable, use a supported browser or an appropriate native tool instead of repeatedly granting unrelated permissions.