Meeting Transcript Converter
approvedby Ivan Batura
Convert .txt or .vtt meeting transcript files into cleaned .md notes. - This plugin has not been manually reviewed by Obsidian staff.
Meeting Transcript Converter
Convert .txt and .vtt transcript files into clean Markdown notes, entirely offline. Built for meeting transcripts (e.g. Zoom recordings) but works with any plain-text or WebVTT transcript.
This plugin is desktop-only and does not send data anywhere — all conversion happens locally in your vault.
Features
- Manual conversion — run "Convert transcript file (txt/vtt) to Markdown" from the Command Palette on the active
.txtor.vttfile. - Auto-conversion — optionally watch a folder and convert new transcript files as soon as they're created, with no manual step.
- VTT timestamp rendering — WebVTT cues are rendered as a bulleted list, each optionally prefixed with a formatted timestamp computed from the file's creation time.
- Frontmatter generation — output notes get YAML frontmatter with
meeting_name,date, and, when detectable,durationandparticipants. - Optional cleanup — delete the original transcript file automatically once it's been converted.
Usage
Manual conversion
- Open a
.txtor.vttfile in Obsidian. - Open the Command Palette and run Convert transcript file (txt/vtt) to Markdown.
- The converted note is created (or updated, if it already exists) in your configured output folder.
Auto-conversion
- Open Settings → Meeting Transcript Converter.
- Enable Auto-convert new transcripts.
- Set Watch folder to the vault folder you want monitored (leave empty to watch the whole vault).
- Any
.txtor.vttfile created in that folder is converted automatically. Enable Delete original file after convert if you don't want to keep the source file around.
How conversion works
TXT files are cleaned by trimming each line and removing empty lines — no other reformatting is applied.
VTT files are parsed as WebVTT: the header, cue sequence numbers, and empty lines are skipped, and each cue becomes a bullet point. If a time format is set, each bullet is prefixed with a timestamp computed as the file's creation time plus the cue's offset, e.g.:
- **[2026-04-05 14:32:01]** Hello, this is the first line
- **[2026-04-05 14:32:06]** Second cue block here
With the time format left empty, timestamps are omitted:
- Hello, this is the first line
- Second cue block here
Every converted note starts with a title (# {name}) and YAML frontmatter containing the meeting name and date, plus duration and participant list when they can be detected from the transcript content.
Known limitation: WebVTT
<v Speaker>voice tags are not stripped and will pass through as raw text in the output.
Settings
| Setting | Description | Default |
|---|---|---|
| Output folder | Vault folder where converted .md files are saved. Created automatically if it doesn't exist. | Transcripts |
| Watch folder | Vault folder monitored for new transcripts when auto-convert is on. Empty watches the entire vault. | Transcripts |
| Auto-convert new transcripts | Automatically convert new .txt/.vtt files as they're created. | Off |
| Delete original file after convert | Remove the source file after a successful conversion. | Off |
| Time format | Moment.js format string used for VTT cue timestamps. Leave empty to omit timestamps. | YYYY-MM-DD HH:mm:ss |
Installing
Manual install:
- Download
main.js,manifest.json, andstyles.cssfrom the latest release. - Copy them into
<vault>/.obsidian/plugins/meeting-transcript-converter/. - Reload Obsidian and enable Meeting Transcript Converter under Settings → Community plugins.
Development
npm install # install dependencies
npm run dev # esbuild watch mode
npm run build # type-check and produce a production bundle
npm run lint # run eslint
npm run test # run the test suite (vitest)
See the doc/ folder for detailed architecture, converter, and settings specifications.
License
This project is licensed under the GNU General Public License v3.0.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.