> 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/screen-recorder/record-and-capture/screen-recording/webcam-and-camera-preview.md). # Webcam and camera preview Add a webcam preview while recording your screen. Camera access is optional. ## Set up your camera 1. Open the Screendesk extension and expand **Recording settings**. 2. Grant camera permission when prompted by Chrome and choose your camera. 3. Turn the camera toggle on. Choosing a device or granting permission does not turn the camera on by itself. 4. Position the preview before starting your recording. Drag the camera bubble to move it and resize it to fit your page. Screendesk remembers its position and size. The preview is not mirrored. ## Tab recordings The camera bubble appears on the page. It is included when it is visible within the captured tab. ## Desktop recordings Screendesk uses a separate picture-in-picture camera window while you select a screen, window, or tab in Chrome's sharing picker. The saved video contains the surface you chose. A separate camera window is not automatically added to a recording of another window or tab. To include it in a full-screen recording, keep the camera window visible on the screen you are sharing and check the result before uploading. Closing the camera window does not stop the screen recording. Use the recording controls to end the recording. ## If the camera does not appear Check Chrome's camera permission, your operating system's privacy settings, and whether another application is using the device. Reopen Recording settings and select an available camera. Turn the camera off to continue with a screen-only recording. --- # 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 dynamically 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/screen-recorder/record-and-capture/screen-recording/webcam-and-camera-preview.md?ask=&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 `build a script that syncs our docs to a CMS` 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.