[Feature Request]: Separate custom storage paths for Projects, Videos, and Screenshots (Crucial for Local/Desktop Licenses)

[dennyschroeder]

Hi @richiemcilroy,

For users operating entirely on the standalone Desktop License without Cloud features, storage management is a massive priority.

Currently, there is no option in the settings panel to manually define where projects, exported videos, and screenshots are saved.

The Problem:
By default, many users have their system "Pictures" or "Movies" folders automatically synced to cloud providers (like iCloud, Dropbox, or OneDrive). Since video project files are massive compared to screenshots, I would consider not the same path.

I want my screenshots to go to my cloud-synced folder for quick sharing, but my heavy video & projects separated on different drives.

Proposed Solution:
Please add a "Storage" or "Paths" section in the Settings panel with the following options:

1. Default Project Location: Choose a custom path where raw recording segments and project files are stored.
2. Video Export Destination: Define a default folder for finished MP4/GIF exports.
3. Screenshot Destination: Set a custom path specifically for saving local screenshots.

Giving local power-users full control over their directory geometry would be a massive quality-of-life improvement for storage management.
Thanks, Denny

[linear]

CAP-718

[tembo]

There's an existing open issue for this at #424 that covers the general feature request for custom save folder locations. @Brendonovich noted there that PR #421 (cap-file-open) already added support for opening projects at any path, so the foundation exists - what's needed now is the configuration UI.

For implementation context, the current storage paths are hardcoded in the Rust backend:

• Recordings: app.path().app_data_dir().unwrap().join("recordings") (lib.rs:5557-5561 and tray.rs:135-139)
• Screenshots: app.path().app_data_dir().unwrap().join("screenshots") (lib.rs:5567-5571 and tray.rs:141-145)

The settings infrastructure is already in place via GeneralSettingsStore in general_settings.rs, which uses tauri-plugin-store for persistence. Adding new fields like custom_recordings_path, custom_screenshots_path, and custom_export_path would follow the existing pattern.

The settings UI at apps/desktop/src/routes/(window-chrome)/settings/general.tsx already has section components that could host the new path configuration options - likely as a new "Storage" section with directory picker dialogs via Tauri's tauri-plugin-dialog.

The point about cloud-synced folders (iCloud, Dropbox, OneDrive) causing issues with large video files is valid - keeping heavy project files separate from quick-share screenshots makes sense for this use case.