Final Draft's built-in voice dictation is Mac-only. On Windows, you have been stuck. StarWhisper fills the gap, typing dialogue, action, and parentheticals straight into Final Draft, WriterDuet, Fade In, and Celtx as you speak.
Speaking dialogue out loud is a screenwriting tradition. Dictating it directly into Final Draft makes the tradition practical.
Speaking dialogue out loud catches what reads naturally and what does not. With dictation, the "say it aloud" pass IS the writing pass. Drafts move faster.
StarWhisper types what you say. The element switching, the slug line caps, the character cue formatting, all that is Final Draft's job. Dictation handles the words; the script app handles the format.
Six surfaces in a working script where voice replaces typing
Dialogue is the surface where dictation shines. You are already supposed to say lines aloud to test how they read. Dictating bypasses the typing tax and lets the spoken rhythm flow straight onto the page, exactly the way screenwriters have always taught.
The action block is the densest prose in a screenplay. Twenty to forty words per beat, often a dozen beats per scene. Dictating this at 130 to 150 words per minute beats typing at 60. Cumulative time savings across a draft are measured in days, not hours.
Long parentheticals like (sotto voce, eyes drifting toward the window) and inline stage directions add texture but are slow to type. Dictating them keeps your hands on whatever you are already doing and your eyes on the screen, not the keyboard.
Before the script comes the treatment, the beat sheet, the synopsis, the logline. These live in Word, Scrivener, Notion, or Google Docs depending on your workflow. The same dictation hotkey works in every one, so you stay in one input mode end to end.
Once the script is out, you are writing pitch documents, character bios, episode breakdowns, and notes back to producers. None of that is screenplay-formatted, all of it is long prose. Dictation cuts the typing time roughly in half.
The screenwriter's inbox is its own job. Replies to notes, scheduling for table reads, pitch follow-ups. Dictation works the same in Outlook, Gmail in a browser, and Slack as it does in Final Draft, because the layer is below the application.
Final Draft is the industry-standard screenwriting application. It is also one of the longest-running ones, and its feature set reflects decades of mostly-Mac-centric development. The built-in voice dictation features tie into Apple's system dictation framework, which is why they have always worked on the Mac version and never had a real Windows equivalent. Some marketing copy across the years has implied parity, but in practice Windows screenwriters who want voice input have had a poor set of options.
Dragon NaturallySpeaking was the historical default. It works, but it is expensive at $699 for a one-time license, the user interface has barely changed in years, and active development has slowed dramatically since Nuance was acquired by Microsoft. The built-in Windows Voice Typing is free and tolerable for chat-style sentences, but its accuracy on long creative prose is uneven, and it does not handle the rhythm or vocabulary of dialogue particularly well.
The third option is a modern Whisper-based desktop layer. StarWhisper runs OpenAI's Whisper locally on your Windows machine and types the transcription into whatever text field is focused. Final Draft, WriterDuet, Fade In, Celtx, your beat sheet in Notion, your email to your manager. The same hotkey works everywhere because the dictation happens at the operating system input level, not as a plugin.
Every screenwriting craft book that talks about dialogue makes the same recommendation: read your scenes aloud. The page is silent; the screen is not. Dialogue that reads on paper as elegant and natural often turns out, when spoken, to be clunky, awkward, or rhythmically wrong. The "say it aloud" pass is a quality gate that catches problems no silent read-through will catch.
Voice dictation collapses that pass into the writing pass. When you say a line of dialogue out loud as you write it, you hear it. If it is clunky, you stop, rephrase, dictate the better version. The bad first draft never makes it to the page in the first place. Many screenwriters who try this report that their dialogue gets better faster, not just because dictating is fast but because the silent typing layer never caught what their ear catches in real time.
Action lines benefit from the same effect for a different reason: pacing. A line of action that reads ploddingly when typed often reads brisk and clear when dictated. You hear the rhythm in your own voice before it lands on the page, and you naturally shape it tighter.
The workflow is undramatic, which is the point. Open Final Draft. Open your script. Click into whatever element you are working on: scene heading, action, character, dialogue, parenthetical, transition. Hold the StarWhisper hotkey, speak, release. Final Draft sees the text as if you had typed it. The auto-formatting that turns "INT. APARTMENT, NIGHT" into a proper slug line still happens; the auto-cap on character names still happens; the margin and indent rules still apply.
For dialogue specifically, the most natural pattern is: type or click into the character cue field, type the character name (it auto-caps), press Tab to drop into the dialogue line, hold the hotkey, speak the line, release. The dictated text lands in the dialogue element with the right margins. Press Tab or Enter to end the dialogue and move to the next element, exactly as you would with typed input.
For action blocks, the pattern is even simpler: click into the action element, hold the hotkey, speak the description, release. Speak the next beat and dictate again. Most screenwriters find that they want to dictate one beat at a time rather than a whole paragraph at once, because that gives them a chance to hear what just landed before committing to the next beat.
Final Draft has the most market share in feature television and studio film work, but it is not the only screenplay app on Windows. WriterDuet has a desktop client and a strong web app, and its collaboration features have made it popular for writers' rooms working remotely. Fade In is a clean, fast, well-priced alternative that screenwriters who value craft over enterprise features often prefer. Celtx is widely used for indie and student work and runs in a browser as well as a desktop app. KIT Scenarist and Trelby exist for niche workflows.
StarWhisper works in all of them on Windows without any per-app configuration. The dictation layer types into whatever field is focused. WriterDuet's web app gets dictation into the script editor the same way as Final Draft's native app. Fade In's element switching is different from Final Draft's, but the typed input is the same, so dictation feels identical. Celtx in the browser is just a web text field. Highland 2 is Mac-only as a desktop app and therefore out of scope for this page, but its web tools accept dictation in a browser like any other site.
For the prose drafts that live outside the script, like treatments in Microsoft Word or beat sheets in Scrivener, the same hotkey works. See the voice to text for writers overview and the voice to text for copywriters overview for adjacent workflows that share the same tool.
The biggest accuracy concern for screenplay dictation is not industry jargon but character names. A modern thriller might have a "Detective Kovalenko" and a "Sister Adelaide" and a "Mr. Renworth," none of which Whisper has any reason to know in advance. In practice, common Western names land cleanly: Sarah, James, Maria, Daniel, Olivia, Marcus, and so on come out correctly. Less common names sometimes need a one-word correction the first few times they appear, after which you learn to pronounce them the way Whisper transcribes cleanly.
Industry jargon (cut to, dissolve to, fade in, fade out, intercut, montage, V.O., O.S., POV, beat, smash cut) lands correctly with Whisper because these words are well represented in the broader English corpus the model was trained on. Slang, regional dialect, period-specific vocabulary, and invented sci-fi words follow the same pattern as character names: a few corrections at first, then it settles down.
Pro users on NVIDIA GPU paths run the medium or large Whisper model, which handles edge cases noticeably better than smaller models. For a dense scene with a lot of unfamiliar proper nouns, the GPU path is worth having.
An unproduced screenplay is a sensitive document. It has commercial value in a way most prose drafts do not, and the writer often does not want it sitting on a third-party server while in development. The standard cloud transcription model, where audio is uploaded to a vendor, processed remotely, and deleted on some schedule, is awkward for working screenwriters.
StarWhisper runs Whisper locally on your CPU or GPU. The audio never leaves your machine. There is no transcription cloud, no audio retention period, no third-party vendor with access to your dialogue. If you take your laptop to a coffee shop with no WiFi, dictation still works because nothing is uploaded.
Cloud Mode, which sends audio to the OpenAI Whisper API for faster turnaround on weaker hardware, is opt-in and disabled by default. For a working screenplay, leave it off. On any modern NVIDIA GPU the local path is fast enough that there is no performance reason to enable Cloud Mode.
The setup takes about three minutes. Install StarWhisper from the download page or the Microsoft Store. The installer auto-detects whether you have an NVIDIA GPU and picks the matching pack: CPU, CUDA 11, or CUDA 12. First launch downloads the Whisper model files, which takes a couple of minutes on a normal connection. After that the app lives in your system tray and listens for a hotkey.
For screenwriting, pick a hotkey that does not collide with anything in Final Draft's keyboard map. Right-side modifier keys (Right Ctrl, Right Alt) are good defaults because Final Draft's own shortcuts use the left-side modifiers. If you already use a foot pedal or programmable mouse for video editing or transcription work, those buttons are excellent hotkey targets because they keep your hands on the keyboard for the formatting work that still wants typing.
Test by opening a blank Final Draft document and dictating a few lines of dialogue and a paragraph of action. Once that flow feels comfortable, switch to your working script. For the first week, treat dictation as your dialogue tool only; that is where the win is largest and the learning curve smallest. Once dialogue dictation feels natural, extend to action lines, then to treatments and outlines, then to the email and Slack work that fills the rest of the writer's day. For complementary tools that work everywhere on Windows, see the works everywhere feature overview.
Use voice dictation to get rough scenes, notes, outlines, and rewrites onto the page faster.
The general writer's overview covering novels, essays, blog posts, and creative prose.
The commercial writing angle: ad copy, sales pages, landing pages, and email drafts.
The technical overview of why one dictation hotkey works in every Windows app.