Final Draft 13.4.0 Mac

Beat Board arrived before you even typed FADE IN. Final Draft — screenwriting software for film, television and stage scripts from Cast & Crew Production Software — ships with a handful of tools a newcomer will meet within the first hour, and the Beat Board is the one worth clicking first.

Beat Board — a freeform canvas where you drag beats into a rough story order, then send them straight into the script as outline elements. It is the bridge between index cards and pages.

ScriptNotes — margin-based annotations that stay with the script but never print. Use them to flag a line that needs research or a character beat that feels flat.

Templates — Final Draft ships with templates for screenplays, stage plays, multi-camera sitcoms and graphic novels. Choosing one sets margins, element styles and page breaks automatically.

SmartType — the app remembers character names, scene headings and locations as you type, offering pop-up completions so you never type "DETECTIVE HENDERSON" twice.

It is worth mentioning that this is not the place for that phrase. Here is the extended section instead.

Most questions about Final Draft come from people who have written in a regular word processor and are switching over for the first time. The formatting scares them, not the writing itself. The answer is usually simpler than expected: Final Draft formats as you type, so you do not need to know how wide a dialogue block should be or how many blank lines sit before a scene heading. You type a character name in uppercase, press Return, and the next line is already formatted as dialogue. Type INT. or EXT. and the scene heading style applies itself.

Another common question is whether a script written in Final Draft will look right when it reaches a producer or an agent. The industry has settled on a standard screenplay format, and Final Draft is built around it. A page from Final Draft 13.4.0 matches the formatting expectations of studios, contests and writing programs that request screenplays in the Final Draft file format.

Highland 2 keeps scripts in plain-text Fountain

People often weigh Final Draft against a handful of other Mac writing tools. The first comparison is with Highland 2, a plain-text screenwriting app. Highland 2 keeps scripts in Fountain, a plain-text markup format, and is deliberately lightweight. It suits writers who want minimal interface chrome and who are comfortable with text files. Final Draft is the heavier, feature-complete option: Beat Board, ScriptNotes, revision tracking, production features and the reporting tools all live inside one application. If you only need to write pages, Highland 2 gets out of the way. If you need to build a story, track revisions and prep a shooting script, Final Draft covers that ground.

Another comparison is with Fade In, a screenwriting app that positions itself as a professional alternative. Fade In has a similar feature list: templates, revision marks, reports and import filters for many formats. Writers who have used both often say Fade In feels closer to a utility, while Final Draft feels like an office. The difference shows in small moments — dragging beats on the Beat Board, opening the Navigator to jump between scenes, or using SmartType to autocomplete a location. Fade In can do most of the same jobs, but the route to each one is different.

A third comparison is with Scrivener, which is not a screenwriting app first but is often used for scripts because of its corkboard and binder. Scrivener is a project manager for long-form writing, and it contains a screenwriting mode. Final Draft 13 integrates with Scrivener, which means a writer can keep research and notes in Scrivener while drafting in Final Draft. The two tools do not overlap as much as people assume: Scrivener organizes, Final Draft formats.

Spell check and text replacements work system-wide

On macOS, Final Draft cooperates with several parts of the system. The app supports standard macOS text editing behaviors, so a writer can use the built-in spell checker, keyboard shortcuts and system text replacements. The script can be printed to PDF directly, which is how most writers send drafts to collaborators who do not own Final Draft.

Final Draft also works alongside Final Draft Go, the companion app for iPhone and iPad. A writer who starts a scene on the Mac can continue on an iPad during a commute, then return to the Mac version with the changes intact. That workflow matters to writers who do not want to carry a laptop everywhere but still need the full formatting engine when they sit down at a desk.

For writers who use Scrivener for project management, the integration means the Scrivener binder and the Final Draft script stay separate but connected. Research, character sheets and location notes live in Scrivener; the script itself stays in Final Draft. The exchange works both ways, so a script can move between the two apps without losing formatting.

Tab or Enter toggles a line’s assigned element

The first snag new users hit is element confusion — a line comes out as dialogue when it should be action, or a character name refuses to become a character name. The fix is usually the Tab key or the Return key. Final Draft cycles through script elements as you type: Return after a scene heading gives action, Return after action gives a blank line, typing a name in uppercase then pressing Return gives dialogue. If a line is in the wrong element, click the element name in the toolbar or use the keyboard shortcut to change it. The behavior becomes automatic after a day or two.

Another common issue is SmartType suggestions that no longer match the script. If a character was renamed from SARAH to DR. VANCE, SmartType may still offer the old name from its memory. The fix is to clear the SmartType list from the Tools menu, then type the new name once. SmartType rebuilds its memory from the current script.

A third snag is page count anxiety. Writers notice that a script in Final Draft looks different in page count than the same text in a word processor. That is expected: screenplay formatting uses Courier, specific margins and specific line spacing, so the page count is the industry-standard count, not the word processor count. If a writer is using an old script converted from Word, the page count may shift after the formatting is applied. That is not a bug; it is the screenplay format doing its job.

Cursor lands in last night’s scene on launch

A typical morning session starts with the script already open from the night before. The writer opens Final Draft, and the script appears with the cursor blinking in the last scene. The first move is often to the Beat Board: yesterday's ending left three beats unordered, and the writer drags them into a new sequence before writing a single line of dialogue. One beat moves left, another splits into two, and the new order feels right.

Then the writer switches back to the script view and starts typing. A scene heading comes first — INT. DINER - DAY — and Final Draft formats it as a scene heading. A line of action follows: the waitress slides a coffee cup across the counter. SmartType offers the waitress's name, and a tap of Return accepts it. The dialogue writes itself from there, one exchange at a time, with Final Draft handling every margin and indent.

Mid-morning, the writer remembers a note from yesterday: a character's motivation feels thin in the second act. Instead of scrolling, the writer opens the Navigator and jumps to the scene. A ScriptNote goes onto the margin: "Give her a reason to stay." The note will not print, but it will be waiting the next time the scene is revised.

Before lunch, the writer exports a PDF and sends it to a writing partner. The PDF opens cleanly on the partner's machine, and the partner's notes come back as a marked-up PDF. The writer opens the script again, makes three small changes, and saves. The whole session happened in one application, from planning to draft to export.

That is the rhythm Final Draft settles into: planning on the Beat Board, writing in the script view, noting in the margins, and exporting when the draft is ready. The tools stay out of the way until they are needed, and the formatting never interrupts the typing.

Version 13.4.0 delivers minor bug fixes.

• macOS 12 Monterey or later
• Intel processor (x86 64-bit)
• Active internet connection for initial sign-in