Bring your Arc Studio scripts. FDX round-trips cleanly. Fountain underneath. The same editor on every device — not a desktop app and a mobile companion.
Export FDX from Arc Studio. Open in Arqo. Scenes, dual-dialogue, revisions, locked scene numbers — preserved. Round-trip back to Arc or to Final Draft 12 if a producer needs it.
Arc Studio is desktop-first with a mobile companion. Arqo is the same editor on iOS, Android, Windows, and the web. Phone is not a viewer — it is the editor.
Character index, location index, the through-line — surfaced when you ask, hidden when you don't. Iv does not autocomplete your dialogue.
Two scripts, full editor, full FDX export, no nag. Pro at $9.99 launch (was $11) if you grow into it.
In Arc Studio: File → Export → Final Draft (.fdx). Pick "Final Draft 12" format if asked.
Scripts → Import → drop the .fdx. Done. Locked scene numbers, dual dialogue, revisions, all there.
Spot-check the first three scenes — element types, character names, scene numbers, revision marks. Export FDX back if you need it.
Sign in on iOS or Android. Same editor. Same script. No "mobile mode" with half the features.
Not directly. Arc's beat board is their flagship feature and we don't replicate it 1:1. Beat metadata in your FDX preserves as Fountain notes; the visual beat-board surface is on the roadmap, not in v1.
Yes. Locked scene numbers, A-page numbering, dual dialogue, and revision marks are verified by golden round-trip tests against FD12 — the format Arc Studio also targets.
Yes. Round-trip the FDX. Outline in Arc, write in Arqo, hand a producer FDX from either side.
Not yet. Real-time collab ships Q4 2026 with the Max tier. Until then: hand off via FDX or PDF round-trip.
Arc's assistant is generation-leaning. Arqo's memory layer is the opposite — it answers questions about your script (where did Mira last appear, which scenes happen on the rooftop) without writing dialogue for you. Different tool, different bet.
Two scripts on Free. Full editor. Full export. Bring your FDX, see how it lands.