DocsScript Studio › .slima import + bulk export multiple scripts

.slima import + bulk export multiple scripts

Last updated May 29, 2026 · 5 min read

Import a script book from .slima backup, or bulk-export multiple script books at once.

Slima Script Studio "My Screenplays" page: Batch Export is a top button; .slima restore lives inside the New Screenplay dialog

Importing .slima backups

Flow is the same as Writing Studio's .slima import. Script Studio entry:

  • "+ New Screenplay" → pick "Restore Backup" → upload .slima file
  • Result: new Series (script book) with full version history preserved

Vs "Import script files"

Import script files Import .slima backup
Source format .rtf / .docx / .pdf / .fountain / .txt / .fdx .slima internal format
Result New Series + heuristic-parsed metadata New Series + full metadata + version history
Best for Migrating from another tool Restoring from a Slima backup

See: Import script to new book

Bulk export

"My Screenplays" top "Batch Export" button:

  1. Click "Batch Export" → enters selection mode
  2. Tick the script books you want on the shelf (multi-select)
  3. Click "Export Backup (N)" (N = how many you ticked) → exports the selected books as .slima backups

Batch export only outputs .slima (there's no format picker, no merged .zip, no per-book PDF / Fountain). Each book's .slima backup includes:

  • All Episodes / scenes / dialogue / description
  • Metadata (Logline / Concept / Synopsis)
  • Character Bible / storylines / locations / worldview / notes
  • Version history

To export PDF / Word / Fountain, use a single book's Deliver view.

Vs single-book export

Single-book Bulk export
Entry Card ⋯ menu "Export" or Deliver view "My Screenplays" top
Format choice PDF / Word / Fountain (Deliver view) .slima backup only
Best for Sending one to someone Whole-account archive / tool migration / account move

Use cases

1. Whole-account archive

Wrote 3 scripts, want everything archived to local disk → bulk-export .slima → save locally.
Bulk-import back later as needed.

2. Cross-account migration

Move from Account A to Account B:

  1. Bulk-export .slima from A
  2. Restore each backup in B (one at a time)
  3. Or ask support for batch import help

3. To production team

To hand scripts to a production team (PDF / Fountain), open each book's Deliver view and export there → proper formatting plus cross-tool compatibility. Batch export only produces .slima backups, which aren't meant for direct delivery.

Auto-versioning

Bulk export doesn't auto-version (it doesn't modify the original). But .slima import auto-versions the new book as its initial state (Auto-version rules).

Related

Was this helpful?