Plan Screenpipe storage and retention

Plan Screenpipe disk storage and data retention by measuring real workdays, then manage local recordings, cloud copies, and generated reports.

Storage use depends on what you capture and retain. Measure your own representative workdays before choosing a retention window. Local recordings, cloud copies, generated reports, and AI usage are separate things to manage.

Start here

Record your data directory size and free disk space before and after a normal day. Note recording hours, enabled inputs, and any retention or archive settings. Use the installed app’s storage controls rather than manually deleting database files.

Use an external SSD or another data directory

Open Settings → Storage → Data Directory → Change and select a writable folder on the connected drive. Apply the restart requested by the app, then record a harmless test and verify it in the timeline.

Changing the directory starts fresh recordings at that location. It does not automatically move or merge existing history. Keep the old directory until you have a verified backup and a migration plan. The Database storage conversion controls are separate from moving recordings to another drive.

Keep the drive mounted while recording. If the configured directory becomes unavailable, Screenpipe can fall back to the default directory and show a warning. After reconnecting the drive, check the active path and recent recordings before assuming everything went to the SSD. Avoid a live database on a network share or a drive that disconnects during capture.

Copy this prompt

Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.

Create a storage planning worksheet from these measurements:
[date, recording hours, starting bytes, ending bytes, free bytes].
Calculate observed net growth per day and a clearly labeled projection for
[retention window]. Flag days affected by deletion, uploads, or unusual work.
List local history, archived copies, exported reports, and backups separately.
Do not delete anything or present the estimate as a guaranteed requirement.

Check the result

Check whether older text, screenshots, and audio are still available after your chosen policy takes effect. Confirm that a retained report does not point to evidence you have already removed.

See a worked example

For a fictional measured net increase of 2 GB per day, 14 days projects to 28 GB before extra headroom. This is arithmetic for planning, not a Screenpipe benchmark. Compression, audio, displays, cleanup, and workload can change the result.

Go deeper: setup choices and edge cases

A retention window answers how long to keep data; an archive setting answers where another copy may live. Neither implies that an exported CSV, an agent memory file, or a backup is removed too.

Before moving or backing up the local database, fully quit Screenpipe and use the storage guidance. Keep the copy protected and verify a restore before relying on it. A successful copy operation alone is not a restore test. Avoid opening a live database on an unreliable network drive.

Continue

Privacy data flow · AI usage and controls · reliable reports