Rubil vs Voice In: the Chrome voice dictation upgrade you didn't know existed

Voice In is the most popular voice typing extension on the Chrome Web Store. Over 600,000 users, 2,000+ reviews, a 4.4 star rating, and a history that goes back years. If you've searched for voice dictation in Chrome, you've probably tried it.

It works. You talk, words appear. For raw transcription, it does what it says.

But raw transcription is where it stops. Voice In gives you exactly what you said, including the filler words, the run-on structure, the missing punctuation you forgot to dictate as a voice command. The text that appears in your Gmail compose box is the same text that appears in your Slack message, your Notion page, and your Google Doc. No adaptation. No formatting. Just a transcript.

If you've ever finished a Voice In dictation and spent the next five minutes cleaning it up before hitting send, this post is for you.

What Voice In does well

Credit where it's due. Voice In works on over 10,000 websites. It supports 50+ languages. The free tier gives you 60 minutes of dictation per day, which is genuinely usable. The Plus plan at $60/year unlocks custom voice commands and an Advanced Mode that handles more complex text fields. For the price and the breadth, it's hard to argue with.

The accessibility story is real too. Voice In's reviews are full of people with arthritis, broken arms, and RSI who depend on it. That matters.

If all you need is raw transcription in Chrome and you're willing to edit the output yourself, Voice In is a solid tool at a fair price.

Where Voice In falls short

Voice In uses your browser's built-in speech recognition engine (the Web Speech API). That means the accuracy, punctuation, and formatting are whatever Chrome gives you. No AI layer. No language model. No cleanup.

The result is text that reads like a transcript, not like writing. You need to say "comma" and "period" out loud. You need to manually add paragraph breaks. You need to restructure your dictation into something that looks like an email, a Slack message, or a document after the fact.

That editing step defeats the purpose of dictating. You saved 30 seconds by talking instead of typing, then spent 3 minutes fixing the output. Net loss.

The other gap is platform awareness. Voice In doesn't know whether you're writing in Gmail, Slack, Notion, or a Jira ticket. The output is identical regardless of context. A professional email and a quick Slack reply get the same raw dump of words.

What Rubil does differently

Rubil is also a Chrome extension. Same install model: one click from the Chrome Web Store, and it works in your browser. But the output is different.

When you dictate in Gmail, Rubil formats your speech as an email. Proper greeting, structured paragraphs, professional sign-off if the content calls for it. When you dictate in Slack, the same words come out as a concise message. In Notion, document prose. In Google Docs, clean paragraphs. In Jira, a structured ticket update.

This happens because Rubil reads the URL of the page you're on and applies platform-specific formatting rules. It's not generic system-wide transcription. It's formatting designed for the app you're actually writing in, across 20+ platforms today.

The transcription itself runs on Groq's Whisper model, not the browser's built-in speech engine. Filler words are removed automatically. Punctuation and capitalization are handled by the language model, not by you saying "period" out loud. Self-corrections mid-sentence are cleaned up. What comes out reads like text you would have typed, not a transcript of your speech.

Your vocabulary, handled

Voice In Plus has custom voice commands: you say a trigger phrase, it inserts mapped text. Useful for templates and text expansion, but it's not vocabulary correction.

Rubil's Glossary is different. You teach it the names, acronyms, and terms specific to your work. When Whisper mishears your colleague's name or mangles an industry acronym, the Glossary catches it and applies the correct spelling every time. It also knows which platforms expand acronyms and which keep them short. One Glossary, synced across Chrome and the Mac app.

Beyond Chrome

Voice In is Chrome only. If you use any native Mac app like Slack desktop, Apple Mail, Apple Notes, VS Code, or Notion desktop, Voice In can't help.

Rubil has a Mac desktop app that works system-wide. Press a global hotkey, speak, and the formatted text is injected directly into whatever app is in focus. Same Glossary, same formatting rules, same backend. The Chrome extension covers your browser. The Mac app covers everything else.

Privacy

Voice In processes audio through Chrome's Web Speech API, which sends audio to Google's servers for recognition. Their privacy page states that no audio or transcript is sent to Voice In's own servers.

Rubil processes audio through Groq's Whisper model. Audio is discarded immediately after transcription. Transcripts are sent to OpenAI for formatting and discarded after processing. Rubil does not store transcripts on its servers. Your Glossary is encrypted and synced to your account. Every data processor is named publicly on the privacy page.

Both tools are privacy-conscious. The difference is transparency: Rubil names every processor and describes the data flow explicitly. Voice In routes through Google's speech engine, which is governed by Google's own privacy terms.

Pricing

Voice In is cheaper on paper. But the comparison isn't price to price, it's price to output. Voice In gives you a transcript you'll edit. Rubil gives you formatted text you can send. The editing time you save is the real cost difference.

When Voice In is the better choice

If you need raw transcription and prefer to format the text yourself. If you use voice commands for template insertion and text expansion. If you work primarily on simple text fields and web forms where formatting doesn't matter. If $60/year is the ceiling of your budget. If you need to dictate into EHR systems or specialized healthcare platforms where Voice In has specific integrations.

Voice In has been around for years, it's stable, and 600,000+ people use it for a reason. For raw, affordable Chrome-based dictation, it works.

When Rubil is the better choice

If you write across Gmail, Slack, Notion, Google Docs, and other platforms and want the output formatted for each one automatically. If you're tired of editing transcripts before sending. If you need your names, acronyms, and technical terms spelled correctly every time. If you also use native Mac apps and want voice dictation that covers both browser and desktop. If you want AI-powered transcription and formatting instead of Chrome's built-in speech engine. Rubil publishes its send-ready accuracy monthly so you can see how often the formatted output lands with no edits.