Data storage
Portable data
Packaged Windows and Linux builds keep ASR Pro data beside the executable in asrpro-data/. macOS does the same
when the app is outside a normal Applications folder.
Resolution rules
ASR Pro resolves its storage root from the current executable location, with platform-specific fallbacks where the OS expects them.
| platform | resolved data root |
|---|---|
| Windows packaged | sibling asrpro-data/ folder beside ASR Pro.exe |
| Windows portable | PORTABLE_EXECUTABLE_DIR plus sibling asrpro-data/ |
| Linux packaged | sibling asrpro-data/ folder beside the binary |
| macOS in Applications | ~/Library/Application Support/ASR Pro/data/ |
| macOS outside Applications | sibling asrpro-data/ folder beside ASR Pro.app |
| Development workspace | tmp/app-data/ in the project root |
What moves with the install
Moving the executable together with asrpro-data/ preserves the local runtime state that matters.
| path | contents |
|---|---|
asrpro-data/models/whisper/ |
downloaded Whisper model binaries |
asrpro-data/transcripts/ |
flat text exports of completed transcripts |
asrpro-data/config/ |
preferences, defaults, launch state, and editor targets |
asrpro-data/user-data/ |
Electron history and local application state |
asrpro-data/session/ |
Chromium session data and cache |
asrpro-data/logs/ |
runtime logs and diagnostic output |
Move checklist
- move the executable or app bundle together with its sibling
asrpro-data/folder - launch ASR Pro from the new location
- confirm models, transcripts, and history are still present
- if Launch at startup was enabled, toggle it off and on again from the new location
Packaged Windows and Linux builds are designed around this sibling-folder model. macOS uses the same pattern only when the app is being run outside the standard Applications location.