Begin with five quick checks
- Open the recording link in a new private window and confirm that the public page loads.
- Make sure the hostname is
kommodo.aiand the path begins with/recordings/. - Copy a fresh link from Kommodo if the original may be old or truncated.
- Use a current desktop browser and close memory-heavy tabs.
- Try the download once more on a stable network without a VPN or filtering extension that might block media hosts.
Do not publish the recording URL in a support issue. Share links can grant access to the recording. When reporting a bug, provide the visible error stage, browser name and version, approximate recording duration, and whether the public page opens—without including the recording identifier.
The failure occurs while finding the recording
Paste a Kommodo recording link from kommodo.ai means the URL points to another hostname. Return to the public recording page rather than a dashboard, redirect service, or copied text that contains extra punctuation. This does not look like a Kommodo recording link means the path shape is wrong or the recording identifier is missing.
Could not find a downloadable HLS playlist usually means the public page structure changed, the recording does not expose a compatible playlist, or access is restricted. Kommodo returned HTTP 404 can indicate a deleted or mistyped recording. An authorization status can indicate an expired or private link. Create a new authorized share link before investigating the media stage.
Unsupported video host is a security boundary. The resolver found a URL outside its approved Komododecks host family and refused to return it. Do not try to bypass that check; report the behavior through the Contact page so the host change can be reviewed safely.
The failure occurs while reading the playlist
A playlist HTTP error can mean the signed URL expired between resolution and download, the media host is temporarily unavailable, or a network product blocked the request. Refresh the public link and retry. If the problem is consistent across browsers and networks, the recording host may have changed its access policy.
The resolved file is not an HLS playlist means the response did not begin with the expected HLS marker. An intermediary may have returned an error page instead of media. This recording is encrypted is intentional: the tool will not request encryption keys or work around protected delivery.
CORS errors appear when the browser is not permitted to read the remote response. Extensions, enterprise policies, and remote response headers can affect the result. The MDN CORS error guide explains why JavaScript often receives only a general failure message.
Segments stall, retry, or fail
The technical details panel records bounded segment retries. One retry can be a harmless network interruption. Repeated failure at the same segment suggests an expired signed resource or a missing object. Failures scattered across different segments suggest network instability, filtering, or temporary CDN errors.
Average speed begins low and stabilizes as more bytes arrive. ETA is based on completed segments rather than exact remaining bytes, so segments of uneven size can make it move up or down. A background tab may slow when the browser applies power-saving policies. Keep the tab visible and the device awake during a long transfer.
If the connection changed during a download, start over with a fresh link. The current tool does not persist partial segments or resume an interrupted job.
The tab becomes slow or closes
Browser assembly is memory intensive. Downloaded segment arrays, MP4 fragments, and the final Blob can exist at the same time. A one-gigabyte final file can therefore require substantially more than one gigabyte of available memory. Mobile browsers and low-memory devices may close the tab without a detailed application error.
Close other tabs and applications, restart the browser, and use a desktop with more memory. Process one recording at a time. If the same long recording repeatedly exhausts the browser, request an official export or use an authorized desktop media workflow designed to write incrementally to disk.
The MP4 converter fails
The MP4 converter did not load can indicate that a security extension blocked the local script or that the build is incomplete. Refresh the site and confirm that other static assets load. The browser could not convert this HLS stream into MP4 means the transmuxer produced no compatible output.
Possible causes include unsupported codecs, fragmented MP4 segments instead of transport streams, separate audio renditions, timestamp discontinuities, or damaged media. Review recording format compatibility and how HLS transmuxing works. The downloader does not re-encode unsupported media.
The MP4 is ready but does not save
Check whether the browser blocked automatic downloads, whether the chosen folder has enough storage, and whether a security product quarantined the file. Select Save MP4 again before closing the page. A Blob URL is temporary; reopening it in a different browser session will not work.
After saving, test the beginning, middle, and end. If only part of the recording plays, do not treat the file as a successful archive. Repeat with a fresh link and stable network, or obtain an official export from the owner.