Search existing issues
Is your feature request related to a problem?
After a recording or export completes successfully, users should be able to quickly open the folder containing the exported file directly from the export dialog.
Currently, the dialog displays the saved file path, but users must manually navigate to the output directory to locate the exported file. Adding an Open File Location action will improve usability and align with the behavior of many desktop recording and editing applications.
Proposed Solution
Add an Open File Location button or link to the export success section.
When clicked:
- Windows: Open File Explorer and select the exported file.
- macOS: Reveal the file in Finder.
- Linux: Open the parent directory (or reveal the file if supported by the file manager).
Acceptance Criteria
- Display an Open File Location action after a successful export.
- Open the parent folder containing the exported file.
- Reveal/select the exported file where supported by the operating system.
- Gracefully handle cases where the file no longer exists (e.g., disable the action or show an appropriate error message).
- Support Windows, macOS, and Linux.
Requirement Screenshot
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
Search existing issues
Is your feature request related to a problem?
After a recording or export completes successfully, users should be able to quickly open the folder containing the exported file directly from the export dialog.
Currently, the dialog displays the saved file path, but users must manually navigate to the output directory to locate the exported file. Adding an Open File Location action will improve usability and align with the behavior of many desktop recording and editing applications.
Proposed Solution
Add an Open File Location button or link to the export success section.
When clicked:
Acceptance Criteria
Requirement Screenshot
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response