Short answer: Final Cut Pro has no built-in microphone button, and you do not need one. A system-wide dictation app types at your cursor in any focused text field, so you can speak into marker notes, clip notes, titles, and caption text. Pick a modifier-heavy hotkey so it does not collide with Final Cut's shortcuts.
Editing is not usually thought of as a writing job, which is why the amount of typing in a Final Cut Pro session comes as a surprise when you actually count it. Logging a shoot means naming and describing clips. Reviewing a cut means leaving notes on markers. Finishing means titles, lower thirds, captions, and then a description, a title, and a set of tags for wherever the video is going.
None of that is glamorous, and all of it happens with one hand hovering over a keyboard you would rather be using for J, K, and L. This guide covers where dictation genuinely helps inside Final Cut, where it makes things worse, and the one setup step that determines whether the whole thing works or fights you.
Final Cut Pro has no dictation feature, and does not need one
There is no microphone button in Final Cut Pro's interface, no voice input panel, and no plugin required to add one. People search for a Final Cut dictation extension and come up empty, and conclude it cannot be done.
The reason it can be done is that dictation does not have to live inside the app. A system-wide dictation tool works one layer below the application: it types at whatever cursor is currently active, in whatever window has focus. As far as Final Cut is concerned, the text arrives the same way it would if you had typed it. No integration exists because none is needed.
The practical form of this is a hotkey. Hold it, speak, release, and the words land where your cursor is. Click into a marker's note field, hold, describe the problem, release, hit return. The same motion works in the browser's notes column, in the text inspector for a title, in a caption, in a keyword name, in the Share metadata fields, and in the name of a project you are about to duplicate for the third time. This is covered more generally in our guide to hands-free typing on Mac.
Set your hotkey before you do anything else
This is the step that decides whether dictation feels like a tool or a nuisance in Final Cut specifically, and it is worth ten seconds of thought.
Final Cut Pro has one of the densest keyboard shortcut maps of any Mac application. Nearly every unmodified letter does something. Single keys select tools, set in and out points, add markers, blade, and navigate. Many modifier combinations are also spoken for. If you pick a casual hotkey, you will eventually hold it while the timeline has focus and trigger something you did not intend.
Two things protect you.
Pick a combination Final Cut does not use. A double modifier plus a key, or a function key, is the safe zone. Avoid bare letters and avoid single-modifier letter combinations entirely, because that is where Final Cut lives.
Understand what focus means here. When a text field is active, keystrokes go into the text field rather than firing shortcuts. That is the normal, intended behaviour, and it means the risk window is smaller than it first appears: the collision problem is mostly about accidentally triggering the hotkey when a text field is not focused. Getting into the habit of clicking into the field first and only then holding your key removes almost all of it.
Test it once before a real session. Open a project you do not care about, click into a clip's notes field, dictate a sentence, then click on the timeline and hold the same key to confirm nothing dramatic happens. Thirty seconds now, no surprises later.
Where dictation actually earns its place
Not every text field in Final Cut is worth speaking into. These are the ones where the difference is real.
Marker notes, which are the biggest win
Markers are where editors leave messages for their future selves, and almost everyone underuses them for one reason: writing the note interrupts the review. You are watching a cut, you see a problem, and the choice is between stopping to type a useful description or dropping a bare marker and hoping you remember what it was about. Most people drop the bare marker. Then, an hour later, they are staring at an unnamed marker at 04:12 with no idea what was wrong.
The result is that marker notes tend to be terrible. Not because editors do not know what is wrong, but because typing a full sentence mid-review costs enough attention that people compress everything into three words they will not understand later.
Speaking the note removes that cost. Stop, mark, click into the note, hold the key, and say the whole thing: "audio dips under the music here, and the cut on his eyeline is a frame early, check the b-roll from take four." That is a note you can act on tomorrow. It took four seconds to say and would have taken thirty to type.
This changes what markers are for. When notes are cheap, you leave more of them and they are more specific, which is the entire point of the feature.
Clip notes and logging
Logging footage is the most typing-heavy task in the whole workflow and the one editors most often skip, then regret. If you shot four hours of interview and never wrote down what was in it, you will pay for that in the edit.
The browser's notes field is designed for exactly this and is miserable to fill by hand at scale. Dictation turns logging into something closer to watching: play the clip, and as you go, click the notes field and speak what is in it. "Good take, he stumbles on the second answer but recovers, strong close." Keyword names, favourite ranges, and rejects still want the keyboard because they are shortcuts, not text.
The two-handed rhythm that works well: left hand on the transport keys, right hand clicking into fields, voice doing the writing. Nothing competes for the same limb.
Titles, lower thirds, and on-screen text
Title text is dictated well because it is prose, and because the failure mode is easy to catch: it is on screen at 40 point type, so an error cannot hide. Click into the text field in the inspector or in the viewer, speak the line, then check the spelling of any name yourself.
One habit worth building for titles specifically: names and job titles in lower thirds are exactly the class of word transcription gets wrong, and exactly the class of error that is embarrassing on delivery. Handle them with a vocabulary rule rather than by proofreading each time. More on that below.
Captions and subtitles
Caption text fields accept dictated text like any other field. Whether this is worth it depends on the job. For a short piece with sparse on-screen text, speaking each caption is comfortable. For a full-length subtitle pass on a long interview, you are transcribing rather than writing, and you should be using a transcription workflow rather than repeating someone else's words into a microphone.
The useful middle case is fixing and rewriting captions: adjusting a line that reads badly, splitting a caption that runs long, or rewriting for a different reading level. That is writing, and writing goes faster spoken.
Everything after the export
The writing does not stop when the render does. Video titles, descriptions, chapter lists, tags, client emails, and the notes that go in the delivery folder are all prose, and they are all the same system-wide dictation. Since publishing is where most of the remaining typing lives, our guide to dictating on YouTube covers descriptions, comments, and community posts in detail.
Where to keep your hands on the keyboard
Being honest about this matters more than being enthusiastic, because dictation used in the wrong place is what convinces people it does not work.
- Timecode entry. Typing numbers into the timecode field is precise and fast with the keyboard. Speaking digit strings is neither. Type them.
- Navigation and tool selection. Final Cut's single-key shortcuts are one of the fastest interfaces in professional software. Voice has nothing to add here and dictation is not a command system.
- Trimming and timing. Frame-accurate work is a keyboard and trackpad job, always.
- File naming schemes with strict formats. If your naming convention includes underscores, version numbers, and date codes, type it. Structured strings are the weakest case for dictation and always will be.
- Anywhere a single character matters. Codec names, aspect ratios, LUT filenames. Precision beats speed here.
The pattern behind all five: dictate prose, type parameters. If a human would read it as a sentence, speak it. If it is a value, type it.
Teach it your project's vocabulary
Post-production runs on words that no general transcription is going to guess. Client names, agency names, talent names, project codenames, product names, and the format and workflow terms that fill every note you write. These are the same handful of words appearing in every clip note and every marker on a job, which makes them the single highest-value thing to fix once.
Smart Vocabulary is a personal dictionary with replacement rules. You add the term, and if a word comes out mangled in a predictable way, you add a rule mapping the wrong output to the right one. Before a big job, spend five minutes adding the client, the talent, the product, and the project name. Every note for the next six weeks comes out correct.
This is worth doing per project rather than once, because the terms that matter change with the client. It is also the difference between dictation you trust for logging and dictation you have to proofread, which is the difference between using it and not.
Client reviews and the notes that come out of them
The other significant writing load in editing is not inside Final Cut at all. It is the review call, where a client talks for forty minutes and you are expected to leave with an accurate list of changes.
Trying to type notes during a review means you stop listening, and the notes you get are worse for it. Meeting Mode on Mac handles the session with speaker detection and produces AI notes afterwards, and calendar meeting detection means it can start when the review does rather than after you remember. What you take away is a record of what was said, which you then turn into markers on the timeline.
That second step, converting a client's rambling comment into a specific marker note, is itself a dictation job. Read the line, click the marker, say the actionable version.
Logging on location, before Final Cut ever opens
Some of the best notes are made on the day, not in the suite, and on the day there is no Mac open. The iPhone keyboard has a microphone button and works in any app, so shot notes, setup details, continuity observations, and the "we will need to fix this in post" list can go into whatever notes app you use while they are fresh.
Voice Edit is useful here for the same reason it is useful anywhere on a phone: fixing a typed note on a touch screen is unpleasant, and speaking the correction skips the cursor entirely. If your production is multilingual, dictating with two-way translation across 24 languages means notes taken in one language arrive readable to a crew working in another.
A workflow that holds together
Putting it in order for a typical job:
- Before the shoot, add the client, talent, product, and project names to your vocabulary list.
- On location, capture notes on the phone as they occur. Do not trust memory for continuity details.
- Ingest and log with the transport keys under your left hand and the notes field under your voice. Speak full sentences, not keywords. You are writing for a version of yourself who has forgotten everything.
- Assemble with the keyboard. Dictation contributes nothing to a rough cut and should stay out of the way.
- Review passes with markers. Speak every note in full. This is where the habit pays for itself the most.
- Titles and captions by voice, with names checked against your vocabulary rules.
- Client review in Meeting Mode, then convert the outcome into marker notes.
- Delivery writing by voice, since descriptions and handover emails are prose.
The through-line is that the keyboard keeps everything it is good at. Nothing here asks you to give up shortcuts, and the editors who get the most out of this are not the ones who dictate the most, but the ones who drew the line in the right place.
On privacy, since footage is usually confidential
Unreleased client work, embargoed products, and interview content under agreement are the normal case in post, not the exception, so it is fair to ask what leaves your machine. Our server stores only operational pings. No audio and no transcript content. Your marker notes and clip logs live on your Mac.
If you are working under a client NDA with specific requirements about cloud services, check the terms before adding any new tool to the pipeline. That is true of every application in a post workflow and it is true of this one.
Getting started
Voice Keyboard Pro lives in the Mac menu bar. Hold your hotkey, speak, release, and the text appears at your cursor in whatever application is in front, Final Cut included. Smart Vocabulary holds your project terms, Meeting Mode covers client reviews with speaker detection and notes, and calendar meeting detection starts it for you. On iPhone it is a keyboard with a mic button for on-location notes, with Voice Edit and two-way translation.
There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. If you want a single test that tells you whether this belongs in your workflow, do a review pass on a cut you already know needs work and speak every marker note in full sentences. Read them back the next morning. The gap between those notes and the three-word ones you usually leave is the whole argument.
For the broader picture beyond one application, see our guide to voice typing for video editors, and for presentation and pitch work alongside the edit, dictating in Keynote on Mac.