Exporting and importing a project pack

Data, sync & account

Exporting and importing a project pack

Delivery export and project backup are different jobs: .quill.json, plain text (TXT), snapshots and the archive box.

Two exports, not one

Loomworld exports two different things for two different readers: a delivery export, which is the script as a document for a collaborator to read, and a project backup, which is the whole project as data you can load again. One is a finished artefact; the other is a container.

Delivery export

Word (.docx) / PDF (via the system print dialog → Save as PDF) / Plain text (.txt). Scope: the whole script or one chapter, Word/PDF can include note lines; TXT omits them.

Project backup

The complete project packed as .quill.json: draft, structure, records and bundled assets, for moving machines or restoring independently.

Where to do it

Settings → Project data holds both: “delivery export” on top (choose format and scope, then export the script) and “project backup” below (Export project downloads the JSON pack). The lobby card menu has “Export project” too, so a work can be carried out without opening it.

  • Word/PDF offer an “include comment lines” switch. Plain text always leaves out author notes.
  • PDF rides the system print panel, saved from there as PDF, so paper and headers follow print settings.
  • Images travel inside the pack. Import restores the assets that pass validation; anything damaged is named in the import summary rather than replaced with something else.

Choosing among the three delivery formats

  • Word (.docx): when actors, a director or an editor will read and annotate it in an office suite. Scene headings, speakers and dialogue levels stay recognisable in the layout.
  • PDF: when the draft is going out and must not be edited on the way. It runs through the system print panel, so paper, margins and headers are yours to set first.
  • Plain text (.txt): for publishing serial chapters, copying into another platform or reading in a text editor. A single-chapter export keeps its original chapter number.

Decide the scope deliberately: an outside reader usually needs the whole script; a chapter under review wants “Chapter N” only. For Word/PDF, check the “include comment lines” switch—the memos you wrote to yourself generally do not belong in a delivery.

Importing and restoring

In the lobby, choose “Import project” and upload a .quill.json. Import always creates a new local copy rather than overwriting a same-named project, restoring draft, structure, records and validated assets. It opens locally without depending on cloud access. With an active subscription or recorded legacy Global access, the imported project automatically starts cloud sync when opened, and its local copy is kept.

For finer recovery there are two project-internal tools: version snapshots (manual archive, restore to an earlier state) and the archive box (deleted scenes and scene settings wait there, and a restore appends them back to the end of their original chapter). Snapshots and the archive are safety nets inside a project; the pack is the cold copy across machines.

What plain text contains

Plain text keeps the original chapter numbers, chapter titles and readable body text, including speakers, dialogue, actions, narration and transitions. Use it for daily serial chapters or to copy writing into another platform.

TXT leaves out scene and scene-setting metadata, author notes, reference source and Quilldown markers. Export a complete project package separately to preserve the full structure for restoring in Loomworld.

Limits and troubleshooting

  • A pack is made for Loomworld to import again. Do not hand-edit its data structures; a hand-edited pack may refuse to load.
  • The pack carries the project’s own sessions and history, so chat history travels with the work; credit balances and task records belong to the account and do not.
  • A failed export reports its reason; follow the prompt, reopen the project and try once, rather than hammering the button.
  • The backup advice is plain: export once per finished chapter. It costs one click.