Support
Why getDisplayMedia Is Not Working
When `getDisplayMedia` fails, the root cause is usually one of a small set of browser-level issues: unsupported environment, insecure context, blocked permission flow, or a rejected capture request.
Free to use, no account required, and no watermark on exports.
In this article
Do this next
Confirm you are using a supported desktop Chromium browser on a secure HTTPS page.
Try the capture flow again and check whether the browser share dialog is being blocked or dismissed.
Use a short test capture to verify the browser can open the screen-share picker successfully.
Common questions
What does getDisplayMedia do?
It is the browser API that opens the screen-share picker and returns the screen, window, or tab capture stream used by browser-based recorders.
Why would getDisplayMedia fail on a working site?
The browser may block the share dialog, the page may not be in a secure context, or the environment may not support that capture flow.
Can the recorder work around a browser-level getDisplayMedia failure?
No. If the browser itself refuses or cannot provide the capture stream, the recorder cannot override that failure.
Start with browser and context checks
Browser-based screen recording depends on a secure context and a supported browser. If the page is not running in the right environment, `getDisplayMedia` will fail before recording can begin.
Why this error matters
This is the API behind browser-native screen capture itself. When it fails, the right fix is usually environment or browser-level, not a UI tweak inside the recorder.