Short answer: Final Draft has no dictation feature of its own, so use a system-wide dictation tool that types at the cursor. Set the element type with Tab and Enter first, then speak the words. Keep formatting on the keyboard and content on the voice, and nothing breaks.
Screenwriting is the one kind of writing where the words were always meant to be spoken. Dialogue exists to be performed. Action lines are read at pace. The whole form is built around how something sounds and how long it takes. So there is a real argument that dictation belongs in a screenplay more naturally than it belongs in a spreadsheet or a legal brief.
Final Draft, though, is not a plain text editor. It is a formatting engine that decides what a line is before it decides what it says, and that makes naive dictation frustrating. Speak a scene heading and you get a mangled action line. Speak a character name and SmartType replaces it with a different one. Most people try dictation in Final Draft once, hit that wall, and go back to typing.
The fix is a division of labor, and once you set it up the app stops fighting you. Here is how to make it work.
Final Draft does not have dictation. That is fine.
There is no microphone button in Final Draft and no dictation preference to find. This surprises people, but it is actually the easier situation, because it means you are not choosing between a built-in tool and an external one. You are just choosing a system-wide dictation tool that inserts text at the cursor in whatever app has focus.
Anything that works that way works in Final Draft. The app receives the text exactly as if you had typed it, which means it applies the current element's formatting, respects the current margins, and behaves normally. Nothing about a screenplay document is hostile to inserted text. What is hostile is trying to say the formatting out loud.
Voice Keyboard Pro works this way on Mac: it lives in the menu bar, you hold a hotkey, speak, release, and the text appears at your cursor in whatever app you are in. There is no per-app setup, no integration to configure, and nothing to enable inside Final Draft.
The rule that makes this work
Format with the keyboard. Content with the voice.
Final Draft already gives you extremely fast keyboard control over element types. Tab and Enter cycle you between Scene Heading, Action, Character, Dialogue, Parenthetical, and Transition, and there are direct shortcuts for each. Those keystrokes are single presses. They are already faster than saying "new scene heading" out loud, and unlike speech they are unambiguous.
So the loop looks like this:
- Press the key that puts you in the right element.
- Hold your dictation hotkey.
- Say the words for that element and nothing else.
- Release. The text lands with the element's formatting already applied.
- Press the key for the next element. Repeat.
Your left hand stays near Tab and Enter, your other hand holds the hotkey, and you never say a formatting instruction aloud. This is the entire technique. Everything below is refinement.
Element by element
Action lines
Action is where dictation pays off most, and it is also where it changes your writing for the better. Action lines are supposed to be lean and readable at speed. When you speak them, you naturally produce shorter sentences and more concrete verbs, because the overwritten sentence sounds wrong coming out of your mouth in a way it does not look wrong on screen.
Speak action in beats rather than paragraphs. One or two sentences per hold, then release. The pause between holds is where you decide what the next image is, which is the same rhythm a reader will experience.
One thing to watch: dictation adds punctuation, and action lines in a spec script tend to use fewer commas than prose. Read the passage after you finish a page and cut the commas that slow the read.
Dialogue
This is the reason to dictate a screenplay at all. Performing a line and then writing it down is a technique writers already use; dictation just removes the transcription step between the two.
Set the element to Dialogue, then say the line the way the character would say it. You will hear immediately when a line does not fit the mouth. Contractions land where a real person would use them. Rhythm shows up on its own. Lines you would have written as a tidy sentence come out clipped, which is usually the better version.
Do not narrate stage business into the dialogue. If you want a parenthetical, stop, press the key for Parenthetical, dictate the word or two, then move back into Dialogue. Trying to fold it into the same breath produces a dialogue line with a stray phrase glued to the end.
Character names
This is the one that causes the most trouble, for two reasons that stack.
First, Final Draft's SmartType autocompletes character names as you enter them, which is a genuinely useful feature when typing and an actively hostile one when text arrives all at once from dictation. A dictated name can trigger a completion to a different character already in the list, and you will not notice until a read-through.
Second, character names in scripts are frequently invented, stylized, or spelled unusually, which is exactly the category of word any transcription engine is least likely to get right on first hearing.
Two fixes, and you want both:
- Type character names, do not dictate them. The Character element is one short line and SmartType makes it two or three keystrokes. There is nothing to gain from speaking it.
- Add the names to Smart Vocabulary. Voice Keyboard Pro's Smart Vocabulary is a personal dictionary with replacement rules, so you can teach it that the sound you make maps to the exact spelling you use. Do this for your cast, your invented locations, your fictional companies, and any technical jargon the script leans on. It fixes the names when they appear inside dialogue and action too, not just in the Character element, which is where you actually cannot avoid saying them.
Setting up ten or fifteen entries before you start a draft is the highest-return ten minutes in this whole workflow.
Scene headings
Do not dictate these. Say the words "interior" or "exterior" out loud and you will spend more time fixing the result than you would have spent typing it.
Scene headings are the most abbreviated, most conventionalized line in the format: an abbreviation, a location in caps, a dash, a time of day. Final Draft's SmartType already autocompletes locations and times of day you have used before, so once a location exists in the script it is a few keystrokes. Type them.
The exception is a long location name you have never used, in a script full of them. In that case set the element first, dictate just the location, then fix the abbreviation and dash by hand.
Transitions and shots
Type them. They are short, uppercase, and mostly drawn from a fixed vocabulary that SmartType already knows. Speech has no advantage here.
Where dictation actually wins
Put together, the pattern is clear: dictation wins on the long, prose-shaped parts of a screenplay and loses on the short, formatted ones. That is a good trade, because the long parts are most of the page count and all of the hard thinking.
The speed argument is straightforward. A comfortable adult types around 40 words per minute and a strong typist reaches 80 to 100. Ordinary speech runs 130 to 150 words per minute. For dialogue and action, where you are producing continuous language rather than navigating structure, that gap is the difference between finishing a scene in one sitting and losing the thread halfway through.
The less obvious win is the one about staying inside the scene. Typing a screenplay involves constant micro-interruptions: fixing a typo, correcting a capital, watching the cursor. Every one of those pulls you out of the room you are imagining. Dictating action and dialogue in beats keeps your attention on what the characters are doing while the words get recorded almost as a side effect. Writers who have used voice for long-form work describe this as the main benefit, well ahead of raw speed. We looked at that effect more broadly in our guide to voice typing for screenwriters.
Setting it up
The Mac setup is short:
- Install Voice Keyboard Pro and grant microphone and accessibility permissions when prompted. Accessibility is what lets text be inserted at the cursor in another app, which is exactly what Final Draft needs.
- Pick a hotkey you can hold comfortably while your other hand rests on Tab. Something you will not hit by accident inside Final Draft's own shortcut set.
- Open Smart Vocabulary and add your character names, locations, and any invented proper nouns before you start writing.
- Open a script, put the cursor in an Action element, hold the hotkey, and say a sentence. Confirm it lands with correct formatting.
If nothing appears, the cause is almost always the accessibility permission not being fully granted, or granted before an update and now stale. Toggling it off and on in System Settings resolves it.
Notes, outlines, and the Beat Board
The parts of Final Draft outside the script page are, if anything, better suited to dictation than the script itself, because they are unformatted.
Beat Board cards, outline entries, and ScriptNotes are all plain text fields with no element rules and no SmartType interference. This is where you can talk freely: dump a scene idea into a card, argue with yourself about a structural problem in a note, record why a scene exists before you write it. Structural thinking is verbal thinking, and forcing it through a keyboard is what turns a five-minute idea into a twenty-minute one.
A workflow a lot of writers land on: dictate the whole beat sheet in one pass, talking through the story out loud as if pitching it, then convert beats to scenes and dictate the pages underneath them. The pitch and the outline become the same artifact.
Revisions and production drafts
Once a script is locked and you are working in revision mode, the calculus shifts. Revision passes are surgical: a line here, a word there, a page of new material in the middle of an existing scene.
For small changes, click into place and type. For anything longer than a sentence, set the element and dictate as usual; revision colors and locked page numbers are applied by Final Draft based on where the text goes, not how it got there, so dictated text is treated identically to typed text.
The one habit worth keeping is to dictate into the correct element rather than dictating into a scratch document and pasting. Pasting into Final Draft can carry formatting assumptions with it and produces more cleanup than it saves.
Common problems
The wrong character name keeps appearing
SmartType completed the dictated name to an existing entry. Type character names instead of dictating them, and add every name to Smart Vocabulary so the same substitution does not happen inside dialogue.
My dialogue has too much punctuation
Dictation punctuates for prose by default, and dialogue in a script often reads better with less. Do a punctuation pass at the end of a scene rather than fighting it line by line. Reading the scene aloud, which you should be doing anyway, will tell you which commas to cut.
Everything landed as an action line
You dictated before setting the element. The text is placed into whatever element the cursor is currently in. Select the misplaced text and change its element type, then get in the habit of pressing the element key first.
Technical terms come out wrong
Any script with a specific world will have vocabulary no general engine has heard: a ship name, a medical procedure, a piece of slang you made up. Smart Vocabulary exists for exactly this, and unlike a global autocorrect it applies only to your dictation, so the fix does not leak into the rest of your system.
Dictation is fine but I lose the thread when I stop to format
Try dictating the whole scene as continuous action first, in one element, then splitting it into Character and Dialogue elements afterward. Some writers find that formatting passes and writing passes should not be interleaved at all. This is the same principle behind drafting in a plain editor first; if you prefer that approach, our guides to dictating in Scrivener and Ulysses cover the draft-then-import route in more detail.
What about privacy?
Unproduced scripts are sensitive material, and writers are right to ask where the words go. Our position is simple: the server stores only operational pings. No audio and no transcript content is stored. Your pages are yours.
Frequently asked questions
Does Final Draft have built-in dictation?
No. There is no microphone button or dictation preference in the app. You use a system-wide dictation tool that types at the cursor, and Final Draft treats the result exactly like typed text.
Will dictation break my script formatting?
Not if you set the element type before you speak. Inserted text inherits the current element's formatting. Formatting only breaks when you try to speak the structure instead of pressing the keys for it.
Can I dictate on the iPad or iPhone version?
On iOS you can use a custom keyboard with a built-in mic button, which gives you dictation in Final Draft the same way it gives you dictation in any other iOS app. The element keys are the constraint on a small screen, not the dictation.
How fast is this really?
For dialogue and action, expect a large gain, since speech runs 130 to 150 words per minute against 40 for an average typist. For scene headings, character names, and transitions, expect none, which is why the workflow above tells you to type those.
Should I dictate a whole first draft?
Many writers do, and the format rewards it, since a screenplay page is roughly a minute of screen time and reading a scene aloud is already part of the craft. Just budget a formatting and punctuation pass afterward rather than expecting the first pass to be clean.
Start with one scene
Do not convert your whole process at once. Pick one scene that is mostly dialogue, add the two or three character names to Smart Vocabulary, and write it with the element keys in one hand and the hotkey in the other. You will know inside a page whether the rhythm suits you.
Voice Keyboard Pro has a free tier with daily limits, which is enough to test the workflow across a few scenes. Pro is $4.99 per month or $34.99 per year.