Voice to Text for Sublime Text

Sublime Text is fast and minimal. Your workflow should be too. But writing code comments, documentation, and commit messages pulls you out of the zone. Blurt lets you speak your prose directly into Sublime Text. Hold a button, say what you need, release. Text appears at your cursor instantly. Your hands stay on the keyboard. Your focus stays on the code. Works anywhere in Sublime Text — any file, any language, any context where you can type.

First 1,000 words free Works in all Sublime Text contexts macOS only
Download Blurt Free

The Typing Problem

Code comments feel like friction in a fast editor

Sublime Text is built for speed. Every keystroke is instant. But when you need to write a comment explaining complex logic, you slow down. Your fingers are optimized for code syntax, not English prose. The comment you should write takes longer than the code you just wrote. So you skip it. The speed of Sublime works against documentation.

Documentation gets postponed indefinitely

You just implemented a tricky algorithm. You know exactly how it works right now. But typing out the explanation feels tedious after the mental effort of writing the code. You tell yourself you'll document it later. Later never comes. Two months from now, you'll stare at this code wondering what you were thinking.

Commit messages become meaningless shortcuts

Git needs a commit message. You've been deep in Sublime for hours. Switching from code brain to explanation brain is hard. You type 'fix' or 'update' and move on. The git history becomes useless. When something breaks, you have no idea which commit to investigate. Good commit messages require prose. Prose requires mental gear-switching.

Inline notes you think but never type

While reading code, you have insights. Why this approach was chosen. What edge cases it handles. What might break in the future. These thoughts exist briefly in your mind. Typing them interrupts your reading flow. So they vanish. The tribal knowledge stays in your head instead of the codebase.

README updates that require context switching

The function signature changed. The README example is now wrong. Fixing it means opening the file, finding the section, and typing prose while your brain is in code mode. It's a five-minute task that feels like thirty. So the README stays outdated. New team members get confused. The documentation debt compounds.

How It Works

Blurt works everywhere in Sublime Text. Any file type, any project, anywhere you can place a cursor and type.

1

Hold your hotkey

Press your chosen shortcut anywhere in Sublime Text. A small indicator shows Blurt is listening.

2

Speak naturally

Say your comment, documentation, or notes. Blurt handles punctuation and capitalization automatically.

3

Release and continue

Text appears at your cursor in Sublime Text. No dialogs. No confirmations. Keep coding.

Real Scenarios

Speaking TODO comments while coding

You notice something that needs fixing but don't want to lose focus. Hold button: 'TODO refactor this to use the new authentication helper once the API migration is complete. See ticket 4521 for details.' The reminder is captured. Your train of thought continues uninterrupted. The technical debt is documented, not forgotten.

Documenting functions and classes as you write them

You just finished a class definition. The docstring should be written while the implementation is fresh. Hold button: 'This class manages database connection pooling for the application. Initialize with a maximum pool size and connection timeout. Call get connection to acquire a connection from the pool. Always release connections back to the pool when done.' Documentation complete before you move on.

Explaining workarounds and hacks

You wrote code that looks wrong but is intentionally that way. Hold button above the suspicious line: 'This looks like a bug but the third-party API returns timestamps in seconds on weekdays and milliseconds on weekends. Yes really. See their GitHub issue 892. We normalize here before processing.' The context is preserved. Future you won't delete this 'fix.'

Writing commit messages with detail

You're about to commit changes. Instead of typing 'fix bug,' hold button: 'Fix race condition in session refresh logic where concurrent requests could invalidate tokens prematurely. Add mutex lock around token refresh. Add regression test for concurrent session scenario.' A meaningful commit message in seconds. Git history becomes useful.

Adding inline notes during code review

You're reviewing code in Sublime Text and want to leave notes. Hold button: 'Consider extracting this validation logic into a separate function. It's duplicated in three places and the rules might change. Also check if we need to handle null input here.' Review notes captured as fast as you think them.

Updating README and docs in context

You changed an API endpoint. The docs need updating. Hold button: 'The users endpoint now accepts an optional filter parameter. Pass filter equals active to return only active users. Default behavior returns all users including inactive. Rate limit increased to 100 requests per minute.' Documentation updated while the changes are fresh.

Why Sublime Text developers choose Blurt over built-in dictation

Blurt macOS Dictation
Activation Single hotkey, instant start Double-tap Fn or menu bar click
Speed Text appears in under 500ms 2-3 second delay before transcription starts
Technical vocabulary Handles programming terms accurately Often misinterprets function names and jargon
Workflow interruption Matches Sublime's minimal, fast philosophy Clunky UI breaks flow
Price $10/month or $99/year Free (built into macOS)
Free tier First 1,000 words free Unlimited but unreliable

Frequently Asked Questions

Does Blurt work with all file types in Sublime Text?
Yes. Blurt works anywhere you can place a cursor in Sublime Text. Python, JavaScript, Markdown, plain text, JSON, whatever you're editing. It inserts text at your cursor position regardless of file type or syntax highlighting.
Can Blurt handle programming terminology?
Blurt handles programming vocabulary well. Terms like 'refactor', 'async', 'middleware', 'API', and common programming patterns transcribe accurately. For highly specialized terms unique to your project, occasional edits may be needed. Most developers find the accuracy sufficient for comments and documentation.
Will Blurt interfere with Sublime Text keyboard shortcuts?
No. You choose your own hotkey during Blurt setup. Pick any key combination that doesn't conflict with your Sublime Text bindings. Most developers use a modifier combination they're not already using, like Ctrl+Shift+Space or a dedicated function key.
Should I use Blurt for writing actual code?
Blurt is designed for prose, not code syntax. Saying 'def function name parenthesis argument colon' is awkward and slower than typing. Use Blurt for comments, documentation, commit messages, and notes. Use your keyboard for the code itself.
Does Blurt work with Sublime Text packages and plugins?
Blurt works independently of Sublime Text packages. It simply inserts text at your cursor position using standard macOS text insertion. Any package that allows text input will work with Blurt. There's no Sublime Text plugin required.
Does Blurt work on Windows or Linux?
Blurt is macOS only. We focused on creating the best possible Mac experience with native menu bar integration and system-level keyboard shortcuts. Windows and Linux versions are not currently available.

Start Typing Faster Today

Free to try — no credit card required

Download Blurt