Loading…
Tab stops aren't formatting. Real screenwriting tools know what a scene heading is, and they hand a producer an FDX, not a .docx.
Arqo knows scene heading from action from dialogue. You don't hit tab anymore: you hit return and it picks the right element.
FDX for Final Draft, Fountain for plain-text people, production PDF for distribution. Not a .docx pretending to be a screenplay.
Same editor, same engine, same export on phone, tablet, desktop. Docs is a web app pretending to be a writing tool.
Where did Mira last appear? Which scenes happen on the rooftop? Continuity Docs can't answer.
Select all → copy → paste into a new Arqo script. Arqo guesses elements as it lands; review the first scene to confirm.
File → Download → Plain Text from Docs. Then in Arqo: Scripts → Import → drop the .txt.
If you used Tab tab tab to fake formatting, Arqo will detect indent patterns and reformat. Verify on the first 3 scenes.
Now you can hand a producer a real FDX. Open it in Final Draft 12. It works.
You don't have to. Invite them into the script instead, named presence, live cursors, threaded comments, and suggest mode all work in Arqo today on Studio. Pro carries 2 co-writers who take turns rather than typing together, and threaded comments work on both. If a notes-giver won't sign up, export a Docs-friendly PDF or paste back into Docs; that path still works.
Not as a .docx: Arqo can't read Word files yet. Save it from Word as plain text (.txt) or a PDF, then import that. Arqo reads scene headings and character cues from the text, tab-formatted or not; check the first few scenes after import.
Yes. Inline notes, threaded comments in the margin, and suggest mode / track changes all ship today. Docs is free and uncapped for that; Arqo needs Pro ($9/mo, 2 co-writers per script) or Studio ($24/mo, 5). Free has no co-writers.
You can't. Docs has no real FDX export. That's the gap.
Two scripts on Free. Full editor. Full export. Bring your FDX, see how it lands.