where are Vibe transcription files
Where Are Vibe Transcription Files Stored?
If you are asking where are Vibe transcription files, start by identifying the file type. Vibe can keep the transcript in the editor, export it beside a recording, or write it to a project folder selected in your settings. This guide shows how to find the real destination and recover a transcript that seems to have disappeared.
The short answer: identify the file before searching
There is no single universal Vibe transcript folder that is safe to assume across every version and setup. A saved TXT, SRT, DOCX, or JSON export is different from a Whisper model, an application data file, or an unsaved transcript still open in the editor. Check the export result and the active project before searching your whole drive.
A transcript visible in Vibe is not necessarily an exported file yet.
Auto-export can place output next to the recording, in the projects folder, or in a folder chosen in Settings.
Model files and application data help Vibe run, but they are not the transcript you can open and edit.
Find the file in five checks
- Look at the transcript status and confirm that the run finished rather than remaining an unsaved editor result.
- Check the export format and the filename suggested by Vibe; the extension tells you which files to search for.
- Open the project or recording folder, then inspect the destination shown by the export dialog or the Auto-export setting.
- Search recent files for the source recording name with a TXT, SRT, VTT, DOCX, JSON, CSV, Markdown, HTML, or PDF extension.
- Open the candidate file and verify its timestamp and first lines before deleting duplicate drafts.
1. Separate an export from an in-app transcript
The first question is whether Vibe has written a file at all. Finishing speech recognition produces text in the editor, but that result can remain an in-app working state until you choose an export action. If you close the window, change projects, or replace the source before exporting, a file search may correctly return nothing.
Look for the export control, the selected format, and a success message. A TXT or DOCX file is meant for reading and editing; SRT and VTT carry timing for captions; JSON and CSV are useful for structured processing; Markdown, HTML, and PDF are publishing or sharing formats. Searching for the wrong extension is a common reason a real export is missed.
- Editor text only: visible in Vibe, with no durable file confirmed.
- Manual export: written to the location approved in the native save dialog.
- Auto-export: written after a completed run according to the selected folder and format rules.
2. Check the project and recording folders
Recent Vibe releases can use an auto-export workflow that writes each finished transcript next to the recording, in the projects folder, or in one folder you choose. That means the source media is the best starting point. Open the folder that contains the audio or video and sort by modified time, then look for a matching base filename with a text or subtitle extension.
If the recording folder is read-only, disconnected, or unavailable, the application may use the project folder as a fallback. This is why a transcript can appear somewhere other than the media folder without being lost. A project folder also makes batch jobs easier to audit because exported files and their source names stay together.
- Use the exact source filename as the search phrase, without changing its spelling.
- Compare the export timestamp with the time the transcription finished.
- Check cloud-synced folders such as OneDrive or iCloud when the project is stored there.
3. Do not confuse models or app data with transcript files
Vibe downloads Whisper models and may use additional files for speaker diarization. Those files can be large binary or ONNX model assets, and they are used to run transcription rather than store the readable result. Finding a recently modified .bin or .onnx file does not mean you found the transcript.
The application also keeps settings and working data in an operating-system data directory. The exact location can change with the platform, portable mode, a custom model folder, and the installed version. Treat these directories as implementation details: use the app's settings and the official source when you need to inspect them, and do not delete them while trying to recover an export.
- Readable result: TXT, SRT, VTT, DOCX, JSON, CSV, Markdown, HTML, or PDF.
- Model asset: a downloaded file required for local speech recognition.
- App data: settings, cache, logs, or project metadata that may not be human-readable.
4. Where are Vibe transcription files on each OS?
On Windows, start with the recording folder, the Vibe projects folder, and the Recent view in File Explorer. Search the source filename plus the expected extension, then open the result to make sure it contains the latest text. If the file was saved to a synced or external drive, check that drive before searching the system disk.
On macOS, use Finder Recents or Spotlight after checking the source folder and the project location. Pay attention to iCloud Drive and external volumes because a save dialog can target either. On Linux, check the project directory, the recording directory, and your file manager's recent documents list; then repeat the search with the extension rather than the word transcript alone.
These checks are more reliable than copying a guessed path from another Vibe installation. Vibe's storage behavior can change between versions, and a user-selected destination always takes precedence over a platform default.
- Windows: File Explorer search, Recent, the source folder, and the projects folder.
- macOS: Finder Recents, Spotlight, iCloud Drive, and the source folder.
- Linux: recent documents, the project directory, mounted drives, and extension-based search.
5. Recover a transcript that is not where you expected
If no candidate file appears, return to Vibe while the transcript is still visible. Confirm that the run completed, export a short copy to a new folder you control, and note the exact path shown by the save dialog. This separates a search problem from an export problem. If the new test file opens correctly, the original likely went to a different destination or was never exported.
For batch work, inspect the run summary and the per-file status. A skipped or failed item should not be treated as an empty transcript. Check permissions, free disk space, disconnected drives, and filename conflicts before rerunning. Keep the original media and the newly exported result together so a later correction does not overwrite the wrong draft.
- Export one short test clip to a clearly named recovery folder.
- Use an explicit extension and avoid replacing an existing file until the new copy is verified.
- Record the source path, Vibe version, model, export format, and destination for repeatable troubleshooting.
6. Use Auto-export without losing track of files
Auto-export is useful when you transcribe several recordings, but it makes the chosen folder part of the workflow. Before starting a batch, review the setting and formats, create a project folder, and run one short file. Confirm where that file appears before processing the full queue. The first successful test prevents a long batch from scattering outputs across several directories.
When a batch finishes, use the summary and any Open folder action as the source of truth. Existing files may be kept unless you explicitly replace them, so a folder can contain multiple drafts with similar names. Add a simple naming convention such as date, source name, language, and revision number when the transcript will be edited by more than one person.
- Test Auto-export with one file before a large batch.
- Keep one project folder per recording set and one documented output format.
- Review skipped, failed, and replaced files separately from successful exports.
7. Build a dependable Vibe transcript folder convention
A predictable folder structure makes the answer to where are Vibe transcription files obvious. Keep the source recording, the untouched transcript, the edited transcript, and timed subtitles in one project directory. Use separate names for machine output and human-edited copy so a correction never destroys the original evidence.
Back up the project folder after you verify an export, especially when the source is a removable drive or a synced workspace. Local processing protects the audio during transcription, but it does not automatically protect the resulting files from deletion, disk failure, or an accidental overwrite.
- 01-source for original audio or video.
- 02-vibe-export for the untouched TXT, SRT, VTT, JSON, or DOCX output.
- 03-edited for reviewed text, subtitles, and published copies.
Sources and version context
FAQ
Vibe transcription file questions
Where are Vibe transcription files stored by default?
There is no single path that applies to every version and setup. Check the export dialog, the Auto-export setting, the source recording folder, and the active projects folder.
Why can I see a transcript in Vibe but not find a file?
The text may still be an in-app result. Choose an export format, approve a destination, and confirm the success message before closing or changing the project.
Are Whisper model files the same as transcript files?
No. Model files such as GGML or ONNX assets power local transcription. Readable exports use formats such as TXT, SRT, VTT, DOCX, JSON, CSV, Markdown, HTML, or PDF.
Can Auto-export save transcripts next to recordings?
Recent release notes describe Auto-export destinations such as the recording folder, projects folder, or one folder chosen in Settings. Test one file first and verify the actual result.
What should I do when a Vibe transcript is missing?
Return to the open result, export a short copy to a known recovery folder, then inspect permissions, free space, drives, and batch status for the original run.
Does this page replace the Vibe save-transcript guide?
No. The save-transcript guide explains the export control and formats. This page focuses on locating files, distinguishing models from exports, and troubleshooting missing results.
offline transcription with vibe
download vibe and start with a short local transcription test.
Download Vibe