Voice to Text for Hazel

Hazel rules need clear, descriptive names — otherwise you're debugging automation logic months later with no idea what 'Rule 3 copy' was supposed to do. But typing out 'Move invoices older than 30 days to Archive sorted by client name' takes forever. Blurt lets you name rules naturally. Hold a button, speak the description, release. Your rule name appears exactly as you said it. Same for folder comments, rename patterns, and shell script descriptions. $10/month or $99/year. First 1,000 words free. macOS only.

First 1,000 words free Works with any text field No setup required

Download Blurt Free

The Typing Problem

Cryptic rule names make debugging impossible

You built a dozen Hazel rules last year. Now something's not working. You open Hazel and see 'PDF Sort', 'New Rule', 'Downloads cleanup (2)', and 'test'. Which one handles invoices? Which one moves receipts? You end up clicking through each rule to remember what you built. Good naming would have prevented this, but typing descriptive names felt like too much friction at the time.

Rename patterns require mental translation

Hazel's rename patterns are powerful but cryptic. You want 'Invoice - ClientName - Date.pdf' but you have to think in terms of date patterns and attribute tokens. Typing the pattern description while mentally juggling the syntax splits your focus. By the time you've typed the comment, you've lost track of the pattern logic.

Folder descriptions get skipped entirely

Hazel lets you add comments to watched folders — invaluable context for future you. But when you're in the flow of building automations, stopping to type a paragraph explaining why this folder exists feels like busywork. So you skip it. Six months later, you have no idea why Downloads has 14 rules attached.

Shell script comments are an afterthought

Your Hazel rule runs a shell script. The script works, but you copied it from Stack Overflow and barely understand it. Adding a comment explaining what it does would help future you. But you're already deep in the rule configuration. Switching mental modes to write documentation feels exhausting. You tell yourself you'll add comments later. You won't.

Complex conditions need explanation

You've built a rule with five nested conditions: file type AND date AND size AND name contains AND NOT in subfolder. It works perfectly. But the logic is invisible once you leave the rule editor. Typing a clear description of what this rule actually catches feels tedious when you're in automation-building mode.

How It Works

Blurt works anywhere you can place a cursor on macOS — including Hazel's rule name fields, folder comments, and embedded script editors. Just hold, speak, release.

Hold your hotkey

Press your chosen shortcut. A small indicator shows Blurt is listening.

Speak your description naturally

Describe what the rule does, what the folder contains, or what the pattern means. Just explain it like you would to a colleague.

Release and done

Your spoken description appears at the cursor. Rule named, comment added, documentation done.

Real Scenarios

Naming rules as you build them

You're creating a rule to move old screenshots to a dated archive folder. Instead of typing 'Screenshot Archive Rule', hold your hotkey and say 'Move screenshots older than 7 days to Archive Screenshots folder organized by month taken.' Release. Your rule now has a name that actually explains what it does. Future you will understand this instantly.

Adding folder comments for context

You're setting up a new watched folder for client deliverables. Click the folder in Hazel, open the comments field, hold your hotkey: 'Client deliverables folder. Hazel moves completed projects to the archive after 30 days. PDFs get renamed with client code prefix. Large files over 100MB trigger a cleanup notification.' Your folder now has documentation that explains the entire workflow.

Documenting rename patterns

Your rename pattern uses date attributes and custom text. In the pattern notes field, hold and speak: 'Renames invoices to format Invoice dash client name dash year month day dot pdf for consistent sorting and searching.' Now when you revisit this pattern, you'll remember exactly what format you were going for.

Explaining shell script actions

Your rule runs a bash script that optimizes images. In the script comments: 'Uses ImageOptim CLI to compress PNG files while preserving quality. Reduces file size by 40 to 60 percent without visible quality loss. Requires ImageOptim to be installed.' Now anyone reading this rule (including future you) understands what the script does and what it needs.

Describing complex condition logic

You've built a rule with multiple conditions for sorting client files. In the rule description: 'Catches PDF files from the last 30 days that contain invoice in the name but excludes anything in the Processed subfolder. Moves matching files to the Pending Review folder for manual check before archiving.' The logic is now readable without parsing each condition.

Creating rule sets with clear purpose

You're organizing rules into groups. For each group name, hold and speak naturally: 'Financial documents processing' or 'Screenshot management and archiving' or 'Download folder cleanup automations.' Your Hazel sidebar becomes a clear table of contents instead of cryptic abbreviations.

Adding maintenance notes

A rule depends on an external service or folder structure. Add a comment: 'This rule requires the Dropbox sync folder to be in the default location. If Dropbox moves, update the destination path. Last verified working January 2026.' Future maintenance just got much easier.

Why Hazel users choose Blurt over macOS Dictation

	Blurt	macOS Dictation
Activation	Hold hotkey, speak, release	Double-tap Fn, speak, tap again
Speed	Instant transcription on release	Processing delay after stopping
Accuracy	Optimized for technical terms	General purpose, misses jargon
Works in Hazel dialogs	Yes, any text field	Inconsistent in some dialogs
Privacy	Audio processed securely, not stored	Processed through Apple servers

Frequently Asked Questions

Does Blurt work in Hazel's rule name field?

Yes. Blurt works anywhere you can place a cursor on macOS — including Hazel's rule name field, folder comments, script editors, and pattern description fields. If you can click and type there, Blurt can insert text there.

Can I use Blurt for shell script comments inside Hazel?

Absolutely. When editing a shell script action in Hazel, click into the script editor, hold your Blurt hotkey, and speak your comment. Blurt inserts the text at your cursor. Just remember to add the # for comment syntax yourself, or speak 'hash' to include it.

How does Blurt handle technical terms like file extensions?

Blurt's transcription is optimized for accuracy with technical terms. It handles file extensions, folder paths, and programming terms better than general-purpose dictation. You can say 'dot PDF' or 'slash documents slash archive' naturally.

Does this work with Hazel 5's new interface?

Yes. Blurt works at the macOS system level, not within specific apps. Any text field in Hazel 5's interface — whether it's a rule name, folder comment, or script editor — works with Blurt. The app version doesn't matter.

Can I dictate into the conditions or actions panels?

For dropdown menus and pickers, no — those aren't text fields. But for any text input field (rule names, path fields, script content, comments), yes. Blurt works wherever you can type freeform text.

What if I make a mistake while speaking?

The text appears after you release the hotkey. You can edit it normally with your keyboard before saving. Or just undo (Cmd+Z), hold the hotkey, and try again. Blurt doesn't lock you into anything.

Start Typing Faster Today

Free to try — no credit card required

Download Blurt