Static browser speech-to-text workspace for live/file transcription, translation, BYOK assistant workflows, and transcript export.
Verbatim is an open-source browser transcription workspace for voice-to-text capture, audio/video file transcription, translation, bring-your-own-key (BYOK) assistant workflows, diagnostics, and subtitle-ready exports using a static HTML/CSS/JavaScript app.
The maintained package lives in production ready/. That folder is the app root: it contains the source files, tests, screenshots, Netlify config, docs, and optional Expo mobile shell.
The banner above is conceptual artwork with deterministic text overlay. The screenshots below are captured from the real local app with demo/default data.
Live package preview: GitHub Pages demo. Provider-backed calls still require user-owned API keys.
| Recording workspace | Transcript workflow | Assistant workflow |
|---|---|---|
![]() |
![]() |
![]() |
git clone https://github.com/RossDmello2/verbatim-browser-transcriber.git
cd verbatim-browser-transcriber
cd "production ready"
npm ci
python -m http.server 8080Open http://localhost:8080 in Chrome or Edge.
Run from production ready/:
npm test
npm run test:web:smoke
npm --prefix apps/mobile run check
npm audit --audit-level=moderate
npm --prefix apps/mobile audit --audit-level=moderateCurrent status: READY WITH GAPS. Root install, static checks, unit tests, Playwright browser smoke, mobile typecheck, and root audit pass. The Expo shell dependency audit currently reports 13 moderate transitive advisories through Expo dependencies; live provider success calls and physical Expo Go/device verification require owner-controlled keys/devices and are not claimed.
- Package README
- Documentation index
- Architecture overview
- Provider/API integration notes
- Deployment guide
- Naming and SEO strategy
- Troubleshooting
- Security policy
- Contributing
Verbatim deploys as static files. For Netlify, set the base directory to production ready so production ready/netlify.toml is used, with publish directory .. Do not configure provider API keys in hosting environment variables; users enter their own keys in the app UI.
This repository also contains older root-level project files from the original Verba Transcriber history. The maintained open-source package for this publication is under production ready/. Root community files and workflows are included so GitHub can display the project correctly while preserving the existing repository history.
Recommended future repo slug: verbatim-browser-transcriber. The actual repository has not been renamed because renames affect clone URLs, GitHub Pages URLs, and downstream links.
MIT. See LICENSE.



