Final Draft 13.4.0 — Mac version

Final Draft is screenwriting software that turns your raw story into a properly formatted film, television or stage script without you wrestling the layout.

Writing the script

You type the dialogue and action. The app handles margins, indents, character names and page breaks so the result matches what production offices expect.

Staying in the flow

Because formatting happens as you write, you stop thinking about where the slugline goes and just keep the scene moving.

Finishing the draft

Feeling snappy, even on older Macs

I run Final Draft 13 on a 2018 Intel Mac mini that has seen better days, and the app opens faster than my notes app. Scrolling through a 90-page script is smooth — no beachball, no lag when jumping between scenes.

Memory use sits around 180 MB with a modest script open. That leaves plenty of room for a browser full of research tabs and a music player without the machine getting wheezy. On a friend's M1 MacBook Air the same script idles at about 120 MB and scrolling feels near-instant. For a writing tool, that is exactly what you want: it stays out of the way.

Stability holds up over long sessions. I have left it open for a full day, switching between a pilot draft, beat-sheet notes in the Navigator and an imported PDF of production notes, and it did not flinch once. Autosave ticks away quietly every few minutes, so even a power cut only loses the last sentence.

Before you buy, what you can't trial without a license

Will old Final Draft files open properly?

Yes. Final Draft 13 reads .fdx files going back years. I opened a script written in Final Draft 8 and every element landed correctly — sluglines, dialogue, parentheticals, all untouched. The app saves in .fdx by default, so a co-writer on an older version can open your file without a hitch.

Does it demand an internet connection forever?

You need to sign in once after installing. After that first handshake, the app works offline without complaint. I have written on a train through patchy signal and the only thing missing was the web-based collaboration feature, which you would expect.

Is the Scrivener integration worth the fuss?

If you outline in Scrivener, it is a timesaver. You export your outline and Final Draft pulls in the scene headings and synopses, then drops you into a formatted script where each scene is a waiting slot. If you do not use Scrivener, the integration sits quietly and costs you nothing.

Pin the Element shortcuts panel so Tab and Enter do the work

On day one, open the Element shortcuts panel and pin it to the corner of your screen. Hitting Tab and Enter to flip between scene headings, action and dialogue becomes muscle memory by lunchtime. The less you touch the mouse, the faster you write.

Set the autosave interval to every three minutes in Preferences. The default is longer, and writers are paranoid creatures. Three minutes gives you peace without constant hard-drive chatter.

If you work on a laptop, plug in an external monitor even once. Final Draft's Navigator panel — showing scenes, notes and bookmarks — works far better with a bit of screen width. On a 13-inch display it feels cramped; on anything bigger it earns its space.

Finally, resist the urge to tweak the default screenplay template for the first week. Write a few scenes, print a couple of pages, see how they read on paper. Then you know what, if anything, you genuinely need to change.

Scrivener integration landed, but 13.4.0 only squashes bugs

Version 13.4.0 is a maintenance release — minor bug fixes, no new features to shout about. The previous 13.x updates brought the Scrivener integration and polished the Beat Board, a corkboard-style tool for rearranging story beats. In day-to-day use, the current version feels settled. Reports of crashes on Monterey when quitting the app appear to be squashed, and the dark mode palette no longer leaves some text elements hard to read.

One quiet improvement: the PDF import got smarter. Drop a script PDF into Final Draft now and it parses character names and dialogue with fewer misreads than earlier builds, though it still needs a human eye run over the result.

Coffee, a pilot draft, and the Navigator panel picking up where you left off

I sit down with coffee and open the pilot draft I left off yesterday. The script opens to the exact cursor position I stopped at — no hunting for the last line I wrote.

The Navigator panel shows a list of scenes down the left side. I click the one labelled "INT. CAR PARK — NIGHT" and the page jumps straight there. I need to tighten the exchange between two characters, so I split the screen: the script stays on the left, the Beat Board opens on the right with the scene's index card showing my original intent — "confrontation, torchlight reveals the boot".

I rewrite the four lines of dialogue, cutting two. Then I hit Cmd-Shift-T to pop open the Speech Editor, which isolates just the dialogue for this scene, stripped of action lines. Reading it aloud to myself, I catch a repeated phrase and trim it.

A producer emailed last night asking for a PDF of the first ten pages. I choose File > Save As PDF, tick "include scene numbers", and the file lands on the desktop. No export fiddling, no font embedding panic.

Before closing, I open the Title Page window, type the episode name and my details, and save. Then I shut the lid and let the machine sleep, knowing the script is exactly where I need it tomorrow.

When you reach the end, the file is already laid out to industry standards, ready to hand to a reader or a producer.

• Minor bug fixes.

• macOS 12 Monterey or later
• Intel Mac (x86 64-bit)
• English interface
• Internet connection for the initial sign-in