Import Your Script
Without Retyping It.

I have moved scripts between three or four apps over the years. The worst moves were the ones where I had to fix every scene heading by hand. Building import for ActOne, we wanted the opposite: you pick a file, it lands in the editor looking right, and you keep writing.

What ActOne imports

• Final Draft .fdx — full script structure, characters, dialogue blocks, scene numbers.
• Fade In .fadein — same, with care for parenthetical and dialogue flow.
• Fountain .fountain and plain .txt — already plain text, just opened as a new project.

If you have older files in PDF or other formats, export them to FDX or Fountain first in their original app, then import.

How to import in two clicks

From the Welcome Screen

1. Open ActOne. On the Welcome Screen, choose Import Script.
2. Pick your file. Choose FDX, Fade In, Fountain or TXT.
3. ActOne converts the script and opens it as a new project. You will see a save prompt for the new .actone file. Save where you like.

From the editor

1. Press Ctrl+K and type Import Screenplay.
2. Choose the file. ActOne does the conversion and opens it alongside your other scripts in the Project Pane.

That is all. No extra settings, no plugins.

What conversion does for you

ActOne does not just copy text. It adds Fountain markers so the script is cleanly structured:

• Scene headings get a leading . so they are recognized even if they are short or unusual.
• Character cues get @ so names like “DAD” are not confused with action.
• Transitions get > so something like CUT TO: sits where it should.
• Action stays action. Your original wording is not changed, only the small markers that make navigation and export reliable.

The result is that outline navigation, snapshots and PDF export all work right away. Search in the Command Palette will also find your scenes by title.

After import, check these three things

You usually do not need to fix much, but a quick pass helps.

1. Scene numbers. If your FDX had scene numbers, they carry over. You can renumber from the Command Palette if needed.
2. Parentheticals. We kept dialogue and parentheticals together so an actor direction does not get split from its line. Scan one conversation to confirm.
3. Title page. Title page fields from FDX come in, but give them a look. Fountain title pages are simple key value lines.

Title: The Night Shift
Author: You

INT. DINER - NIGHT

MARA wipes the counter. The bell rings.

Your original file stays where it was. ActOne works on a new Fountain copy, so you can always go back.

Why Fountain after import?

After the import, your script is Fountain. That means it is plain text. You can back it up with normal file tools, open it in FountTUI in the terminal, or share it without worrying about version mismatch. When you need to send to production, export to PDF or FDX from ActOne. The Fountain source stays simple.

Troubleshooting

My dialogue looks off

It is rare now, but if a block of dialogue lost a blank line, use the Fix Formatting command. It tightens spacing without changing words.

Some characters are flagged as spelling errors

Add them to the custom dictionary. Character names are usually excluded from spellcheck, but a very unusual name might need one click to remember.

Can I batch import many files?

Import one at a time for now. Each import creates its own project file you can keep.

FAQ

Can ActOne open Final Draft FDX files?

Yes. Use Import Screenplay and choose the FDX file. ActOne converts it to Fountain and opens it as a new .actone project.

Does it support Fade In files?

Yes, including .fadein. Dialogue contiguity is preserved so the script reads correctly.

Will my formatting be lost?

No. The script content stays the same. ActOne adds small Fountain markers so structure is preserved for outline and export.