Cap: Record, Edit, and Share Screen Videos

Overview

Cap is a screen-recording and sharing platform positioned as an alternative to Loom. It helps teams communicate through recorded demonstrations and updates, with options to edit locally, share a link, or keep recordings under their own storage and hosting.

Cap is aimed at people who want more control over how recordings are stored and shared. It offers a hosted service as well as self-hosting, and supports both quick recordings and a more deliberate editing workflow.

Key Features

• Instant Mode uploads while recording and provides a share link when recording ends.
• Studio Mode records locally and supports editing, captions, backgrounds, zooms, trimming, and export controls.
• Recording can include screen, camera, and microphone.
• Share pages support comments, reactions, transcripts, viewer analytics, and team workspaces.
• Storage options include Cap Cloud, local files, S3-compatible storage, and self-hosting.
• Sharing controls include private or public access, passwords, and custom domains.
• Cap AI can generate titles, summaries, chapters, captions, and transcripts.
• Desktop apps are available for macOS and Windows, alongside a web dashboard.

Use Cases

• Product and design teams can send walkthroughs or design reviews when a live presentation is unnecessary.
• Support and engineering teams can record reproducible bug reports with visual context.
• Managers and distributed teams can share async standups or project updates across time zones.
• Educators and product teams can make tutorials, onboarding videos, and demonstrations for viewers to watch on demand.
• Organizations with storage or privacy requirements can use their own S3-compatible storage or self-host the platform.

Getting Started

Download the desktop app from cap.so/download, or self-host the web app with Docker Compose:

git clone https://github.com/CapSoftware/Cap.git
cd Cap
docker compose up -d

For setup details, configuration, and development instructions, see the README and documentation.

Considerations

• Self-hosting requires configuring services such as a database and object storage, and production deployments need appropriate public URLs and secrets.
• Local development uses a multi-part toolchain, including Bun, Node.js, Rust, and Docker.
• The repository metadata reports NOASSERTION for the license. The README describes different licensing for some crates and other repository content, so review the applicable license files before reuse or redistribution.