Exporting scripts and projects
Arthoff can export scripts and projects in multiple formats for sharing outside the app, printing, archiving, and importing into other systems.
Arthoff can export scripts and projects in multiple formats for sharing outside the app, printing, archiving, and importing into other systems.
Export formats
| Format | Contents | Use case |
|---|---|---|
| Printable script with cue and section numbering, descriptions, and optionally comments. | Printing for the team, operators, and actors; presenting outside the app. | |
| CSV | A table with cue fields such as ID, type, content, section, volume, and DMX channels. | Data analysis, Excel import, and reporting. |
| JSON | Full script structure with metadata, sections, cues, authors, tags, and fields. | Backups, integrations, automation pipelines, and versioning. |
| Plain Text | Dialogue and stage directions without technical metadata or cue numbering. | Quick review, copying into other documents, or sharing with writers. |
Exporting a script
Open the script you want to export.
In the upper-right corner, click Export or open … → Export.
Choose PDF, CSV, JSON, or Plain Text.
Configure optional settings for the selected format:
- PDF: include comments and optionally restart cue numbering in each section.
- CSV: include sections and optionally export only fields currently visible in the editor.
- JSON: include version history and optionally device metadata for devices assigned to cues.
Click Export. The file is downloaded locally or opened in a preview, depending on the browser.
Exporting an entire project
Open Project settings (⚙️ in the left sidebar).
Select Project export.
Choose PDF or JSON. CSV does not currently export an entire project as one file.
Click Generate export. The result can include:
- all scripts and their structure,
- members and roles,
- devices and their parameters,
- change history, when selected.
The generated file is downloaded as arthoff-export-<project>.json or .pdf.
Importing an export
JSON import
In the project view, choose Import script or Import project, depending on the file.
Select a JSON file previously exported from Arthoff.
Choose whether to create a new script/project or replace an existing one. Replacing data overwrites the current object, so use it carefully.
After import, verify that sections, cues, and metadata were loaded correctly.
CSV import
CSV import is currently limited to a cue list with content and basic properties. Use it to bring data from Excel or another system into Arthoff, then complete advanced fields manually.
Common scenarios
Scenario A: Printout before a rehearsal
Open the director’s script.
Export to PDF with Include comments and Restart cue numbering in each section enabled.
Download and print the file or distribute the PDF to the team.
Actors and operators can follow the event using a physical copy during rehearsal.
Scenario B: Data analysis after an event
After the event, export the script as JSON with version history included.
Analyze the file in tools such as Python, R, or Power BI to inspect cue counts, durations, and change frequency.
You can also export CSV with sections included to prepare client-facing reports.
Scenario C: Share a clean script with a new team
Export the completed production as Plain Text to provide only dialogue and stage directions.
Share it as a clean source text without cue numbers and technical details.
Scenario D: Backup before a major change
Before restructuring sections or making another major change, export JSON with version history.
Store the file on external storage or in a cloud service such as OneDrive or Dropbox.
If necessary, restore the earlier state by importing the backup.
Limitations and notes
- PDF is static. Changes made in Arthoff after export do not update an already downloaded PDF.
- JSON preserves the full working structure, although some internal or diagnostic fields may be omitted for security.
- CSV contains exportable editor fields rather than internal system-only fields.
- Export respects Arthoff privacy rules. Sensitive information such as device credentials or private account identifiers should not be included unless explicitly supported and intentionally selected.
Frequently asked questions
Can I export a script while a live event is running?
Yes. The export captures the state at the moment it is generated and does not include changes made afterwards.
Does a JSON export contain device information and current state?
If devices are assigned to cues, JSON can include connection information such as protocol, IP address, and device identifier. Runtime DMX or MIDI values are only a snapshot of the exported state.
Can I re-import a CSV and preserve every cue property?
No. CSV import covers basic fields such as cue content, type, and section. Advanced properties such as DMX values, device assignments, and comments require manual completion or a JSON-based workflow.
Is there a PDF export size limit?
There is no fixed limit, but very large scripts can produce large PDF files. For data-heavy projects, use CSV or JSON for analysis and export selected sections or summaries for printing.