> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/request-screen-recording/browser-compatibility.md).

# Browser compatibility

Which browsers and devices can record, and what to try when the recorder doesn't start.

The recorder runs in the browser. Customers don't install anything.

### On a computer

It records the screen in the latest Chrome, Edge, Firefox and Safari. The browser asks what to share (a tab, a window or the whole screen) and for the microphone. A browser too old to record video in a supported format shows a message asking to update it.

### On a phone or tablet

Mobile browsers can't share the screen, so the recorder films with the camera instead. Customers can switch between the front and back camera while recording.

### Limits

* Recordings stop at 10 minutes.
* Some browsers can't capture the computer's own sound, only the microphone.
* Browsers inside other apps (a link opened in a chat or social app) and strict company policies often block screen sharing.

### If the recorder doesn't start

1. Open the link in Chrome or Edge on a computer, not inside another app.
2. Turn off ad and privacy blockers for the page.
3. Reload, then allow screen sharing and the microphone when asked. A dismissed prompt only comes back after a reload.

Browser support for screen sharing: [Can I use getDisplayMedia](https://caniuse.com/?search=getdisplaymedia).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/request-screen-recording/browser-compatibility.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
