[Feature Request]: Separate custom storage paths for Projects, Videos, and Screenshots (Crucial for Local/Desktop Licenses)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
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:
- Default Project Location: Choose a custom path where raw recording segments and project files are stored.
- Video Export Destination: Define a default folder for finished MP4/GIF exports.
- 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
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CapSoftware/Cap
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Download, FAQ, privacy and terms pages have no meta descriptionPossibly taken @patrickballard claimed this 13 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CapSoftware/Cap#3675 · 1 comment ·
Maintainers usually reply within 1 day
-
self hosting
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#2384 · 3 comments ·
Maintainers usually reply within 1 day
-
Dashboard pagination causes full page reloads on self-hosted CapPossibly taken @DipanshuAmbilkar03 claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CapSoftware/Cap#2305 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#1714 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day