Skip to main content

​
Community Support

​
Discord

Join our active Discord community to:
  • Get help from other Cap users
  • Suggest new features
  • Share your recordings and use cases
  • Connect with the development team

Join Cap Discord

Get instant help and connect with the community

​
GitHub Discussions

For longer-form discussions, feature requests, and community Q&A:

GitHub Discussions

Share ideas and discuss the future of Cap

​
Report Issues

​
Bug Reports

Found a bug? Help us improve Cap by reporting it:

Report a Bug

Create a detailed bug report on GitHub
When reporting bugs, please include:
  • Operating system and version (e.g., macOS 14.0, Windows 11)
  • Cap version (Desktop app version or self-hosted commit)
  • Steps to reproduce the issue
  • Expected behavior vs actual behavior
  • Screenshots or screen recordings (use Cap to record the bug!)
  • Error messages from logs
  • Browser version (for web app issues)

​
Feature Requests

Have an idea for a new feature? We’d love to hear it! The best place to suggest features is on Discord where you can discuss with the community and maintainers:

Suggest Features

Share your ideas on Discord

​
Contributing

​
Ways to Contribute

Cap is open source and welcomes contributions:

Code Contributions

Submit pull requests to fix bugs or add features

Documentation

Improve docs, write tutorials, or create guides

Testing

Test new features and report issues

Translation

Help translate Cap to other languages

​
Bounty Program

Earn money by contributing to Cap! We offer bounties for specific issues and features:

Open Bounties

View paid issues and start contributing

​
Contributing Guide

Before contributing code, please read our contributing guide:

Contributing Guide

Learn how to set up your development environment
Quick start for contributors:
  1. Fork the repository
  2. Clone your fork locally
  3. Install dependencies: 
    pnpm install
pnpm cap-setup
pnpm env-setup
  4. Create a feature branch
  5. Make your changes
  6. Test thoroughly
  7. Submit a pull request

​
Documentation

​
Resources

Explore our documentation:

Getting Started

Quick start guide for new users

Self-Hosting

Deploy Cap on your own infrastructure

FAQ

Answers to common questions

Troubleshooting

Solutions to common issues

​
API Documentation

For developers building with Cap:
API documentation is currently in development. Check back soon or contribute to the docs!

​
Social Media

Stay updated with Cap news and updates:

GitHub

Star the repo and watch for updates

Twitter/X

Follow for announcements

Discord

Join the community

​
Self-Hosting Support

​
Community Help

For self-hosting questions:
  1. Check the self-hosting documentation
  2. Search GitHub issues
  3. Ask on Discord in the #self-hosting channel

​
Common Resources

Get Cap running with one command:
git clone https://github.com/CapSoftware/Cap.git && cd Cap && docker compose up -d
Visit Self-Hosting Quickstart for details.
Learn how to configure:
  • Email providers for login links
  • S3 storage (MinIO, AWS, etc.)
  • Environment variables
  • SSL/HTTPS
  • AI features
See Configuration Guide.
Deploy Cap on:
  • Docker Compose (recommended)
  • Railway (one-click)
  • Coolify
  • Your own VPS
Compare options in Docker Compose Guide.

​
Feedback

Your feedback helps make Cap better!

​
What to Share

  • Feature requests and ideas
  • User experience feedback
  • Performance issues
  • Documentation improvements
  • Use cases and workflows

​
Where to Share

1

Join Discord

The fastest way to share feedback is on Discord where you can discuss directly with the team and community.
2

Create GitHub Issue

For bug reports or detailed feature requests, create a GitHub issue with full context.
3

Contribute Code

The best feedback is a pull request! Fix bugs, add features, or improve docs.

​
Security

​
Reporting Security Issues

If you discover a security vulnerability:
Do NOT create a public GitHub issue for security vulnerabilities.
Instead:
  1. Email the maintainers privately (check GitHub for security contact)
  2. Provide detailed information about the vulnerability
  3. Wait for a response before public disclosure
Responsible disclosure helps keep all Cap users safe.

​
Code of Conduct

Cap is committed to providing a welcoming and inclusive community.

​
Our Standards

  • Be respectful and considerate
  • Welcome newcomers and help them learn
  • Focus on constructive feedback
  • Respect different viewpoints and experiences
  • Accept responsibility and apologize for mistakes

​
Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers. All complaints will be reviewed and investigated.

​
Thank You

Cap is built by the community, for the community. Thank you for:
  • Using Cap for your video messaging
  • Reporting bugs and suggesting features
  • Contributing code and documentation
  • Helping other users in Discord
  • Spreading the word about Cap
Together, we’re building the best open source alternative to Loom!

Build docs developers (and LLMs) love

Get started for freeTalk to us