Screenplay file types: quick guide to save time and errors

Screenplay file types are the formats you use to write, share, review, schedule, and deliver scripts: .fdx (Final Draft) for pro exchange and imports, .fountain for portable drafting, and .pdf/PDF-A for locked reads and archival.

Choose by stage: draft in Fountain or FDX, share reads as PDF (watermark if needed), send FDX for coverage or tool parsing, use FDX for breakdown/scheduling, and deliver PDF plus an editable FDX master.

This approach prevents formatting loss, broken imports, and version sprawl—saving hours in revisions and production. Read on for the exact picks, pitfalls to avoid, and a 60-second checklist.

Read This First: Our Perspective and Your Best Alternative

You want clean collaboration, faster notes, and zero import headaches. File types decide all three. We accept standard screenplay formats and return detailed, secure coverage in minutes, so you can move from draft to decision without delays.

• We provide instant, industry-vetted script coverage that accepts Final Draft .fdx, Fountain, and PDFs, returns notes within minutes, and never trains on your work. Result: fast, private development loops that scale with your schedule. Best fit: writers and producers who need actionable feedback now. Source: Greenlight Coverage workflow.
• Our Full Context Reviewer handles line-level Q&A for full scripts regardless of origin, keeping citations tied to your pages. Result: precise fixes at the line and scene level. Best fit: deeper rewrites or team review. Source: https://glcoverage.com/2024/03/12/understanding-the-different-types-of-script-reviewers-overview-vs-full-context/
• Use this guide to choose formats by stage. Result: fewer conversion errors and smoother handoffs to scheduling. Best fit: anyone moving from draft to production inside real timelines.

Format is function. Pick the file that matches the job, not the logo.

Start With the Outcome: What You Need Your File Type To Do

File type choices should map to outcomes. That prevents formatting loss, broken imports, and confusion when stakes rise. Use formats that carry structure and metadata where it matters most.

You’ll make decisions across five outcomes. Tie each to a file that protects speed and fidelity.

The five outcomes that drive your choice

• Writing and drafting: Use editable, structured text that travels. Fountain lets you draft anywhere, then compile to .fdx or .pdf without fiddling with formatting. Proof: plain text portability and easy diffs.
• Collaboration and versioning: Use .fdx when teams expect pro exchange, since Final Draft has been the industry standard for decades. Proof: wide support and reliable imports across tools.
• Analysis and proofreading: Send a clean .pdf for read-only coverage or .fdx for structure-aware tools that parse scene numbers and character elements. Proof: element metadata improves accuracy.
• Production breakdown and scheduling: Provide .fdx so tools like StudioBinder can auto-populate scenes, numbers, and locations. Proof: faster breakdown, less data entry.
• Delivery and archival: Deliver .pdf or PDF/A for locked reads, keep an editable .fdx or .fountain master. Proof: stable layout plus future edits.

Risks to manage at each outcome

• Lost formatting during export leads to misread dialogue or broken scene numbers.
• Broken imports to scheduling when headings deviate from INT/EXT and DAY/NIGHT.
• Files unreadable by key stakeholders without licensed apps.
• Redaction or watermark needs for broader sharing.
• Time-stamped captions or transcripts confused with scripts if formats like SRT or VTT slip into the workflow.

The Mental Model: Choose by Stage, Not by App Logo

Pick files by stage. That keeps your options open across tools while protecting structure. You can draft in one app, collaborate in another, and schedule in a third if you end stages with .fdx or .pdf.

Writing stage: editable and structured wins

Choose Final Draft .fdx or Fountain .fountain. Fountain’s plain text lets you write in Google Docs or Notepad, then convert. Arc Studio and others export to pdf, fountain, and Final Draft fdx, so you can switch apps without lock-in.

• Keep dialogue, scene numbers, and headings clean to avoid conversion noise later.

Collaboration stage: set a lingua franca

Use .fdx for pro teams and .fountain for lightweight, git-friendly drafts. Lock review rounds with .pdf. Comment in the file rather than baking notes into the script pages when you need clean imports later.

• Celtx and StudioBinder accept .fdx and PDFs, reinforcing these as reliable exchange formats.

Analysis stage: match the tool to the task

For coverage and proofreading, send a clean .pdf for reading or .fdx when the tool parses structure. Our Proofreading Tool flags grammar and formatting fast and respects screenplay elements, which saves hours of manual checks.

• Structure-aware inputs produce better notes because scene and character metadata survive.

Production stage: protect downstream imports

Provide .fdx to scheduling tools. StudioBinder states each scene is auto-populated upon import, which reduces manual data entry. Keep consistent scene headings and character names to avoid duplicates during breakdown.

• Fountain supports #12# scene numbers and forced headings, which helps before you convert to .fdx.

Delivery stage: lock it and archive it

Send .pdf or PDF/A for the final read, plus an editable master .fdx in your delivery package. Watermark PDFs when sending to larger lists to protect sharing.

