Whisper DictatorWindows app

We wanted to dictate without sending the audio to anyone.

We built a voice dictation app that transcribes inside your own computer. This page isn’t the sales pitch. It’s the story of why we decided to build it this way.

Whisper Dictator · dictationTranscribing on-device
  1. 1Hold key
  2. 2Speak
  3. 3Release
LocalText
What it is

Before the story, what it actually is.

One factual paragraph, so nobody has to guess what we’re talking about.

Whisper Dictator is a Windows app that turns speech into text. You hold a key, speak, let go, and the text is typed wherever your cursor already was: email, editor, browser, internal system. Transcription happens inside your machine. No audio is sent to any server, and once it’s installed it works offline.

The pain we saw

The problem was never the speed of dictation.

It was where the audio went: a discussion that ends before it begins.

We kept seeing the same scene in medical practices, offices and technical teams: a good part of the workday turns into record-keeping. The appointment is over, and someone has to turn what they already know into text inside a system. The work is done; what’s left is typing it up, competing with the next appointment.

The obvious way out would be dictation, and almost everyone had already tried it. What got in the way was always the same detail: the dictation services built into the operating system or the browser send the audio to another company’s server. A patient note, a deposition, a clause, an account number: it all leaves the machine before it becomes text. In a regulated industry, that ends the conversation.

There was one more detail the sales material for these services doesn’t mention: no internet, no dictation. The tool fails exactly where it would be most useful: on a plane, in an area with a weak signal, in a practice with an unstable network. It was the sum of these three things that convinced us to build instead of recommending something off the shelf.

The decisions we made

Three choices that shaped the rest of the project.

Each one closed a door. It’s more useful to explain what we closed than to list what stayed open.

01 · Where to process

On the user’s machine, not in our cloud

It was the most expensive decision, and the first. Running speech recognition on our own servers would have been simpler to maintain and would have worked on any operating system. We chose the opposite: the model is downloaded to disk during installation, and transcription happens right there. The price is a longer initial setup and a dependence on the user’s hardware. The gain is the only thing that solved the original pain: the audio doesn’t leave the machine.

02 · How to trigger

Holding a key instead of always listening

The comfortable alternative was a wake word, with the microphone always open, waiting for the command. We ruled it out because in practice it undoes the previous decision: processing locally doesn’t help if the microphone stays on all day. Activation is an explicit gesture: the microphone is only on while the key is held down. The cost is not being able to dictate with your hands full, and we think that cost is fair.

03 · Where to deliver

Typing into the field that was already open

We could have built our own window with the text for you to copy. It would have been easier to build and would work the same everywhere. But it would create one more place the text has to be moved out of, which is exactly the friction we wanted to eliminate. The shortcut is global, and the text goes in wherever the cursor already was. The price shows up in compatibility: that’s what ties the app to Windows for now.

Where it stands, honestly

What works today and what doesn’t yet.

A stated limit is worth more than a superlative, especially when trying it takes ten minutes.

What works

99 languages recognized, chosen from the system tray menu, and an ordinary PC with 4 GB of memory can handle it. An NVIDIA graphics card speeds it up but isn’t required. Besides live dictation, audio and video files you already have are transcribed in full on your own machine, with no upload and no per-minute charge. The free version gives you seven transcriptions a day, with every model and language.

What doesn’t

Today it only exists for Windows 10 and 11. Mac and Linux are on the roadmap, with no date. And it transcribes what you say or the file you choose; it doesn’t sit in on a live meeting to produce minutes that identify the speakers. That’s a different category of tool.

The trade-off you inherit

Accuracy varies with model size. A bigger model gets more right and takes longer; a smaller one responds instantly and makes slightly more mistakes. No setting solves both sides, and the choice is left to the user.

Whisper Dictator came out of Sincron IA, the same team that builds process automation into client operations. When the bottleneck is bigger than one tool can solve, the path is the Discovery stage.

Want to see the actual product?

Purchase, download and documentation are on its website. This text was only meant to explain why it exists.