> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/ai-video/ai-video/overview.md). # Overview ## Is this the same Chrome extension used for interactive demos? No. Arcade has two separate Chrome extensions: | | Arcade: AI Interactive Product Demos | Arcade AI Videos | | ---------- | ---------------------------------------------------- | ------------------- | | Used for | Interactive, step-by-step demos (hotspots, callouts) | AI-generated videos | | Covered on | [Record](broken://pages/GOjwmtEwxAk3YCym93vt) | This page | Install the one that matches what you're making. If you make both kinds of content, install both — they don't conflict. ## How do I install the AI Video Chrome Extension? Install **Arcade AI Videos** from the Chrome Web Store. It's generally available to every signed-in customer — no waitlist or early access required. ## What can I capture with it? Open the extension on any page and it reads the page — text, images, and links (on a YouTube page, it watches the video itself). If your workspace uses Google Workspace, Arcade can also read Google Docs and Slides directly, not just regular web pages. From there, Arcade starts a conversation about the video you want, and you can: * Record the page you're on as a **video** * Capture a **screenshot** * Add your **camera and voice** to the recording Recording isn't something you have to choose up front — Arcade offers to record your screen partway through the conversation, when it's useful for the video you're making, or you can ask for it at any point. ## Can I open on camera and switch to my screen in one take? Yes. Start talking to the camera, then switch to your screen — Arcade picks the moment to cut from your face to your screen based on your speech and cursor movement, all in a single recording. Your webcam records at 720p, and the recording happens inside your conversation with the AI rather than as a separate capture step. ## Does the extension still ask me to add callouts, lower thirds, or title cards? No. The extension no longer prompts you to mark up your recording with callouts, lower thirds, or title cards before handing it off — it captures your footage and lets the AI handle the presentation layer in the video itself. ## What if I didn't say anything during my recording? If you record a silent take, the extension offers to generate an AI voiceover for it rather than leaving the clip without narration. ## Does it know what pages I visited while recording? Yes. Pages you visited during your recording are automatically added as context, so the AI has them available when it builds your video. ## How do I actually start recording? When Arcade offers to record (or you ask it to), open the `Record this tab` card. Toggle `Camera` and/or `Microphone` on if you want them — both are off by default — then click `Start recording`. Chrome will ask which tab to record; pick the one you're on. With the camera on, a 3-second countdown runs first so you can drag the round camera bubble into place before capture begins. ## What happens if my workspace is low on AI video credits? Arcade tells you before the interview starts, rather than partway through — so you're not interrupted mid-conversation after you've already answered questions. ## Where do I start a video from a page without recording anything? Use [Producer](/kb/ai-video/ai-video/producer.md) — point it at any page and it drafts a video brief from the page's content, no recording required. ## Related * [Producer](/kb/ai-video/ai-video/producer.md) * [AI Video](/kb/ai-video/ai-video.md) * [Record](broken://pages/GOjwmtEwxAk3YCym93vt) (interactive demos) --- # 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.arcade.software/kb/ai-video/ai-video/overview.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 `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.