# Fraime.it Docs - Full Agent Context --- --- This file contains the plain Markdown version of every public docs page. --- --- --- title: "Fraime.it Docs" description: "Learn how to record, edit, protect, and export polished developer videos with Fraime.it." canonical_url: "/docs" markdown_url: "/docs.md" --- # Fraime.it Docs Learn how to record, edit, protect, and export polished developer videos with Fraime.it. Canonical URL: /docs Markdown URL: /docs.md Fraime.it is a native macOS recorder and editor for developer demos, tutorials, launch videos, and short-form product clips. Use these docs when you want practical guidance for a workflow, not marketing copy. Start with recording, then move through timeline editing, privacy, captions, creator formats, and export. ## Recommended path If you are new to Fraime.it, follow this order: 1. [Record your first video](/docs/recording-first-video) 2. [Check recording settings](/docs/recording-settings) 3. [Learn the timeline basics](/docs/timeline-basics) 4. [Use the inspector reference](/docs/inspector-reference) 5. [Add redactions before sharing](/docs/redaction-text-replacement) 6. [Generate subtitles](/docs/subtitles-transcription) 7. [Choose export settings](/docs/export-settings) For launch posts or social clips, continue with [Shorts and vertical export](/docs/shorts-vertical-export). For camera-heavy videos, read [webcam backgrounds and green screen keying](/docs/webcam-keying). ## Core workflows - [Record your first video](/docs/recording-first-video) - [Configure recording settings](/docs/recording-settings) - [Edit in the timeline](/docs/timeline-basics) - [Use the timeline editor reference](/docs/timeline-editor-reference) - [Find inspector controls](/docs/inspector-reference) - [Create Shorts and vertical clips](/docs/shorts-vertical-export) - [Clean up webcam backgrounds and green screens](/docs/webcam-keying) - [Redact secrets and replace sensitive text](/docs/redaction-text-replacement) - [Generate and style subtitles](/docs/subtitles-transcription) - [Choose export settings](/docs/export-settings) ## Polish features - [Style backgrounds, gradients, and generated wallpapers](/docs/backgrounds-gradients-wallpapers) - [Add a project-wide watermark](/docs/project-watermark) - [Add overlays, annotations, and visual assets](/docs/overlays-annotations-assets) - [Use Smart Zoom, manual zoom, 3D punch, and animation](/docs/zoom-3d-punch-animation) - [Tune cursor and keyboard HUD presentation](/docs/cursor-keyboard-hud) - [Polish audio and background framing](/docs/audio-background-polish) ## Advanced - [Set up the editor extension](/docs/extension-setup) - [Set up the Chrome browser extension](/docs/browser-extension-setup) - [Use AI-assisted editing](/docs/ai-assisted-editing) - [Set up the Agent API and MCP helper](/docs/agent-api-mcp) ## Account - [Understand billing, trial exports, and updates](/docs/billing-trial-updates) ## What Fraime.it records Fraime.it records local screen, webcam, audio, cursor, keyboard, scroll, and optional IDE metadata into a `.fraimeit` project package. The app keeps source recordings local by default and applies timeline edits during preview and export. ## Local-first by default Normal recording, editing, preview, and export workflows run on your Mac. Connected features such as billing, analytics, license validation, model downloads, and AI-assisted timeline requests may use network services when you choose those flows. ## Agent-readable docs Agents can read the same docs as plain Markdown: - [`/llms.txt`](/llms.txt) lists every docs page with canonical and Markdown URLs. - [`/llms-full.txt`](/llms-full.txt) contains all docs pages in one Markdown bundle. - [`/sitemap.md`](/sitemap.md) provides an agent-readable docs sitemap. - `/docs/.md` returns a Markdown version of a single docs page, such as [`/docs/timeline-basics.md`](/docs/timeline-basics.md). - Canonical docs URLs also support HTTP content negotiation: request `/docs/` with `Accept: text/markdown` to receive the Markdown version instead of HTML. ## Common outputs - Full-length tutorials and docs videos - Product walkthroughs and launch demos - Short-form clips in 9:16 - Internal technical walkthroughs - Redacted demos that hide secrets before publishing ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Agent API And MCP Setup" description: "Connect local agents to open Fraime.it projects through the Agent API and MCP helper." canonical_url: "/docs/agent-api-mcp" markdown_url: "/docs/agent-api-mcp.md" --- # Agent API And MCP Setup Connect local agents to open Fraime.it projects through the Agent API and MCP helper. Canonical URL: /docs/agent-api-mcp Markdown URL: /docs/agent-api-mcp.md Fraime.it can expose open projects to local agents through a local bridge and MCP helper. The app stays in control of project files, preview, undo, save, and export while agents propose structured edits. ## When to Use Agents Use the Agent API when you want help with structured timeline work: - Inspect open projects and timeline state - Create a working copy before broad changes - Add or update annotations, subtitles, overlays, and visual assets - Suggest trims, filler-word cuts, or speed-ups - Preview an edit plan before applying it - Export a project after review Do not use agents as the final privacy reviewer. Always manually check redactions and exported videos. ## Setup From the App Open Fraime.it and use the Agent API controls in the app settings or menu. - Copy MCP Config gives the configuration snippet for compatible local agent clients. - Copy Helper Path gives the local helper executable path. - Keep the Fraime.it app open while agents inspect or edit projects. - Open the project you want the agent to work with before asking for project-specific actions. If an agent cannot find the project, confirm the project window is open and the local bridge is running. ## Working Copies Use working copies for experiments, aggressive trims, launch clips, and alternate exports. Agent-created working copies use a visible `.agent` naming convention so the original recording stays separate. Keep the original project as source material and apply broad agent edits to a copy. ## Review Before Apply Agents can dry-run edits and describe what would change before applying the plan. Review the summary carefully, especially changes that affect: - Project timing and clip ranges - Redactions and text replacements - Subtitle timing - Export settings - Large sections of the timeline Apply only the edits you understand. If the plan is too broad, ask for a smaller one, such as only title cards, only filler cuts, or only overlay suggestions. ## Available Operation Types The bridge is designed around structured project operations, including: - Listing open projects - Opening projects - Reading project summaries and timeline data - Creating working copies or duplicates - Previewing edit plans - Applying edit plans - Undoing and redoing edits - Saving projects - Capturing frame snapshots - Exporting projects - Running transcription, OCR redaction analysis, smart trim, and filler-word analysis - Importing image assets into the project and placing them on the canvas - Renaming or deleting project packages Recording control tools currently report capability status rather than starting capture, because recording is still owned by the interactive macOS capture window and ScreenCaptureKit permission flow. Exact tool names depend on the MCP client, but the workflow should stay review-first: inspect, preview, apply, verify, save or export. ## Safe Prompting Good prompts are specific: - "Create a 30 second launch clip from this project, but preview the plan first." - "Add title cards at the major section changes." - "Suggest filler-word cuts from the transcript without applying them." - "Find places where a zoom or callout would help explain the UI." - "Prepare a vertical Short as a working copy." Avoid vague prompts like "make it better" when you care about timing, privacy, brand tone, or export format. ## Troubleshooting If the MCP client cannot connect, copy the config again from the current app build and verify the helper path. If project actions fail, make sure the project is open in Fraime.it. If edits apply but the result is not useful, undo in the app or return to the original project/working copy. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "AI-Assisted Editing And MCP" description: "Use Fraime.it with local agents to inspect projects, propose edits, and export." canonical_url: "/docs/ai-assisted-editing" markdown_url: "/docs/ai-assisted-editing.md" --- # AI-Assisted Editing And MCP Use Fraime.it with local agents to inspect projects, propose edits, and export. Canonical URL: /docs/ai-assisted-editing Markdown URL: /docs/ai-assisted-editing.md Fraime.it exposes structured timeline operations for AI-assisted editing. The goal is to let an agent work with project data while the macOS app stays in control of the project, preview, undo, save, and export path. Use AI-assisted editing when you can describe the outcome you want more easily than you can manually perform every timeline operation. ## What agents can do Agents can inspect clips, tracks, annotations, subtitles, overlays, visual assets, and export settings. They can create working copies, add titles or callouts, adjust timeline elements by ID, suggest trims, and help prepare exports. Assistant edits are review-first. Use the panel to inspect the current time and selection, ask for common edits, generate smart suggestions, and review proposed changes before applying them. Good requests include: - "Create a 30 second launch clip from this project." - "Add a title card, trim the intro, and suggest where callouts would help." - "Find filler words and typing-heavy sections I can speed up." - "Prepare a vertical Short, but show me the edit plan before applying it." - "Use this attached logo image as an overlay in the intro." ## Image attachments The in-app assistant composer supports attached images via the attach button or drag-and-drop. Attached images can be used as visual context for the assistant and can be imported into the project as canvas assets when you ask the assistant to place them in the video. Images used as assistant context are sent to the configured AI planner provider for analysis. Do not attach sensitive images unless you are comfortable with that processing. ## Working copies Agent-created projects use a visible `.agent` naming convention so the original recording stays separate. Use a working copy when asking for broader edits such as a launch demo, short product clip, or cleaned-up walkthrough. Use the original project for archival source material. Use working copies for experiments, aggressive trims, or alternate exports. ## Preview before apply Agents can dry-run edits and report what would change before applying the plan. Review the plan, then apply only the edits you want. Read the summary before accepting a plan. Pay special attention to edits that affect timing, export settings, redactions, subtitles, or large ranges of the timeline. ## Smart edit suggestions Fraime.it can suggest filler-word cuts from transcript words and speed-ups for silent typing stretches. These are reviewable suggestions, not automatic destructive edits. Suggestions should still be judged like human edits. A filler word may be part of natural speech, and a silent typing section may still be useful if the viewer needs to see the code appear step by step. ## Local control The local bridge is designed so Fraime.it owns the source project and export. The agent proposes structured edits, and the app applies them through the same timeline model used by the editor. For MCP helper setup, available operation types, and working-copy guidance, see [Agent API And MCP Setup](/docs/agent-api-mcp). ## Agent API controls The app includes Agent API controls for copying MCP configuration and the helper path. Use them when connecting Cursor, Claude Code, or another local agent client to open Fraime.it projects. Keep the project open in Fraime.it while the agent works. If a prompt could substantially change timing, privacy, subtitles, export settings, or large sections of the timeline, create or ask for a working copy first. ## What not to delegate Do not rely on an agent as the final privacy reviewer. Always manually check redactions and exported videos before publishing. Also avoid vague prompts like "make it better" when you need a specific outcome; describe the target audience, length, format, and tone. ## Troubleshooting If an agent cannot find the project, make sure the project is open in Fraime.it and the local bridge is running. If an edit plan is too broad, ask for a smaller plan first, such as only title cards or only filler-word suggestions. If the result is not what you wanted, return to the original project or a previous working copy. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Audio And Background Polish" description: "Clean up voice, mix music, set loudness, and style the canvas behind your recording." canonical_url: "/docs/audio-background-polish" markdown_url: "/docs/audio-background-polish.md" --- # Audio And Background Polish Clean up voice, mix music, set loudness, and style the canvas behind your recording. Canonical URL: /docs/audio-background-polish Markdown URL: /docs/audio-background-polish.md Polish controls are the last pass before export. Use them after the main edit is stable so you can judge the whole video as a viewer would hear and see it. ## Voice Presets Audio presets give you a starting point for common recording styles: - Raw keeps the capture close to the source. - Podcast Voice makes narration more present. - Clean Voiceover reduces rough edges in spoken tutorials. - Light Cleanup applies mild noise reduction and leveling. - Interview supports conversational audio. Pick the closest preset, then adjust advanced controls only when something still sounds wrong. ## Cleanup Use cleanup controls to solve specific problems. - Noise Reduction helps with fan noise, room tone, or background hiss. - Remove Hum targets 50 Hz or 60 Hz electrical hum. - De-Esser reduces harsh "s" sounds. - EQ adjusts low, mid, and high tone. - Compressor evens out quiet and loud parts. - Loudness normalization targets a consistent final level. Avoid over-processing. If voice starts to sound watery, dull, or unnatural, back off cleanup settings. ## Background Music Fraime.it includes a built-in music catalog across styles such as Lo-Fi, R&B, Hip-Hop, Electro, and Rock. Use music when it supports the pacing of a launch clip, short demo, or product video. Lower the music volume when narration or UI sounds matter. For technical tutorials, silence is often better than music that competes with explanation. ## Master Output Master controls affect the whole project mix. - Use master volume for final level changes. - Choose stereo when spatial feel matters. - Choose mono when the destination or source audio favors simple playback. Always listen through the final section of the video. Problems often appear near cuts, speed changes, or sections where background music starts or stops. ## Background Framing Background controls style the canvas around the screen recording. - Wallpaper creates a designed backdrop, including generated Minimal wallpapers. - Generated wallpapers can use soft mesh, organic blobs, folded planes, wavy bands, or rounded shapes. - Gradient adds depth without requiring an image, with linear and radial options. - Color keeps the frame simple and brandable. - Image lets you use a custom visual background. - Padding, corner radius, blur, and shadow affect how the screen sits in the canvas. Background framing matters most when the output aspect ratio differs from the source, such as Shorts 9:16, square posts, or 4:3 exports. For a deeper walkthrough of generated wallpapers, gradient stops, imported images, and frame controls, see [Backgrounds, Gradients, And Wallpapers](/docs/backgrounds-gradients-wallpapers). ## Final Polish Pass Before export, preview from the beginning and check: - Voice is clear at normal system volume. - Music supports the video and does not mask narration. - Loudness feels consistent across cuts. - Screen background does not distract from UI. - Webcam, subtitles, overlays, cursor, and keyboard HUD still have room. - Redactions remain visible against the final background and motion. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Backgrounds, Gradients, And Wallpapers" description: "Style the canvas with solid colors, gradients, procedural wallpapers, image backdrops, blur, padding, corners, and shadows." canonical_url: "/docs/backgrounds-gradients-wallpapers" markdown_url: "/docs/backgrounds-gradients-wallpapers.md" --- # Backgrounds, Gradients, And Wallpapers Style the canvas with solid colors, gradients, procedural wallpapers, image backdrops, blur, padding, corners, and shadows. Canonical URL: /docs/backgrounds-gradients-wallpapers Markdown URL: /docs/backgrounds-gradients-wallpapers.md Background controls define the canvas behind the screen recording. Use them when the source video does not fill the final aspect ratio, when you are making Shorts or square posts, or when a demo needs a more branded frame. ## Choose a background mode The Background inspector includes four main modes: - Wallpaper for built-in image and generated wallpaper presets. - Gradient for linear or radial color blends. - Color for a simple brand or neutral canvas. - Image for a custom imported backdrop. The background is part of the project state and exports with the final video. ## Use generated wallpapers Generated wallpapers live in the Minimal wallpaper category. They render from colors, a style, and a shape seed, so they do not require a large image asset. Available generated styles include: - Soft Mesh for blended glow fields. - Organic Blobs for soft abstract color regions. - Folded Planes for layered paper-like surfaces. - Wavy Bands for flowing horizontal motion. - Rounded Shapes for simple geometric layouts with light grain. After choosing a generated wallpaper, use Generated Shapes to switch styles. Use Colors to cycle through palette schemes, Shape to regenerate the procedural seed, or edit the four color wells directly. ## Tune gradients Gradient mode supports preset palettes and more detailed shaping: - Use linear gradients when you want direction and depth. - Use radial gradients when the screen should sit inside a soft glow. - Adjust angle for linear gradients. - Move the radial center and invert it when the highlight needs to sit behind or away from the source. - Add up to five gradient stops for more complex brand palettes. Keep gradients subtle enough that text, cursor movement, subtitles, and redactions remain readable. ## Import an image background Use Image mode when a custom visual is part of the brand system. Fraime.it copies the imported image into the `.fraimeit` project package so the project can reopen without depending on the original file location. For best results, choose a high-resolution image that still works when cropped to 16:9, 9:16, and 1:1. ## Frame the screen After choosing the background, tune how the source sits on the canvas. - Padding controls how much background is visible around the source. - Corner radius softens the source frame. - Blur can reduce distracting source edges. - Shadow and shadow distance separate the recording from the background. Background framing matters most when the output aspect ratio differs from the recording, such as vertical clips, square posts, or 4:3 exports. ## Export review Before exporting, scrub a few scenes and check: - The background does not compete with the screen content. - Gradient stops and generated shapes still work at the selected aspect ratio. - Shadows and rounded corners feel intentional. - Redactions, subtitles, cursor, keyboard HUD, webcam, and overlays remain readable. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Billing, Trial, And Updates" description: "Understand free exports, Pro plans, purchase restore, and app updates." canonical_url: "/docs/billing-trial-updates" markdown_url: "/docs/billing-trial-updates.md" --- # Billing, Trial, And Updates Understand free exports, Pro plans, purchase restore, and app updates. Canonical URL: /docs/billing-trial-updates Markdown URL: /docs/billing-trial-updates.md Fraime.it is designed so you can try the real workflow before paying. ## Free trial You get three clean exports free. Recording and editing do not require an account before you try the workflow. After the free exports are used, exporting requires Fraime.it Pro. Use the free exports for real tests, not just blank exports. A good trial flow is to record a short demo, add at least one timeline edit, verify redaction or subtitles if relevant, and export the finished result. The editor may show remaining clean exports in the toolbar or export access flow so you can tell when Pro is required before starting an export. ## Pro plans Pro unlocks unlimited clean exports. During the launch offer, monthly and yearly plans are discounted for new subscribers. The paid plan is focused on export access. You do not need a complicated feature matrix to decide whether Fraime.it fits your workflow: try the full recording and editing path first, then upgrade when you need unlimited exports. ## Billing Fraime.it uses Lemon Squeezy for checkout, taxes, invoices, subscription management, and customer billing flows. Use the account or billing links from the website when you need invoices, subscription management, or order lookup. ## Restore purchase Use your Lemon Squeezy receipt or My Orders page to find your license key. In the macOS app, choose Account, then Restore Purchase, and enter the license key. > Screenshot placeholder: Restore purchase flow > Show where to find the Lemon Squeezy license key and where to enter it in Fraime.it. Keep the license key somewhere you can access later. If you move to a new Mac or reinstall the app, you may need it to restore access. Use Manage Subscription when you need to update billing details, invoices, renewal, or cancellation through Lemon Squeezy. ## Updates Release builds include an in-app update checker powered by Sparkle when update settings are configured. You can also download the latest stable DMG from the Fraime.it website. ## Common questions ### Do I need an account before recording? No. You can record and edit locally before paying. ### Are trial exports watermarked? The trial is based on clean exports. After the free exports are used, exporting requires Pro. ### Where do I get the latest version? Use the download page for the latest stable DMG. Release builds can also check for updates inside the app when Sparkle is configured. ### What if restore fails? Check that the license key is copied exactly from Lemon Squeezy, that the app can reach the license service, and that you are using the purchase associated with the plan you expect. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Chrome Browser Extension Setup" description: "Stream privacy-aware browser interaction context into Fraime.it to power Smart Zoom and other context-aware edits." canonical_url: "/docs/browser-extension-setup" markdown_url: "/docs/browser-extension-setup.md" --- # Chrome Browser Extension Setup Stream privacy-aware browser interaction context into Fraime.it to power Smart Zoom and other context-aware edits. Canonical URL: /docs/browser-extension-setup Markdown URL: /docs/browser-extension-setup.md The Fraime.it Chrome extension streams privacy-aware browser interaction telemetry from Chrome into the local macOS app. When you record a browser-based demo, this context helps Fraime.it understand what you clicked, focused, selected, and scrolled to, not just the pixels on screen. You can record without the extension. Install it when the video is about a web app and you want Fraime.it to place Smart Zoom moves, highlights, and markers based on what you were actually doing in the browser. ## What the extension sends The extension is a Manifest V3 extension that observes browser interactions and forwards structured `browserEvent` payloads to the app. Each event can include: - An `eventType` such as `click`, `focus`, `input`, `selection`, `routeChange`, `scrollStop`, `modalOpen`, or `pageReady`. - The `page` origin, path, and a safe title. - The `viewport` size, scroll offsets, and device pixel ratio. - The interacting `element` tag, role, normalized and visible bounds, a safe label hint, coarse state, and privacy flags. - A normalized `selection` bounds and line-count estimate when applicable. - An `interactionWeight` used to rank importance for downstream features. It sends structured metadata with per-event privacy flags. It intentionally does not send full page contents. ## Why it helps Browser telemetry feeds Smart Zoom first: clicks, selections, input focus, and route changes give Fraime.it the focus region and an appropriate zoom scale, while generic scrolling stays gently framed. The same stream can also feed highlights, smart cuts, redaction hints, markers, cursor behavior, and caption context. ## Connection model The extension connects to the Fraime.it app over a local bridge on `127.0.0.1:49153` and posts events to `http://127.0.0.1:49153/browser-events`. Keep the app running while recording if you want browser context in the project. The connection is local to your Mac. If the app is not running, the extension cannot stream context into the recording. The toolbar icon appears grey while the bridge is unavailable and switches to the colored Fraime.it icon once browser telemetry is connected. ## Install flow [Install Fraime.it Browser Telemetry from the Chrome Web Store](https://chromewebstore.google.com/detail/fraimeit-browser-telemetr/ncnlpknpacieglbacpbjmolefaieohec). The Fraime.it recording window can open the store listing and use bridge events to show installed and connected status. For development or manual installs, load the extension unpacked: 1. Open `chrome://extensions`. 2. Enable Developer Mode. 3. Choose "Load unpacked". 4. Select the `browser-extension/chrome` folder. 5. Start Fraime.it so the local browser telemetry bridge listens on `127.0.0.1:49153`. > Screenshot placeholder: Browser extension connection > Show the Chrome extension toolbar icon switching to connected, and sample browser interaction context appearing in the Fraime.it timeline. ## Confirm it is working Record a short test while clicking and selecting in a web app. Open the project in Fraime.it and check whether browser context appears in the timeline, and whether Smart Zoom suggests zooms around the moments you interacted with. ## Privacy notes Because the extension sends structured interaction metadata with privacy flags rather than full page contents, Fraime.it learns where and how you interacted, not the complete text of every page. The screen recording itself can still contain visible content, terminals, secrets, or private data, so review redactions before export. ## Troubleshooting If browser context does not appear, make sure the app is open, the extension is enabled, Chrome can reach `127.0.0.1:49153`, and no other process is blocking the configured port. If the toolbar icon stays grey, the bridge is not connected, confirm Fraime.it is running and recording. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Cursor And Keyboard HUD" description: "Make pointer movement, clicks, shortcuts, and keypresses readable in the final video." canonical_url: "/docs/cursor-keyboard-hud" markdown_url: "/docs/cursor-keyboard-hud.md" --- # Cursor And Keyboard HUD Make pointer movement, clicks, shortcuts, and keypresses readable in the final video. Canonical URL: /docs/cursor-keyboard-hud Markdown URL: /docs/cursor-keyboard-hud.md Cursor and keyboard presentation help viewers understand interaction, especially in code editors, design tools, terminals, and product demos. ## Synthetic Cursor Synthetic cursor rendering replaces a hard-to-see captured pointer with a cleaner rendered cursor in preview and export. Use it when: - The cursor is too small after scaling or export. - A Retina capture needs a sharper pointer. - You want consistent cursor scale across the video. Tune cursor scale in the Cursor inspector, then preview sections with fast movement and clicks. ## Cursor Ring Cursor ring makes the pointer easier to track. - Enable the ring for dense UI or screen-share-style tutorials. - Adjust radius and width until it is visible without covering the target. - Choose a color that contrasts with both dark and light UI. Use a lighter ring for documentation videos and a stronger ring for short-form demos. ## Click Pulse Click pulse adds a ripple around clicks. Use it when the click itself matters, such as opening a menu, toggling a setting, or submitting a form. If every click pulses in a fast editing session, reduce intensity or disable it for a calmer final video. ## Idle Hiding Idle hiding removes the cursor after a period without movement. This is useful when the cursor stops over code, subtitles, a button, or a sensitive area. Set an idle timeout that hides the cursor only after the viewer has enough time to follow the interaction. ## Keyboard HUD The keyboard HUD renders keypresses and shortcuts into the video. - Enable it for keyboard-driven workflows. - Choose a position that does not cover code, subtitles, terminal output, or the webcam. - Use shortcut-only display when ordinary typing would be distracting. - Adjust hold time, scale, and opacity to fit the pace of the video. Keyboard HUD is especially useful for command palettes, terminal shortcuts, editor navigation, and demos where the action is not obvious from pixels alone. ## Review Checklist Before export, check: - Cursor is visible but not distracting. - Click pulses appear on meaningful interactions. - Idle hiding does not remove the cursor too early. - Keyboard HUD is readable at final resolution. - HUD placement does not collide with subtitles, webcam, or important UI. - Shortcuts shown in the HUD match the explanation. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Export Settings" description: "Choose output format, codec, frame rate, quality, aspect ratio, and resolution." canonical_url: "/docs/export-settings" markdown_url: "/docs/export-settings.md" --- # Export Settings Choose output format, codec, frame rate, quality, aspect ratio, and resolution. Canonical URL: /docs/export-settings Markdown URL: /docs/export-settings.md Fraime.it exports a finished video from the current timeline state. Export includes timeline edits such as redactions, subtitles, webcam keying, overlays, watermark, keyboard HUD, cursor rendering, generated wallpapers, gradients, backgrounds, and audio mix. Export is the point where timeline edits become a standalone video file. Watch a final preview before exporting if the project includes redactions, subtitles, webcam keying, or Shorts formatting. ## Export from the toolbar Use the editor toolbar Export button when the timeline is ready. The export sheet lets you choose file name, save location, format, codec, resolution, FPS, and compression. During export, Fraime.it shows progress and lets you cancel before the file is finished. Export uses the current timeline state, including the project End time, aspect ratio, canvas background, generated wallpaper or gradient settings, overlays, watermark, subtitles, audio mix, redactions, cursor, keyboard HUD, webcam layout, zoom, and 3D punch. ## Aspect ratio Choose the project ratio from the editor toolbar before exporting. Fraime.it supports source/native, 16:9, Shorts 9:16, 4:3, 1:1, and custom ratios. Use the Shorts template when you want a full vertical-video setup. Use manual ratio changes when you only want the canvas shape to change. ## Format and codec Use MP4 with H.264 for broad compatibility. Use HEVC when you want smaller files and know your publishing destination supports it. MOV is useful for some Apple-first workflows. ## Recommended presets - Tutorials and docs: MP4, H.264, 30 fps, 1920 x 1080, high quality. - Smooth UI demos: MP4, H.264 or HEVC, 60 fps, 1920 x 1080 or higher. - Shorts: MP4, H.264, 30 fps, 1080 x 1920, high quality. - Quick review: MP4, H.264, 30 fps, lower quality or smaller resolution. ![Fraime.it export settings sheet showing file name, save location, format, codec, resolution, FPS, compression, cancel, and export controls.](/docs/screenshots/export-settings-panel.png) _Export defaults follow the current performance recommendation, but you can still adjust file name, location, format, codec, resolution, FPS, and compression._ ## Frame rate Choose the frame rate that fits the recording and destination. 30 fps is a good default for tutorials and Shorts. 60 fps can help when motion or scrolling needs to feel smoother. Avoid exporting at a higher frame rate just because the option exists. If the recording was captured at 30 fps, a 60 fps export usually increases file size without adding real motion detail. ## Resolution Fraime.it supports aspect-aware presets, fixed sizes, and custom dimensions. Common choices include: - 1920 x 1080 for standard 16:9 video - 1080 x 1920 for Shorts 9:16 - 1080 x 1080 for square posts - 4K-style presets when you need higher fidelity Use source or aspect-aware presets when you want the export to follow the project canvas. Use fixed vertical presets when publishing to short-form platforms. ## Quality Higher quality increases file size. Use high quality for final publishing, and lower quality for quick review exports. ## Export review Before sharing the file, play the exported video and check: - Redactions are visible and baked in. - Subtitles render where expected. - Generated wallpapers, gradient stops, and imported background images match the preview. - Watermark placement and opacity match the preview. - Webcam keying looks like the preview. - Audio is present on the intended tracks. - The aspect ratio matches the destination. - The file opens in the target player or platform. ## Trial exports Fraime.it starts with three clean exports free. After those exports are used, exporting requires a paid Pro plan. The trial is based on exported files, not recording or editing time. Use trial exports for real end-to-end tests with the timeline edits you care about. ## Troubleshooting If the export looks different from preview, re-open the project and check whether the relevant track or setting is enabled at the export time. If the file is too large, lower resolution, quality, or frame rate. If a platform rejects the upload, try MP4 with H.264 and a standard resolution. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "VS Code-Family Extension Setup" description: "Connect your editor to Fraime.it so recordings include code context." canonical_url: "/docs/extension-setup" markdown_url: "/docs/extension-setup.md" --- # VS Code-Family Extension Setup Connect your editor to Fraime.it so recordings include code context. Canonical URL: /docs/extension-setup Markdown URL: /docs/extension-setup.md The Fraime.it extension streams editor metadata from VS Code-family editors to the local macOS app. This helps the timeline understand what file, language, cursor position, visible range, and function were active during a recording. You can record without the extension. Install it when the video is about code and you want Fraime.it to preserve editor context for later editing. ## What the extension sends The extension sends structured metadata, not document contents. The payload can include editor name, file path, language, cursor position, selection range, visible range, function name, and dirty or untitled flags. It intentionally does not send document contents or selected text. ## Why it helps Editor metadata can support context-aware timeline review, zoom/framing suggestions, AI-assisted edits, and clearer understanding of what happened during a coding session. It also makes it easier to identify important moments later without relying only on pixels. ## Connection model The extension connects to the Fraime.it app over a local TCP socket, typically on `127.0.0.1:49152`. Keep the app running while recording if you want editor context in the project. The connection is local to your Mac. If the app is not running, the extension cannot stream context into the recording. ## Supported editors Use the extension with VS Code-family editors such as Visual Studio Code, Cursor, and compatible forks that can install VSIX extensions. ## Install flow Use the in-app extension helper when available. For development or manual installs, build the VSIX from `vscode-fraimeit` and install it with your editor command-line tool. > Screenshot placeholder: Editor extension connection > Show the in-app extension helper, connected editor status, and sample IDE context appearing in the timeline. ```bash code --install-extension fraimeit-0.0.1.vsix cursor --install-extension fraimeit-0.0.1.vsix ``` After installing, restart or reload the editor if it does not connect immediately. ## Confirm it is working Record a short test while moving the cursor in a code file. Open the project in Fraime.it and check whether editor context appears in the timeline or inspector. ## Use IDE context in the editor When IDE context is present, Fraime.it can show editor events alongside the timeline. Use those events to find file switches, cursor movement, selections, visible range changes, and function-level context during a coding session. This context helps when deciding where to add zooms, callouts, lower thirds, smart edits, or assistant prompts. It also gives local agents more structure than a flat screen recording while still keeping document contents out of the bridge payload. ## Privacy notes Because the extension does not send document contents or selected text, Fraime.it sees where you were working, not the full source content. The screen recording itself can still contain visible code, terminals, secrets, or private data, so review redactions before export. ## Troubleshooting If context does not appear in the timeline, make sure the app is open, the extension is enabled, the editor can connect to localhost, and no other process is blocking the configured port. If you use multiple VS Code-family editors, confirm the extension is installed in the editor you are actually recording. Each editor manages extensions separately. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Inspector Reference" description: "Find the controls for every editor inspector tab and selected timeline element." canonical_url: "/docs/inspector-reference" markdown_url: "/docs/inspector-reference.md" --- # Inspector Reference Find the controls for every editor inspector tab and selected timeline element. Canonical URL: /docs/inspector-reference Markdown URL: /docs/inspector-reference.md The inspector is the right-side control area in the editor. It changes based on the active tab and the selected timeline or preview element. ## Background Use Background to style the canvas behind the screen recording. - Wallpaper, gradient, color, and image modes - Generated wallpaper styles such as Soft Mesh, Organic Blobs, Folded Planes, Wavy Bands, and Rounded Shapes - Palette and shape shuffle controls for generated wallpapers - Linear and radial gradients with adjustable stops - Blur, padding, rounded corners, and shadow - Image import for custom backgrounds Background settings are especially useful for Shorts, square posts, and demos where the captured source does not fill the final aspect ratio. See [Backgrounds, Gradients, And Wallpapers](/docs/backgrounds-gradients-wallpapers) for the full background workflow. ## Screen Use Screen for the main capture and timeline visibility. - Lane Visibility toggles for tracks you want to show or hide while editing - Preview details for source and playback context - Clip Speed controls for selected screen, webcam, or audio clips - Cursor segment details when cursor visibility items are selected - Selected zoom or 3D punch controls when those timeline elements are active Use speed changes for waiting, loading, repetitive typing, or other low-information moments. Keep important narration and UI interactions at normal speed unless the speed change is intentional. ## Camera Use Camera for webcam presentation. - Show or hide webcam picture-in-picture - Adjust PiP size, shape, position, opacity, and corner radius - Switch between normal background, background blur, person segmentation, and green screen - Tune key color, strength, tolerance, edge softness, and spill reduction - Add timeline layout segments when the webcam should move or change size over time See [Webcam Backgrounds And Green Screen Keying](/docs/webcam-keying) for a deeper workflow. ## Audio Use Audio for the project mix. - Master volume and stereo/mono output - Voice presets such as raw, podcast voice, clean voiceover, screencast, and interview - Background music style, track, and volume - Noise reduction, hum removal, de-ess, EQ, compressor, and loudness normalization See [Audio And Background Polish](/docs/audio-background-polish) for mix guidance. ## Subtitles Use Subtitles to generate and style captions. - Transcribe or re-transcribe audio - Edit subtitle text - Choose style preset, font size, position, max width, text color, background, opacity, and corner radius - Review subtitle segments against the timeline See [Subtitles And Transcription](/docs/subtitles-transcription) for review and export advice. ## Cursor Use Cursor to make pointer movement readable. - Enable synthetic cursor rendering - Adjust cursor scale - Add cursor ring and click pulse - Tune ring radius, width, and color - Hide cursor after idle time See [Cursor And Keyboard HUD](/docs/cursor-keyboard-hud) for presentation tips. ## Privacy Use Privacy before anything is shared. - Draw Rect for manual masks - Auto Detect for credential-like text - Blur or pixelate sensitive regions - Tune intensity and padding - Review manual and detected redactions - Draw & Replace visible text with safer values - Re-track replacements when source movement changes See [Redaction And Text Replacement](/docs/redaction-text-replacement) for safety guidance. ## Overlays Use Overlays for viewer guidance, imported assets, and project-level watermarking. - Add title cards, lower thirds, callouts, code snippets, step counters, and spotlights - Import PNG, JPEG, and SVG visual assets - Choose, replace, or remove a PNG, JPEG, or TIFF watermark logo - Toggle watermark rendering and adjust opacity - Position the watermark in the preview or with X, Y, W, and H percentage fields - Drag and resize overlay elements in the preview - Set Start, Duration, and End for selected annotations and assets - Adjust z-order and animations - Save or reuse presets where available See [Project Watermark](/docs/project-watermark) for persistent logo placement and [Overlays, Annotations, And Assets](/docs/overlays-annotations-assets) for exact timing and layout guidance. ## Keyboard Use Keyboard to render keypresses during playback. - Enable the keypress HUD - Choose position and display mode - Set hold time, scale, and opacity - Use shortcut-focused display for command-heavy videos The keyboard HUD is rendered into export when enabled. ## Animation Use Animation for timeline motion and emphasis. - Adjust global zoom smoothness - Add zoom, pan, reframe, or 3D punch moments - Tune tilt, depth, entry, and exit for 3D punch - Use presets for subtle or dramatic emphasis - Add spotlight emphasis for overlay-driven moments See [Zoom, 3D Punch, And Animation](/docs/zoom-3d-punch-animation) for examples. ## Editor The Editor tab appears when IDE context exists in the project. - Review file, selection, view, switch, and cursor events - Jump to recorded editor events - Use context as a guide for zooms, annotations, and assistant prompts See [VS Code-Family Extension Setup](/docs/extension-setup) for capture setup. ## Assistant Use Assistant for review-first AI editing. - Ask for timeline edits in natural language - Generate smart trim and filler-word suggestions - Review proposed actions before applying them - Use clarification replies when the assistant needs a narrower instruction See [AI-Assisted Editing And MCP](/docs/ai-assisted-editing) and [Agent API And MCP Setup](/docs/agent-api-mcp) for agent workflows. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Media Library And Segments" description: "Import videos or record additional screencast segments into an existing Fraime.it project." canonical_url: "/docs/media-library-segments" markdown_url: "/docs/media-library-segments.md" --- # Media Library And Segments Import videos or record additional screencast segments into an existing Fraime.it project. Canonical URL: /docs/media-library-segments Markdown URL: /docs/media-library-segments.md Use the Media Library when a project needs more source footage after the first recording. You can import a video file, record another screencast segment, keep it in the project library, and place it on the timeline when you are ready. ## Open the Media Library Open the editor, then choose the Media tab in the inspector. The project media list shows the original recording plus any imported videos or recorded segments. The original recording stays in place as the primary media item. New media is copied into the `.fraimeit` package so the project remains portable. ## Import a video 1. Click **Import Video**. 2. Pick one or more video files. 3. Fraime.it copies the files into the project package and appends them to the timeline. Imported videos can be appended again or inserted at the current playhead from the Media Library row. ## Record a new segment Click **Record Segment** from the Media Library. Fraime.it opens the normal recording window with a visible banner showing that the capture will be added to the current project. When you stop recording, the segment is saved into the existing project and appears in the Media Library. Segment media keeps its own capture sidecar so cursor, click, keyboard, scroll, IDE, and browser metadata can stay tied to the source recording. ## Place media on the timeline Each non-primary media item has two placement actions: - **Append** places the media after the existing screen track content. - **Insert at Playhead** splits at the playhead, ripples later content forward, and places the media at that point. After inserting media in the middle, review nearby audio, subtitles, overlays, redactions, and zoom segments so pacing still feels intentional. ## Export behavior Preview and export resolve screen frames per clip, so segments and imported videos can render from their own source file. If the project has an audio lane, placed media also gets a paired audio clip so the exported video can include its sound. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Overlays, Annotations, And Assets" description: "Add titles, callouts, code snippets, spotlights, images, SVGs, watermarks, and precisely timed visual elements." canonical_url: "/docs/overlays-annotations-assets" markdown_url: "/docs/overlays-annotations-assets.md" --- # Overlays, Annotations, And Assets Add titles, callouts, code snippets, spotlights, images, SVGs, watermarks, and precisely timed visual elements. Canonical URL: /docs/overlays-annotations-assets Markdown URL: /docs/overlays-annotations-assets.md Overlays help turn a raw recording into a clear story. Use them when the viewer needs a label, callout, visual beat, logo, imported image, watermark, or exact timing cue. ## Annotation Types Fraime.it includes several built-in annotation types: - Title Card for opening hooks, section breaks, or conclusions - Lower Third for speaker names, feature names, or short context - Callout for pointing at a region of the screen - Code Snippet for readable code-focused emphasis - Step Counter for structured walkthroughs - Spotlight for dimming everything except the important region Add overlays from the Overlays inspector, then select the overlay to edit content, style, timing, animation, and z-order. ## Imported Visual Assets Use visual assets for logos, badges, product images, diagrams, and design elements. - PNG and JPEG are useful for screenshots and raster art. - SVG stays sharp when scaled or used with zoom. - Imported assets live in the project package and can be reused in the timeline. - Drag assets in the preview to position them and resize them visually. Keep visual assets short and purposeful. If an imported image stays on screen too long, it can compete with the screen recording. ## Project Watermark Use the Watermark card when a logo should stay visible across the whole project instead of appearing as a timed asset. - Choose a PNG, JPEG, or TIFF logo. - Drag the watermark in the preview to reposition it. - Drag a corner handle or use percentage fields for exact size and placement. - Adjust opacity so the logo supports the video without blocking the content. The watermark is saved in the `.fraimeit` project and rendered into export. Subtitles stay above it for readability. For the full workflow, see [Project Watermark](/docs/project-watermark). ## Exact Timing Selected annotations and visual assets expose Start, Duration, and End fields in the inspector. - Start moves the beginning of the element. - Duration changes how long it remains visible. - End changes the element endpoint. - Move to Current Time places the selected annotation at the playhead while preserving its duration. Use numeric timing when an overlay needs to line up with narration, a cursor action, or the start of a new section. Use drag handles for rough placement, then refine with fields when precision matters. ## Canvas Placement Most overlays can be positioned directly in the preview. - Drag to place the element. - Resize using preview handles when available. - Keep overlays away from subtitles, important UI, and redaction masks. - Review vertical and square aspect ratios after changing the project ratio. For Shorts, use fewer words and larger visual hierarchy. A lower third that works in 16:9 may be too small for 9:16. ## Z-Order Z-order controls which visual elements appear above others. Use it when a title, callout, asset, webcam, subtitle, or spotlight overlaps another element. As a rule, privacy masks should remain visually obvious and should not be hidden behind decorative overlays. Review any section where overlays and redactions overlap. ## Animations Animations can help an overlay enter, emphasize, or leave without feeling abrupt. - Use subtle motion for documentation videos. - Use stronger motion for launch clips or Shorts. - Keep animation duration short enough that it supports the point instead of delaying it. Avoid stacking several attention devices at the same moment. A callout, cursor pulse, zoom, and title can each help, but all together can make the viewer unsure where to look. ## Practical Uses - Add a title card for the first few seconds of a product demo. - Place a lower third when introducing a feature or speaker. - Use a callout when the important control is small. - Add a code snippet when the visible IDE text is too dense. - Use a step counter for multi-step setup. - Import a logo or product screenshot for a launch clip. - Add a project watermark when every exported frame should carry the same brand mark. - Use spotlight emphasis when the screen is visually busy. ## Export Review Before exporting, check overlays at normal playback speed: - Text is readable. - Timing matches narration and cuts. - Assets do not cover subtitles, controls, or sensitive data. - Animations feel intentional. - Z-order is correct through the whole section. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Project Watermark" description: "Add a project-wide logo watermark, position it in the preview, and keep it consistent through export." canonical_url: "/docs/project-watermark" markdown_url: "/docs/project-watermark.md" --- # Project Watermark Add a project-wide logo watermark, position it in the preview, and keep it consistent through export. Canonical URL: /docs/project-watermark Markdown URL: /docs/project-watermark.md Use a project watermark when every exported frame should carry the same logo or brand mark. Unlike timed visual assets, the watermark is a project-level setting: it stays active for the full timeline and is saved with the `.fraimeit` project. ## Add a logo Open the Overlays inspector and use the Watermark card. 1. Choose a PNG, JPEG, or TIFF logo. 2. Fraime.it copies the logo into the project package. 3. Render watermark turns on automatically after a logo is selected. 4. Use Replace or Remove when the brand asset changes. The watermark uses the imported image's aspect ratio when it is first placed, so wide logos and square marks start with different default sizes. ## Position and resize After choosing a logo, adjust it directly in the preview. - Drag the logo to move it around the canvas. - Drag a corner handle to resize it while keeping the image aspect ratio. - Use the X, Y, W, and H percentage fields when you need exact placement. - Keep it away from subtitles, privacy masks, and important product UI. Fraime.it keeps the watermark inside the normalized canvas bounds. If you type a value outside the valid range, the project is normalized back into the visible frame. ## Tune opacity Use Opacity to make the watermark visible without competing with the recording. A lower value works well for persistent brand marks, while a higher value is useful for outro cards or asset-light demos. ## Layering The watermark renders above the canvas, screen content, webcam, annotations, imported visual assets, cursor, keyboard HUD, zoom effects, and 3D punch effects. Subtitles stay above the watermark so captions remain readable. Because redactions are safety-critical, review any scene where a watermark overlaps sensitive content. Do not rely on a watermark to hide private information. ## Export review Before exporting, scrub a few sections and check: - The watermark is enabled. - The logo remains readable against bright and dark backgrounds. - It does not cover subtitles, redactions, or important controls. - The position still works after changing aspect ratio. Export bakes the watermark into the final video together with the rest of the timeline state. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Recording Your First Video" description: "Capture a local screen, window, webcam, audio, and editor context in a Fraime.it project." canonical_url: "/docs/recording-first-video" markdown_url: "/docs/recording-first-video.md" --- # Recording Your First Video Capture a local screen, window, webcam, audio, and editor context in a Fraime.it project. Canonical URL: /docs/recording-first-video Markdown URL: /docs/recording-first-video.md ## Before you record Fraime.it requires macOS 15 Sequoia or later. The first time you record, macOS may ask for Screen Recording, Microphone, Camera, and Accessibility permissions depending on the options you enable. Before a real take, close private tabs, notification-heavy apps, password managers, and anything that might reveal customer data. Fraime.it can redact after the fact, but a cleaner source recording is always easier to ship. ## Quick checklist - Pick the app, window, display, or area you want viewers to focus on. - Decide whether the video needs webcam, microphone, system audio, or both audio sources. - Connect the editor extension before recording a coding session. - Do a short test recording if this is your first time using a source, microphone, or camera. - Make sure macOS permissions are granted before the important take. ## Choose a source Open Fraime.it and pick the display, window, or area you want to capture. Use a window source when you want a focused app demo. Use a display or area source when the walkthrough moves across multiple apps. ![Fraime.it recording setup window showing source selection, preview, camera, audio, microphone, capture quality, and frame rate controls.](/docs/screenshots/capture-source-picker.png) _Choose a display, window, or area, then confirm camera, audio, microphone, quality, and frame rate before recording._ Use area capture when the important content is smaller than the full display. This can make later framing, zoom, and Shorts exports cleaner because there is less irrelevant space around the subject. ## Configure capture Choose the frame rate, retina capture setting, audio mode, and webcam option before starting. Fraime.it can capture system audio, microphone audio, both, or neither. If you are recording a coding session, install and enable the VS Code-family extension so the project includes editor metadata such as file path, language, cursor position, visible range, and function scope. For a full explanation of the Capture, Audio, Webcam, Editor, Performance, and Advanced settings tabs, see [Recording Settings Reference](/docs/recording-settings). ## Choose audio deliberately Use microphone audio for narration. Add system audio only when the app sound matters to the viewer. If you are recording a quiet coding walkthrough, microphone-only is often easier to mix and clean up later. ## Use webcam only when it helps Webcam can make tutorials feel more personal, but it also takes space in the frame. If the final video is a vertical Short, consider recording webcam and then using the Shorts template plus background removal to create a compact picture-in-picture layout. You do not need to perfect webcam background treatment during capture. Fraime.it records the camera track so you can later adjust picture-in-picture layout, background blur, person segmentation, or green-screen keying in the editor. ## Start and stop Start recording from the app. When you stop, Fraime.it saves a `.fraimeit` package under your Movies folder. That package contains the screen recording, optional webcam recording, sidecar metadata, and timeline data used by the editor. ## Review the recording After recording, open the project and check: - The screen source is the one you intended. - Audio is present and not clipping. - Webcam appears when expected. - Cursor and keyboard presentation are usable. - IDE context appears if you recorded with the extension. ## Next step Open the saved project in the editor, review the timeline, then trim, annotate, redact, subtitle, or export the recording. ## Troubleshooting If the screen is black or missing, check macOS Screen Recording permission and restart the app after granting it. If microphone or camera is missing, check the corresponding macOS privacy permission. If editor context is missing, make sure the extension is installed, enabled, and connected before starting the recording. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Recording Settings Reference" description: "Choose capture, audio, webcam, editor, performance, and advanced recording options." canonical_url: "/docs/recording-settings" markdown_url: "/docs/recording-settings.md" --- # Recording Settings Reference Choose capture, audio, webcam, editor, performance, and advanced recording options. Canonical URL: /docs/recording-settings Markdown URL: /docs/recording-settings.md Use the recording settings before a real take to confirm what Fraime.it will capture and which sidecar data will be available later in the editor. ## Capture The Capture tab controls the screen source and capture quality. - Source can be a full display, a single window, or a selected area. - Area capture is useful when the important content is smaller than the full display or when you want cleaner Shorts framing later. - Frame rate is commonly 30 fps for tutorials and 60 fps for smoother scrolling or UI motion. - Retina capture preserves sharper UI detail when the destination needs it, but can increase recording and export workload. If a source is missing or black, check macOS Screen Recording permission and restart Fraime.it after granting access. ## Window and Area Capture Use a window source when the whole video stays in one app. Use a display source when the walkthrough moves between apps. Use area capture when only a region matters. For area capture, select an area on screen and verify the live preview before recording. The selection defines the raw screen content saved into the project, so include enough room for menus, popovers, or terminal output that may appear during the take. Window resize presets can help make app demos more consistent. If resize controls are unavailable, grant Accessibility permission so Fraime.it can manage compatible windows. ## Audio Fraime.it can record system audio, microphone audio, both, or neither. - Use microphone audio for narration. - Add system audio only when app sound matters to the viewer. - Pick the intended microphone before recording a long take. - Do a short test if you changed audio devices, aggregate devices, or headset settings. After recording, use the Audio inspector to apply voice presets, cleanup, loudness, and background music. ## Webcam The Webcam tab controls whether a camera track is recorded and how it appears during capture preview. - Enable webcam when face cam helps the explanation. - Use Visible when you want the camera shown in the recording preview. - Use Full Frame when you want the full camera feed saved for later layout decisions. - Choose camera shape, position, size, opacity, and corner radius for the initial picture-in-picture look. Webcam placement can still be changed later in the editor. Background removal, blur, and green-screen keying are timeline edits, not decisions you must finalize before recording. ## Editor The Editor tab shows the local IDE bridge and Agent API setup controls. - Install the VS Code-family extension when recording coding sessions. - Confirm the connected editor status before starting a take that depends on IDE context. - Use Copy MCP Config and Copy Helper Path when setting up local agents to work with open projects. The IDE bridge sends structured editor metadata such as file path, language, cursor position, visible range, and function scope. It does not send document contents or selected text. ## Performance Performance Mode balances quality, power use, and preview/export cost. - Automatic is the safest default. - High Quality favors fidelity for important captures. - Balanced is a good general-purpose setting. - Low Power is useful when recording on battery or under heavy system load. If preview or export feels slow, check this setting before lowering the final export quality. ## Advanced Advanced settings are mostly for diagnostics and integration setup. - Show Context Debug Overlay helps verify incoming IDE, cursor, scroll, or keyboard metadata. - IDE bridge status helps confirm that local editor context is arriving. - Extension install messages can help troubleshoot a manual VSIX install or removal. Leave debug overlays off for normal recording so they do not distract from the source content. ## Preflight Checklist Before a long recording, confirm: - The selected source is the app, display, window, or area you intended. - Screen Recording, Microphone, Camera, Accessibility, and Input Monitoring permissions are granted when needed. - The microphone and system audio choices match the video. - Webcam is enabled only when it adds value. - IDE context is connected for code-heavy videos. - Frame rate, Retina, and Performance Mode match the destination. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Redaction And Text Replacement" description: "Hide credentials, mask sensitive regions, and replace visible text before export." canonical_url: "/docs/redaction-text-replacement" markdown_url: "/docs/redaction-text-replacement.md" --- # Redaction And Text Replacement Hide credentials, mask sensitive regions, and replace visible text before export. Canonical URL: /docs/redaction-text-replacement Markdown URL: /docs/redaction-text-replacement.md Fraime.it includes privacy tools for developer recordings where secrets, account IDs, emails, URLs, or customer data may appear on screen. Run privacy review before you publish, even if you think the recording is clean. Developer tools can reveal tokens in logs, URLs, terminal output, headers, config files, dashboards, and environment panels. ## Automatic credential detection The privacy analyzer uses on-device OCR to scan for API keys, tokens, and similar credentials. Review detections in the privacy lane before exporting. Pick the privacy tool based on the risk. Draw Rect is fastest for manual masks, Auto Detect helps find credential-like strings, and Draw & Replace keeps the video readable with safer text. Automatic detection is focused on credential-like strings. It is a safety net, not a substitute for manual review of private product data, customer details, internal URLs, or anything specific to your organization. ## Manual Draw Rect Use Draw Rect when you need to mark something the automatic analyzer should not guess, such as a custom identifier, account page, terminal output, or private dashboard value. Fraime.it anchors manual masks to detected text where possible, so the mask can follow content as it scrolls or moves. After drawing a region, scrub through the affected time range. Make sure the mask follows the target while scrolling, resizing, or switching tabs. ## Blur or pixelate Choose blur or pixelate, then tune the mask intensity and bleed. Use enough padding to cover anti-aliased edges and movement between frames. Blur is usually less visually harsh for product demos. Pixelate is more obvious and can be better when you want reviewers to notice that something was intentionally hidden. ## Text replacement Text replacement is useful when you want the video to remain readable while hiding the real value. Replace a hard-coded string with a safer substitute, then style it to blend with the surrounding UI. Good replacements preserve the shape of the explanation. For example, replace a real API token with `sk_test_...`, a customer name with `Acme`, or a private email with `dev@example.com`. ## Privacy review checklist Before exporting, check: - Terminal output and stack traces - Browser address bars and query strings - API clients and request headers - Environment files and config panels - Customer names, emails, IDs, and billing screens - Dashboards, database rows, and admin pages - Clipboard managers, notifications, and menu bar popovers ## Export safety Redactions and text replacements are rendered into the exported file. The original recording remains in the local project package, so treat source projects as sensitive if they contain secrets. ## Troubleshooting If a mask drifts, shorten the affected segment and add another manual redaction. If text replacement looks misaligned, adjust the replacement styling or fall back to blur/pixelate for that section. If you are unsure whether a value is sensitive, redact it. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Shorts And Vertical Export" description: "Use Fraime.it to turn a walkthrough into a 9:16 short-form video." canonical_url: "/docs/shorts-vertical-export" markdown_url: "/docs/shorts-vertical-export.md" --- # Shorts And Vertical Export Use Fraime.it to turn a walkthrough into a 9:16 short-form video. Canonical URL: /docs/shorts-vertical-export Markdown URL: /docs/shorts-vertical-export.md Fraime.it includes a Shorts workflow for launch clips, social posts, and short product demos. Shorts work best when they focus on one outcome. If the full walkthrough explains a whole feature, the vertical version should usually show the hook, one proof point, and a clear ending. ## Apply the Shorts template In the editor toolbar, choose the Shorts template. It sets the project to a 9:16 canvas, chooses a 1080 x 1920 MP4 export, tightens the background framing, applies a bold subtitle style, adds an opening hook title card, and places the webcam for a vertical layout. ![Fraime.it editor ratio menu showing Apply Shorts Template and Shorts 9:16 options.](/docs/screenshots/shorts-template-menu.png) _The ratio menu includes the one-click Shorts template as well as manual aspect-ratio options for vertical clips._ After applying it, scrub the timeline from the beginning. Template defaults give you a strong starting point, but you should still check title text, subtitle placement, webcam overlap, and whether the screen content remains readable in a narrow frame. ## Choose an aspect ratio manually You can also choose aspect ratios without applying the full template: - Source or native - 16:9 - Shorts 9:16 - 4:3 - 1:1 - Custom Manual aspect changes are useful when you want vertical framing without changing subtitles, webcam layout, or title cards. ## Prepare the clip Short-form videos usually need a faster opening than long tutorials. Trim setup time, add a title or hook, use subtitles, and keep the visual focus on one idea. ## Build a short-form structure A simple structure works well: 1. Hook: show the result or state the problem. 2. Proof: show the key interaction or transformation. 3. Payoff: show the final screen, result, or viewer takeaway. For developer demos, avoid starting with installation, setup, or navigation unless that is the point of the clip. ## Keep text readable Vertical video makes screen UI smaller. Use zoom, crop/framing, callouts, and subtitles to reduce how much the viewer has to read. If code is too small, show only the relevant region instead of the whole IDE. ## Export vertical video Use 1080 x 1920 for the highest-quality vertical preset or 720 x 1280 for a smaller file. MP4 with H.264 is the safest default for social platforms. ## Platform-safe review Before publishing, check the video with mobile overlays in mind. Keep important subtitles and UI away from the very bottom where platform captions, buttons, or descriptions often appear. ## Reuse the same project You can keep a full walkthrough and a short-form export in the same project workflow by duplicating the project or saving a separate edit before applying aggressive vertical formatting. ## Troubleshooting If the recording feels too small in 9:16, add zoom or reduce background padding. If subtitles compete with the UI, move them higher or reduce max width. If the webcam blocks controls, switch to a smaller picture-in-picture layout or remove the background so it takes less visual space. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Subtitles And Transcription" description: "Generate editable subtitles for tutorials, launch clips, and Shorts." canonical_url: "/docs/subtitles-transcription" markdown_url: "/docs/subtitles-transcription.md" --- # Subtitles And Transcription Generate editable subtitles for tutorials, launch clips, and Shorts. Canonical URL: /docs/subtitles-transcription Markdown URL: /docs/subtitles-transcription.md Fraime.it can transcribe speech into subtitle segments with word timing. Transcription is designed to run on-device, and model files may be downloaded when needed. Subtitles help viewers follow technical videos without sound and make short-form clips easier to understand when watched quickly. ## Generate subtitles Open the subtitle controls in the editor and start transcription. When the pass completes, review the generated segments in the timeline and preview. ![Fraime.it subtitles inspector with Transcribe Audio, subtitle presets, position, opacity, radius, width, and color controls.](/docs/screenshots/subtitle-style-controls.png) _Start transcription from the subtitles inspector, then tune preset, placement, size, opacity, width, and colors before export._ For best results, record clear microphone audio and reduce background noise before transcription. If the first transcription pass is based on noisy audio, expect more manual cleanup. ## Edit timing and text Subtitles are timeline elements. Adjust text, timing, and styling when the automatic transcript needs cleanup or when you want a punchier caption for a short-form clip. Keep each subtitle short enough to read at playback speed. Split long sentences, remove filler when it does not affect meaning, and rewrite captions that are technically correct but too dense for video. ## Style subtitles Use subtitle style presets or inspector controls to tune typography, placement, width, background, corner radius, and visual weight. The Shorts template applies a bolder style for vertical video. Use stronger subtitle styling for Shorts and social clips. Use calmer styling for documentation videos where the screen content is the main subject. ## Avoid covering UI Subtitles can hide controls, code, command output, or redaction masks. Watch sections with important UI and move subtitles if they cover the thing you are explaining. ## Use subtitles with smart edits Transcript words also support smart edit suggestions such as filler-word cuts. Review suggested edits before applying them so the pacing still feels natural. Smart edits are most useful after transcript cleanup. If words are misrecognized, fix important transcript text before relying on filler-word suggestions. ## Export with captions baked in Subtitles render into the exported video. If you need platform-native captions, keep a separate transcript as part of your publishing workflow. ## Review checklist Before export, check: - Names, product terms, and commands are spelled correctly. - Captions appear long enough to read. - Captions do not cover important UI. - Styling is readable on both dark and light parts of the screen. - Shorts captions stay within mobile-safe areas. ## Troubleshooting If transcription fails, confirm the project has usable audio and that any required model download completed. If text is inaccurate, improve the source audio where possible and manually correct important terms. If subtitles lag after timeline edits, review nearby subtitle segment timing. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Timeline Basics" description: "Learn the main editing controls in the Fraime.it timeline." canonical_url: "/docs/timeline-basics" markdown_url: "/docs/timeline-basics.md" --- # Timeline Basics Learn the main editing controls in the Fraime.it timeline. Canonical URL: /docs/timeline-basics Markdown URL: /docs/timeline-basics.md The timeline is where a raw recording becomes a finished video. Fraime.it keeps screen, webcam, audio, subtitles, cursor, keyboard, overlays, redactions, and IDE context in one project so you can edit without leaving the app. ## A good editing order For most projects, work from broad edits to fine polish: 1. Remove obvious setup time, mistakes, and dead air. 2. Fix pacing with trims, splits, and speed changes. 3. Add privacy redactions before you forget what is sensitive. 4. Add subtitles, callouts, overlays, zoom, and 3D punch. 5. Tune webcam, cursor, keyboard HUD, background, and audio. 6. Choose export settings and watch a final preview. ## Review the tracks Use the track list to find the parts of the project you want to adjust. Common tracks include screen video, webcam, audio, subtitles, cursor, keyboard overlay, IDE context, zoom, 3D punch, annotations, overlays, and privacy redactions. ![Fraime.it timeline editor showing the preview, inspector, transport controls, and multi-track timeline.](/docs/screenshots/timeline-editor-overview.png) _The editor keeps the preview, inspector, transport controls, and timeline tracks visible in one workspace._ Keep related tracks visually aligned while editing. For example, if a split removes a section of the screen recording, review nearby subtitles, overlays, redactions, and audio so they still land at the right time. For a control-by-control overview of the editor, including transport controls, lane visibility, timeline tools, and the editable End time, see [Timeline Editor Reference](/docs/timeline-editor-reference). ## Transport and project length The transport bar shows the playhead time and the project End time. The playhead time is for navigation. The End time sets the overall project length used for preview and export. To edit the project length, click the right-side End number, type a time such as `1:20.00`, then press Return or click away. Press Escape to cancel while editing. Changing End does not automatically ripple-trim clips or overlays, so review the final seconds after shortening a project. ## Trim and split Use trim and split controls to remove setup time, pauses, repeated attempts, or dead air. If you need to preserve sync, keep related tracks aligned while editing. Use split when only the middle of a clip needs work. Use trim when the start or end is simply too long. If an edit changes the rhythm, play a few seconds before and after the cut rather than judging only the frame where the cut happens. Most clips and lane items are timed by dragging their body or edges in the timeline. Annotation overlays and imported visual assets also expose exact Start, Duration, and End fields in the inspector when selected. Need more footage after the first recording? Use the [Media Library](/docs/media-library-segments) to import videos or record another screencast segment into the same project, then append it or insert it at the playhead. ## Adjust pacing Speed changes are useful for repetitive typing, waiting, loading states, or setup work that viewers do not need to watch in real time. Keep narration and important UI interactions at normal speed unless the speed change is part of the style. ## Guide attention Use zoom, 3D punch, cursor settings, callouts, lower thirds, title cards, and overlays to direct the viewer to the important moment. Preview changes before exporting so the final render matches what you saw in the editor. Use one attention device at a time. A zoom, callout, cursor pulse, and keyboard HUD can all be useful, but stacking them on the same moment can make the video feel noisy. For deeper guides, see [Overlays, Annotations, And Assets](/docs/overlays-annotations-assets), [Zoom, 3D Punch, And Animation](/docs/zoom-3d-punch-animation), and [Cursor And Keyboard HUD](/docs/cursor-keyboard-hud). Overlay tools are for viewer guidance. Add title cards, lower thirds, callouts, code snippets, and step counters when the viewer needs more structure than the raw screen provides. ## Use the inspector The inspector changes based on the selected feature. Use it for background framing, screen appearance, webcam layout, audio cleanup, subtitle styles, cursor behavior, privacy masks, overlays, keyboard HUD settings, IDE context, and assistant actions. If you are not sure where a setting lives, select the timeline element or preview element first. The inspector is usually scoped to the selected part of the project. See [Inspector Reference](/docs/inspector-reference) for a tab-by-tab map of the editor controls. ## Preview like a viewer Before exporting, watch the video at normal speed and ask: - Is the first ten seconds clear? - Can a viewer follow where to look? - Are secrets, tokens, or customer data hidden? - Do subtitles cover important UI? - Does the webcam block anything important? - Are cuts, speed-ups, and transitions understandable? ## Save and export Fraime.it stores edits in the project package. Export creates a rendered video with timeline changes baked in, including redactions, subtitles, webcam mattes, overlays, and cursor or keyboard presentation. ## When to duplicate a project Duplicate the project before making a very different version, such as a full tutorial and a vertical launch clip. That gives you a clean way to keep separate pacing, subtitles, canvas settings, and webcam layout for each output. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Timeline Editor Reference" description: "Understand the editor layout, transport bar, timeline lanes, tools, and timing controls." canonical_url: "/docs/timeline-editor-reference" markdown_url: "/docs/timeline-editor-reference.md" --- # Timeline Editor Reference Understand the editor layout, transport bar, timeline lanes, tools, and timing controls. Canonical URL: /docs/timeline-editor-reference Markdown URL: /docs/timeline-editor-reference.md The editor combines preview, inspector, transport controls, and timeline lanes in one workspace. Use this page when you need to find a control or understand how timing changes affect the project. ## Editor Layout - Preview shows the current composed frame, including webcam, overlays, watermark, cursor, keyboard HUD, subtitles, redactions, and background. - Inspector changes based on the selected tab, clip, overlay, or preview element. - Timeline lanes hold screen video, webcam, audio, subtitles, cursor, keyboard, IDE context, zoom, 3D punch, overlays, webcam layout, and privacy redactions. - Transport controls handle play/pause, playhead position, project length, tool mode, undo/redo, and timeline zoom. Select a timeline item or preview element first when a setting seems missing. Many inspector controls are scoped to the current selection. ## Transport Controls The transport bar includes the current playhead time and the project end time. - The left time display follows the playhead. - The right time display is editable and sets the project End, also called project length. - Play/pause previews the current timeline state. - Jump controls move to the start or end of the current project range. - Timeline zoom changes how much time fits on screen; it does not change the exported video. - Undo and redo apply to timeline edit operations. ## Edit the Project End Time To change the project length with the End number: 1. Click the right-side End time in the transport bar. 2. Enter the new time in segmented time format, such as `1:20.00`. 3. Press Return or click away to apply it. 4. Press Escape to cancel while editing. Changing the End time sets the exportable project end. It does not automatically ripple-trim clips, subtitles, overlays, or redactions. After shortening the project, scrub near the new ending and make sure important elements still finish where expected. Use clip trimming when the source content itself is too long. Use the project End field when the overall project should stop at a specific time. ## Timeline Tools Fraime.it has several timeline interaction modes: - Select moves clips, trims handles, selects items, and lets you adjust preview elements. - Blade splits clips at the playhead. Review related subtitles, overlays, audio, redactions, and webcam layout after splitting. - Draw Rect creates manual privacy masks in the preview. - Draw & Replace creates text replacement overlays for sensitive strings. Use Blade when the middle of a clip needs work. Use trim handles when only the start or end is too long. ## Lane Visibility The Screen inspector includes lane visibility controls. Hide lanes you are not actively editing so the timeline stays focused, then show them again before final review. Common lanes include: - Screen video and webcam - Audio - Subtitles - Cursor and keyboard - IDE context - Zoom and 3D punch - Overlays, visual assets, and watermark - Redactions and text replacements - Webcam layout Hidden lanes can still affect preview and export if the underlying feature is enabled. Lane visibility is for editing clarity, not necessarily final render control. ## Media Library The Media inspector tab manages source videos in the current project. Use it to import videos, record additional screencast segments, append media to the end of the screen track, or insert media at the playhead with timeline ripple behavior. See [Media Library And Segments](/docs/media-library-segments) for the full workflow. ## Move and Trim Timeline Items Most timeline items use drag handles for timing: - Drag the body of a selected item to move it. - Drag the left or right edge to trim start or end. - Use timeline zoom when you need precise handles. - Play a few seconds before and after any edit to judge pacing. Screen, webcam, audio, subtitles, zoom segments, 3D punch segments, redactions, text replacements, cursor visibility, webcam layout, annotations, and visual assets all follow this general timeline model, though each item has its own minimum duration. The project watermark is different: it is positioned in the preview and applies across the whole timeline. ## Numeric Timing Fields Some selected elements expose exact timing in the inspector: - Annotation overlays include Start, Duration, and End fields. - Imported visual assets include Start, Duration, and End fields. - The project watermark uses placement and opacity fields instead of timing fields. - The project End field in the transport bar sets the overall project length. Other timing displays are read-only and should be adjusted by dragging timeline handles. Redaction cards, cursor ranges, and subtitle time labels show where the item lives, but the timeline lane is the primary way to change those spans. ## Project Workflow Fraime.it stores edits in the `.fraimeit` package and renders them during preview and export. Duplicate a project before making a substantially different version, such as a full tutorial and a short launch clip. Agent-created working copies use a visible `.agent` naming convention so experiments stay separate from source material. ## Final Timeline Review Before export, review: - Project End time and final seconds. - Cuts, speed changes, and split points. - Audio continuity around edits. - Subtitle timing and placement. - Redactions and text replacements through the whole affected range. - Overlays, watermark, webcam layout, cursor, keyboard HUD, zoom, and 3D punch during motion. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Webcam Backgrounds And Green Screen Keying" description: "Remove, blur, or key the webcam background after recording." canonical_url: "/docs/webcam-keying" markdown_url: "/docs/webcam-keying.md" --- # Webcam Backgrounds And Green Screen Keying Remove, blur, or key the webcam background after recording. Canonical URL: /docs/webcam-keying Markdown URL: /docs/webcam-keying.md Webcam background controls are timeline edits. You do not need to get the camera perfect during capture. Use these controls when the camera track is useful but the room, chair, wall, or green screen should not dominate the final frame. ## Choose a background mode Fraime.it supports three webcam background modes: - Normal keeps the camera track unchanged. - Remove Background uses person segmentation to isolate you from the room. - Blur Background softens the room while keeping the original environment visible. ![Fraime.it camera inspector controls for showing webcam picture-in-picture, size, shape, and corner radius.](/docs/screenshots/webcam-pip-controls.png) _First place the webcam: turn PiP on, set its size, choose a shape, and drag it in the preview._ ![Fraime.it webcam background controls for Normal, None, Blurred, Person, Green Screen, and keying strength.](/docs/screenshots/webcam-keying-controls.png) _Then choose how the background is treated: normal, blurred, person segmentation, or green screen._ Use Remove Background when you want the camera to feel like an overlay. Use Blur Background when the original room is acceptable but distracting. Keep Normal when the webcam already looks intentional. ## Use green-screen keying If you recorded in front of a chroma backdrop, switch the matte method to Green Screen. Pick the key color from the preview or use auto-detect, then tune the matte. Green-screen keying works best when the backdrop is evenly lit and visibly different from clothing, skin, and hair. If your background is not a real chroma screen, person segmentation is usually the better starting point. Advanced tuning is for cleanup. Start by sampling the key color, then adjust tolerance, edge softness, and spill reduction until hair, shoulders, and hands hold up in motion. ## Tune the matte Use the inspector controls to adjust: - Strength for the overall keying amount - Tolerance for how wide the color match should be - Edge softness for smoother outlines - Spill reduction for reducing green color bleed Start with key color and tolerance. Then adjust edge softness for outline quality and spill reduction for color bleed around hair, shoulders, and hands. ## Crop before placing If the webcam source includes empty space, crop it before final placement. A tighter camera frame often looks cleaner in picture-in-picture layouts and leaves more room for the screen recording. ## Preview before export Preview the camera track at a few points in the timeline. Look for hair, hands, transparent edges, and color spill. The same compositor is used for export, so the preview is the best guide to the rendered result. Check both still moments and motion. A matte can look good when you are still but break around hands, headset cables, or fast movement. ## Pair with Shorts The Shorts template can combine background removal with a vertical picture-in-picture webcam layout, which is often cleaner than leaving the full room visible in a narrow frame. ## Troubleshooting If the background is still visible, increase tolerance gradually. If parts of your face, shirt, or hands disappear, reduce tolerance or pick a more accurate key color. If the edge looks harsh, increase edge softness. If there is green tint around the subject, increase spill reduction. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md). --- --- title: "Zoom, 3D Punch, And Animation" description: "Guide attention with Smart Zoom, manual zooms, reframes, 3D punch moments, spotlights, and motion presets." canonical_url: "/docs/zoom-3d-punch-animation" markdown_url: "/docs/zoom-3d-punch-animation.md" --- # Zoom, 3D Punch, And Animation Guide attention with Smart Zoom, manual zooms, reframes, 3D punch moments, spotlights, and motion presets. Canonical URL: /docs/zoom-3d-punch-animation Markdown URL: /docs/zoom-3d-punch-animation.md Motion tools help viewers follow technical detail without making the whole video feel busy. Use them to emphasize what changed, where to look, or why a moment matters. ## Zoom Use zoom when the important UI is too small, the recording includes too much surrounding space, or the viewer needs to focus on one region. - Add a zoom at the playhead for a focused moment. - Adjust the zoom target in the preview or inspector. - Tune smoothness so the move feels intentional. - Keep the zoom active long enough for the viewer to read the content. Zoom is especially helpful for code, terminal output, browser developer tools, and dense dashboards. ## Smart Zoom Smart Zoom places and frames zooms for you based on what happened during the session, so you can skip manual keyframing on busy recordings. - It reads the activity captured during recording: cursor movement, clicks, IDE selections and file or function context, and Chrome browser telemetry such as clicks, selections, and route changes. - It weighs those signals to pick the focus region, choose a zoom scale, and frame the shot. Tighter scales come from focused IDE selections or web element interactions, while generic scrolling stays gently framed. - The camera is stabilized with a dead-zone so it stays calm instead of chasing every cursor sample. - For code, framing nudges toward the leading edge so selected lines stay readable instead of being centered behind a webcam or panel. Smart Zoom needs activity to work from. The richer the captured context, the better its suggestions: - The [editor extension](/docs/extension-setup) adds IDE cursor, selection, and function context. - The [Chrome browser extension](/docs/browser-extension-setup) adds privacy-aware browser interaction context. Suggested zooms land on the timeline as normal, editable zoom segments. Review each one, then retime, reframe, change the scale, or remove it like any manual zoom. Smart Zoom is a starting point, not a locked decision. ## Pan and Reframe Pan and reframe moves shift attention without necessarily making the content feel like a dramatic camera effect. - Use reframe when the important part of the screen moves. - Use manual framing when automatic framing does not match your story. - Preview the transition before export, especially after aspect-ratio changes. For vertical clips, reframing can be more important than scale. A 9:16 canvas often needs the subject centered more aggressively than a 16:9 tutorial. ## 3D Punch 3D punch tilts or pushes the screen recording for emphasis. It works best as a short visual accent around a key moment. - Add a 3D punch at the playhead. - Choose a subtle or dramatic preset as a starting point. - Tune tilt, depth, perspective, entry, and exit duration. - Use it sparingly so it stays meaningful. Good uses include revealing a result, highlighting a before/after change, or giving a launch clip a stronger visual beat. ## Spotlight Spotlight emphasis dims surrounding content and keeps a selected region visible. Use spotlight when the screen is too busy for a callout alone. It pairs well with narration like "look at this value" or "the important part is here." ## Animation Presets Presets are starting points, not final decisions. Apply one, preview it in context, then adjust timing and intensity. - Subtle presets fit tutorials and documentation videos. - Dramatic presets fit launch clips and social clips. - Smooth zoom presets are useful when the viewer needs to read during motion. - Gentle reframe presets work when the subject moves gradually. ## Timing Motion Motion should support the edit rhythm. - Start a zoom slightly before the moment the viewer needs detail. - Hold long enough for reading. - Exit after the point is made. - Avoid cutting away in the middle of a motion unless that is intentional. Review motion together with subtitles, cursor pulses, keyboard HUD, callouts, and webcam placement. Those elements all compete for attention. ## Troubleshooting If motion feels distracting, reduce intensity, shorten the transition, or remove competing overlays. If text is still hard to read, increase zoom or use an annotation instead of relying only on camera movement. If a vertical crop misses the subject, reframe the segment after choosing the final aspect ratio. ## Sitemap See the agent-readable sitemap at [/sitemap.md](/sitemap.md).