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

Open
#1,857 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust, tauri
Domain
desktop

Research direction

Start at the desktop Settings panel and trace the existing save paths for projects, video exports, and screenshots. Define how each location is selected and persisted, then verify that projects, MP4/GIF exports, and screenshots use their respective configured destinations.

Written by the indexing model from the issue text.

Description

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

Dominant language
Rust
Stars
25k
Forks
2.4k
Avg merge
1d 8h
Merged PRs (30d)
676

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CapSoftware/Cap

All issues in CapSoftware/Cap

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.