Troubleshooting
Solutions to common problems with screenpipe installation and usage.Installation Issues
macOS: “screenpipe is damaged and can’t be opened”
Solution:- Right-click the screenpipe app → Open
- Click Open in the security dialog
- Or disable Gatekeeper temporarily:
macOS: “screenpipe wants to access Screen Recording”
Solution: screenpipe needs screen recording permission to capture your screen:- Go to System Settings → Privacy & Security → Screen Recording
- Enable the checkbox for screenpipe
- Restart screenpipe
Dev builds are signed with a developer certificate for consistent permissions. If you rebuild from source, macOS may ask again.
Windows: “Windows protected your PC”
Solution:- Click More info
- Click Run anyway
- The installer will proceed normally
Linux: Build fails with missing dependencies
Solution: Install required dependencies:Permission Issues
macOS: Screen recording not working
Symptoms:- Blank screenshots
- “Permission denied” errors
- No screen data captured
- System Settings → Privacy & Security → Screen Recording
- Make sure screenpipe is checked
-
If already checked:
- Uncheck it
- Restart screenpipe
- Check it again
- Restart screenpipe
- Check logs:
macOS: Audio recording not working
Symptoms:- No audio transcriptions
- Empty audio search results
- System Settings → Privacy & Security → Microphone
- Enable screenpipe
- For system audio, install audio driver:
- screenpipe will prompt on first run
- Or manually: Settings → Audio → Install System Audio Driver
Windows: No audio captured from applications
Solution:- Right-click speaker icon → Sounds
- Recording tab → Right-click Stereo Mix → Enable
- Set as default device
- Restart screenpipe
- Update audio drivers
- Or use VB-Audio Virtual Cable (free)
Capture Issues
Screen captures are blank/black
Possible causes:-
Missing permissions (macOS/Linux):
- Grant screen recording permission
- Restart screenpipe
-
HDR display (Windows):
- Disable HDR temporarily: Settings → Display → Use HDR
- Or update to latest screenpipe version (improved HDR support)
-
Remote desktop session:
- Accessibility/OCR may not work in RDP
- Try running screenpipe on the local machine
-
Missing snapshot files:
- Check logs:
~/.screenpipe/logs/screenpipe.log - Recent fix in v2.2.80 handles missing snapshots gracefully
- Check logs:
Audio not recording
Checklist:- Audio recording enabled in settings
- Microphone permission granted
- System audio driver installed (for app audio)
- Audio device selected correctly
- Volume not muted
- Open screenpipe → Settings → Audio
- Check audio level meters while speaking
- If no movement:
- Try different audio device
- Check OS audio settings
- Restart audio service
Multi-monitor: Only one monitor captured
Solution:- Settings → Capture → Monitors
- Select All monitors or choose specific ones
- Restart capture
- Disconnect/reconnect monitor
- Restart screenpipe
- Check logs for detection errors
OCR text extraction is inaccurate
Causes:- Low screen resolution
- Unusual fonts
- Images/graphics instead of text
- Non-English text (needs language config)
-
Prefer accessibility tree (more accurate):
- Settings → Capture → Prefer Accessibility
- Only falls back to OCR when needed
- Configure OCR language:
- Increase capture quality:
- Settings → Capture → Quality → High
- Uses more storage but better OCR
Performance Issues
High CPU usage
Expected: 5-10% on modern hardware If higher:-
Check event rate:
- Settings → Capture → Event Sensitivity
- Reduce sensitivity if capturing too frequently
-
Disable unused features:
- Disable audio if not needed
- Reduce monitor count
- Lower capture quality
- Check for bugs:
- Recent fixes:
- v2.2.79+: Improved event-driven efficiency
- Update to latest version
High disk usage
Expected: 5-10 GB/month If higher:-
Check capture settings:
- Too many monitors
- High capture quality
- Very frequent captures
-
Clean old data:
- Settings → Storage → Clear Old Data
- Or manually delete frames:
- Adjust retention:
- Settings → Storage → Auto-delete after X days
Slow search results
Solutions:-
Rebuild search index:
- Settings → Advanced → Rebuild Index
- This recreates the FTS5 index
- Optimize database:
- Narrow search scope:
- Use date range filters
- Filter by app/window
- Limit result count
API Issues
API not responding (localhost:3030)
Check if server is running:- Check screenpipe is running
- Check logs for startup errors:
- Try different port:
MCP server connection fails
For Claude Desktop / Cursor:- screenpipe not running
- Port conflict (change from 3030)
- Firewall blocking localhost
Data Issues
Missing data for certain time periods
Causes:-
screenpipe wasn’t running:
- Check uptime: Settings → Status → Running Since
- Enable “Start at login” to avoid gaps
-
Capture paused:
- Settings → Capture → Resume
- Or use pause schedule for specific times
-
Excluded apps/windows:
- Settings → Filters → Review exclusions
- May have filtered out more than intended
-
Disk full:
- Check available space
- Clear old data if needed
Database corruption
Symptoms:- “Database disk image is malformed”
- Search errors
- App crashes
- Restore from backup (if available)
- Or start fresh (will lose history)
Integration Issues
Obsidian sync pipe not working
Checklist:- Pipe enabled: Settings → Pipes → Obsidian Sync
- Vault path configured correctly
- Obsidian vault is accessible
- Permissions to write files
Reminders pipe not creating todos
macOS only - requires system permissions:- System Settings → Privacy → Reminders
- Enable screenpipe
- Restart screenpipe
CLI Issues
npx screenpipe@latest record fails
Solutions:
- Update Node.js:
- Clear npm cache:
- Install directly:
CLI: “Command not found”
Add to PATH:Logs & Debugging
Where are the logs?
Enable debug logging
Common log patterns
Permission denied:Getting Help
Before asking for help
- Check logs:
-
Collect system info:
- OS version
- screenpipe version (Settings → About)
- Relevant error messages
-
Try latest version:
- Updates often fix known issues
- Download from screenpi.pe/onboarding
Where to get help
- Discord: discord.gg/screenpipe (fastest)
- GitHub Issues: Report bugs
- Documentation: docs.screenpi.pe
- Email: [email protected] (for sensitive issues)
Creating a good bug report
Include:-
System info:
- OS and version
- screenpipe version
- Hardware (CPU, RAM, monitors)
-
Problem description:
- What you expected
- What actually happened
- Steps to reproduce
- Logs:
- Screenshots (if UI issue)
Still stuck? Join Discord for real-time help from the community.