• This pairing keeps legal and creative needs covered.

What Are the Core Screenplay File Types and When To Use Each

You do not need every format. You need the right one for the job. Use this snapshot to cut errors and speed decisions.

Final Draft .fdx

• Best for: professional exchange, imports to scheduling, and most coverage tools.
• Pros: structured XML that preserves scene numbers, dual dialogue, and revisions. Industry standard supports wide imports, including StudioBinder and Arc Studio.
• Cons: requires licensed software to edit. Version drift can occur if collaborators export with different settings.
• Ideal use: collaboration and production handoffs where auto-population saves time.

Fountain .fountain

• Best for: drafting anywhere with portability and version control.
• Pros: human-readable plain text; easy diffs; works in simple editors. Supports inline scene numbers (#12#) and forced headings with a leading period.
• Cons: must compile to .pdf or .fdx for stakeholders and production tools.
• Ideal use: fast drafting before locking a review file.

PDF .pdf and PDF/A

• Best for: locked review, contests, investors, legal delivery.
• Pros: preserves layout; easy watermarking; universal reading; PDF/A for archival stability.
• Cons: not suited for edits; weak for scheduling unless imported via conversion.
• Ideal use: final reads and controlled sharing where layout integrity matters.

Native ecosystem files: Celtx, Arc Studio, StudioBinder, Highland, Slugline, Scrite

• Best for: drafting inside that app’s workflow.
• Pros: integrated features, hotkeys, collaboration tools. Arc Studio exports pdf, fountain, and Final Draft fdx, covering 99 percent of exchange cases.
• Cons: export to .fdx or .pdf for wider industry use to avoid feature mismatches.
• Ideal use: focused writing, then export when you share or schedule.

Adjacent text formats

• Plain text .txt for raw notes; DOCX for memos or presentation pages. Do not use as master screenplay files.
• SRT or VTT are timed text for captions, not screenplay files. Keep them out of script exchange to avoid timing and format confusion.

How To Prevent “Future Proofing” Nightmares

Future access matters. Protect your script from app lock-in and dead formats. Pair an editable master with a locked read at every milestone.

• Keep an editable master in .fdx or .fountain alongside a delivered .pdf. Result: easy updates plus a stable reader copy. Fountain’s plain text is resilient if software changes.
• Convert legacy or app-locked files to .fdx or .fountain. Result: migration paths into StudioBinder, Arc Studio, or other tools stay open.
• Maintain an export recipe: source editable plus a locked .pdf in the same delivery. Result: clean legal trail and consistent versions across the team.
• Use ecosystems that export to .fdx and .pdf, like Arc Studio. Result: reliable outputs without rebuilding your layout.

Always keep one editable format and one locked format for every milestone delivery.

Production-Proof Formatting That Survives Imports

Scheduling tools rely on standard cues. Align your script with importer expectations and you save hours during breakdown.

Scene headings that schedule cleanly

• Use INT or EXT, a specific location, and DAY or NIGHT. Avoid commas or custom time phrases that confuse parsers.
• Keep names consistent so StudioBinder can auto-populate scenes, numbers, and locations without duplicates.

Text rules that reduce misreads

• In Fountain, force headings with a leading period and scene numbers with #12#. Use leading exclamation to force Action when uppercase lines might be misread as Character.
• Break long scenes if they mix locations or times. Generate scene numbers before scheduling.

Tagging workflow that stays tidy

• StudioBinder’s drag-and-tag view speeds element tagging when source headings are clean. That reduces duplicate records and missed items.
• A quick import test after export catches misclassification before your AD builds a schedule.

Minimal Decision Tree: Pick the Right File in 5 Clicks

You need speed and certainty. Use this in your next handoff.

1. Writing alone
   • Need maximum portability and future proofing: write in .fountain. Proof: draft anywhere, then convert to .fdx or .pdf cleanly.
   • Need pro collaboration now: write in .fdx. Proof: industry standard with broad tool support.
2. Sharing for read only
   • Send .pdf with watermark if needed. Proof: layout locked, universal access.
3. Sending for coverage or AI analysis
   • Prefer .fdx for structure-aware tools; accept clean .pdf if only a read is needed. Proof: element metadata improves note accuracy.
4. Moving into scheduling
   • Provide .fdx with standardized headings and character names. Proof: StudioBinder auto-populates scenes and metadata on import.
5. Delivering final to producers, financiers, or cast
   • Deliver .pdf or PDF/A plus editable .fdx as master. Proof: stable reads with an editable source for future changes.

Fail-safe Habits That Eliminate Most File-Type Errors

You want fewer retries and faster approvals. Build habits that prevent errors before they spread. Standardize what you can, then automate the rest.

Templates and naming that never drift

• Standardize templates for margins, fonts, and scene heading formats. Result: consistent imports and uniform PDFs. Best fit: teams that share drafts across apps where small changes break layout.
• Lock naming conventions: Project_Title_DraftNumber_Date_Filetype. Result: instant recognition and fewer mistaken uploads. Best fit: producers tracking multiple drafts and deliveries.
• Keep character and location names uniform. Result: fewer duplicate records in breakdown tools. Best fit: any project moving into scheduling.

Export pairs at every milestone

• Export two files every time: one editable master (.fdx or .fountain) and one locked .pdf. Result: legal-ready read plus future-proof edits. Best fit: writers balancing notes and production prep.
• Round-trip test your exports. Import the .fdx into a scheduling or notes tool and skim. Result: caught errors before a wide send. Best fit: tight deadlines where rework costs days.

Consistency compounds. Small standards wipe out hours of cleanup later.

Quick Wins You Can Implement Today

You do not need a rebuild. You need a few precise moves that raise quality and speed.

Rapid upgrades to your current draft

• Save format presets for scene headings and dialogue. Result: one-click consistency across drafts. Best fit: writers who bounce between apps.
• Turn on cloud backups with version history. Result: instant rollback after a bad export. Best fit: teams with parallel notes rounds.
• Use PDF/A or a checksum for critical deliveries. Result: verifiable integrity for investors and legal. Best fit: finance-facing decks and packages.
• Use our Proofreading Tool for grammar and screenplay-specific flags. Result: cleaner dialogue, correct elements, faster polishing. Best fit: last-mile fixes before a table read.
• For revision cycles, use our Rewrite Feature to compare drafts and track structural changes. Result: line-by-line diffs tied to scenes. Best fit: producers managing multiple note sets.

When To Use Advanced Tools for Deep Context

As you scale from draft to deal, some problems need structured parsing. Use the right file to unlock precise analysis.

Deliver structure when the tool parses elements

• Send .fdx when a tool relies on scene numbers, headings, and character blocks. Result: higher accuracy in notes and metrics. Best fit: structural reviews and timing estimates.
• Send a clean .pdf when you only need a read. Result: universal access with locked layout. Best fit: contests, investors, and general feedback rounds.
• Our Full Context Reviewer surfaces line-level dialogue issues, structural concerns, and page-tied citations. Result: targeted fixes without manual cross-referencing. Best fit: deep rewrites with deadlines.

Structured inputs produce structured insights.

Security, Rights, and Delivery Etiquette For File Types

Protect your work while keeping the process smooth. Share the right file with the right control for the right audience.

Share with control and keep the master safe

• Prefer .pdf with watermarking for broad sharing. Result: trackable copies and fewer unauthorized forwards. Best fit: talent, reps, and investors.
• Avoid sending editable masters to large lists. Gate access with private links. Result: tighter control, fewer off-version edits. Best fit: projects in active negotiation.
• Archive with PDF/A plus an editable master (.fdx or .fountain). Result: stable long-term storage and easy future updates. Best fit: slate planning and catalog management.
• We provide secure coverage on standard files and do not train on your scripts. Result: privacy with speed. Best fit: creators who value both.

Common Pitfalls and How To Fix Them Fast

Most file issues come from headings, names, or exports. Fix those first and you’ll solve 80 percent of problems in minutes.

Fast fixes you can apply right now

• Broken imports to scheduling
  Fix: normalize scene headings to INT or EXT and DAY or NIGHT, unify location names, then export .fdx again. Result: StudioBinder auto-populates scenes and metadata correctly.
• Reviewers cannot open your file
  Fix: resend as .pdf and reserve .fdx for key collaborators. Result: no access barriers, fewer support emails.
• Formatting degraded after conversion
  Fix: round-trip test, adjust elements, regenerate the .pdf from the source app. Result: preserved layout with clean page counts.
• Dialogue or scene numbers missing
  Fix: enable auto-numbering, lock numbers before breakdown. Result: consistent references across notes and schedules.
• Fountain-specific misreads
  Fix: force headings with a leading period, force Action with a leading exclamation, and embed scene numbers with #12#. Result: accurate parsing before converting to .fdx.

The 60-Second Screenplay File Types Checklist

You are one minute from cleaner handoffs. Run this before every share.

• Before share: compile to .pdf and skim page headers, scene headings, and character consistency.
• Before production: export .fdx with standardized headings and scene numbers.
• Before archival: save a source editable plus PDF/A in a dated folder and verify both open.
• Name files with project, draft, date, and status; store in cloud with version history.
• Do a quick import test into a scheduling tool if possible to confirm auto-population.

Headings, numbers, and names must be clean before any wide send.

Conclusion: Make File Types Your Strategic Advantage

Choose files by stage and you control speed, structure, and security. You cut rework, protect layout, and keep imports clean for breakdown and scheduling.

If you want rapid, professional feedback on any standard file, upload your script to Greenlight Coverage for a full report in minutes with secure delivery and follow-up Q&A.