Screen Beaver

Open-source desktop screen recorder & motion editor for product videos.
Record any window or screen · polish with zooms, captions & effects · export a crisp MP4 — locally.

Screenshots · Features · Quick start · MCP · Docs · License

Download for Windows from the Microsoft Store · or build from source below

Home — create demos, see weekly activity, and jump back into recent projects.

Studio — backgrounds, camera PiP, timeline, and local export.

Left: camera & timeline · Right: AI voiceover (translate + Edge TTS).

Left: MCP / agent-driven demos · Right: keyboard shortcut overlays in the video.

Android USB takes — vertical 9:16, motion backgrounds, full timeline polish.

Most “screen recorders” stop at a raw take. Screen Beaver is a studio for product stories:

All studio features in this open-source build are free offline. Optional cloud sign-in is only for share links.

Full product surface: docs/FEATURES.md.

The easiest way to run Screen Beaver on Windows 10 / 11:

Get it from Microsoft Store →

Updates come through the Store. Use the build-from-source steps below if you are developing or contributing.

git clone https://github.com/ScreenBeaver/ScreenBeaver.git
cd ScreenBeaver
npm install
npm run desktop:dev

npm run dev

Web mode still records via the browser picker, but loses system-wide cursor tracking and Android USB.

Screen Beaver exposes a local bridge (127.0.0.1:17355) and an MCP server so agents can:

• open apps / URLs
• move, click, type, and scroll during a capture
• add captions, zooms, effects, and music
• run record_and_build / live demo flows while you watch

npm run mcp:install
npm run mcp:build
npm run mcp

See mcp/README.md and docs/PUBLISHING.md.

ScreenBeaver/
├── src/                 # React studio (TanStack Start)
├── src-tauri/           # Tauri / Rust desktop shell + native capture
├── mcp/                 # MCP server (agent tools)
├── extension/           # Chrome/Edge companion
├── packaging/msix/      # Microsoft Store packaging helpers
├── public/              # Runtime assets (sounds, wallpapers, official logo)
├── docs/                # Documentation + README media
│   ├── FEATURES.md
│   ├── DESKTOP.md
│   ├── DESKTOP_ACCOUNT.md
│   ├── PUBLISHING.md
│   └── assets/
│       ├── logo.png           # Official Screen Beaver logo
│       └── screenshots/       # Product screenshots for GitHub
├── recipes/             # Example polish recipes
└── LICENSE

Copy .env.example → .env only if you need overrides. Never commit a real .env.

Studio features work fully offline without an account.

Tauri does not emit MSIX. Build the release binary, stage the payload, then package with Visual Studio / MakeAppx:

npm run desktop:build:store

Details: packaging/msix/README.md · replace placeholder Partner Center identity before Store submission.

1. Fork & clone the repo
2. npm install · npm run desktop:dev
3. Keep PRs focused; don’t commit .env, node_modules, src-tauri/target, or MSIX payloads
4. Prefer clear commit messages (what changed and why)

MIT © Screen Beaver

_{Record · Polish · Export — locally.}