What's the difference with rewind.ai?
screenpipe is for developers to build apps like rewind.ai.
Where is the data stored?
- 100% of the data stay local in a SQLite database and mp4/mp3 files. You own your data
Do you encrypt the data?
- Not yet but we're working on it. We want to provide you the highest level of security.
How can I customize capture settings to reduce storage and energy usage?
- You can adjust frame rates and resolution in the configuration. Lower values will reduce storage and energy consumption. We're working on making this more user-friendly in future updates.
What are some practical use cases for screenpipe?
- RAG & question answering
- Automation (write code somewhere else while watching you coding, write docs, fill your CRM, sync company's knowledge, etc.)
- Analytics (track human performance, education, become aware of how you can improve, etc.)
- etc.
- We're constantly exploring new use cases and welcome community input!
How do I manage screenpipe sessions?
-
starting a session:
- macOS: use the system tray icon or run
screenpipe
in terminal - windows: launch from start menu or run
screenpipe
in command prompt - linux: run
screenpipe
in terminal
- macOS: use the system tray icon or run
-
checking if session is running:
curl localhost:3030/health # If running, you'll get a health status response # If not running, you'll get a connection refused error
-
stopping a session:
- macOS: cmd+option+x or right-click tray icon and select "quit"
- windows: right-click tray icon and select "exit"
- linux: ctrl+c in terminal
-
troubleshooting:
- if ctrl+c doesn't work to stop a terminal session, try:
# Find screenpipe process ID ps aux | grep screenpipe # Kill the process kill -9 [PID]
- if the server starts but API calls fail, check if another instance is already running
- if ctrl+c doesn't work to stop a terminal session, try:
Can I run screenpipe on remote/virtual machines?
- yes! screenpipe works seamlessly with remote desktop solutions
- microsoft remote desktop: works out of the box, capturing both screen and audio
- other remote solutions: generally compatible as long as they support audio/video forwarding
- check our server setup guide for detailed instructions
How resource-intensive is screenpipe?
- designed to be lightweight and efficient
- typical cpu usage: 1-2% on modern machines
- memory footprint: ~100-200mb baseline
- storage usage varies based on your capture settings and activity
- optimized for 24/7 operation
Can I build custom plugins/pipes?
- yes! screenpipe is designed to be extensible
- write plugins in typescript + bun
- full access to captured screen/audio data
- integrate with any ai model or external service
- check our plugin development guide for details
Is screenpipe open source?
- yes! core functionality is open source under MIT license
- built with rust + tauri for the core
- plugins system in typescript + bun
- community contributions welcome
- find us on github (opens in a new tab)
How do I troubleshoot common installation issues?
- missing dependencies:
- linux: install
ffmpeg
and required libraries - macOS: ensure XCode tools are installed
- windows: ensure VS C++ redistributable is installed
- linux: install
see our complete troubleshooting guide for more details.
Does screenpipe work with frameworks other than Next.js?
- yes! while our examples mainly use next.js, you can use any framework:
- react: yes
- vue/svelte/etc: yes
- electron/tauri: yes
- python: yes
- ruby/php/etc: yes
- example pipe templates for other frameworks coming soon!