Exporting your work

Your work in Aquilla is yours to take with you. You can export your translated text in several formats, and your terminology separately.

Exporting translated text

Open a file and choose Export from the editor’s More actions menu. The dialog’s headline action is a primary Download {filename}.{ext} button: your file back in its original format (USFM, Word .docx, or PowerPoint .pptx) with your current translations injected, one click.

The Export dialog leads with your file in its original format: one click and it downloads.

For a file imported as subtitles, the dialog leads with two sections instead of one, and only one is open at a time: Audio (Audio by character or Audio by line, both .zip) and a subtitle/audio-VTT section offering the translated lines or, if the file has a linked audio track, the heard lines instead (“what was actually said, for checking the dub against the picture”). The dialog remembers which section you had open and your format choices for that project, in your browser. See Dubbing & characters for the full dubbing export workflow.

To convert to a different format instead, open the dialog’s collapsed Export to another format section and pick a format, a scope (Current file or Whole project), and a filename:

Format	Good for
USFM (.SFM)	Scripture markup for typesetting and publishing pipelines, with translations injected back into your original markup.
Word (.docx)	Translations injected back into the original Word document. Paragraph and heading structure, and the translator’s inline formatting (bold, italic, and so on), are preserved. Only available for files that were imported as .docx.
PowerPoint (.pptx)	Translations injected back into the original PowerPoint deck. Only available for files that were imported as .pptx; files imported before PowerPoint export existed need a re-import to enable it.
Plain text (.txt)	A simple, readable dump of the target text.
Markdown (.md)	Lightly formatted text.
Bilingual CSV / TSV	Source/target tables for spreadsheets.
XLIFF 1.2 (.xlf)	Round-tripping with other CAT tools.
TMX 1.4b (.tmx)	A translation memory of your source/target pairs.
SRT / WebVTT (.srt, .vtt)	Subtitle tracks with timed cues; WebVTT carries cast voice tags.
Audio by character (.zip)	One WAV per character, with every take at its own place on the timeline and silence in between. All files start at 0:00, so they drop onto a DAW already aligned with each other and with the film.
Audio by line (.zip)	One file per recording, numbered in playing order and named by character, each carrying a broadcast timestamp a DAW can place from, plus a manifest.csv listing every file with its timecode. For reviewing or re-recording individual lines.
Character sheets (corrected) (.xlsx)	Both character spreadsheets (subtitle and audio) back in their original columns, with every resolved disagreement applied. Lines still in dispute go back exactly as they came. See Dubbing & characters.
Project report (.html)	One document for the whole project: open character disagreements, what’s recorded and what isn’t, cues with no subtitle behind them, the timing correction each episode was imported with, characters spelled more than one way, and any episode that couldn’t be read.
Metadata spreadsheet (.csv)	Cast, camera angle, and cell reference: one row per cell.
SDBH XML (MARBLE) (.XML)	Localized lexicon reinjected into the original MARBLE XML edition. Only shown for projects with SDBH lexicon files, and always a whole-project export.

Cells export in order, each carrying its canonical reference label (for example GEN 1:1). USFM, Word, PowerPoint, WebVTT, and audio-by-character export one file at a time; the text and table formats can also export a whole project at once.

Two flags in the dialog are worth reading rather than fearing: formats that can’t carry everything are badged lossy, with a “What this loses:” note naming exactly what drops, and a file with outstanding validation flags shows a notice that they “won’t block your export — download now and resolve them anytime.”

Exports are a live snapshot: they always reflect the current state of the project at the moment you export, and each export is timestamped. There’s no separate “publish” step that freezes a version.

Note

By default, anyone who can read a project can export what they see; an organization owner can restrict export to higher roles. If you lack export permission, the dialog says so (“You don’t have export permission”) and links to Roles & permissions.

Exporting terminology

A project’s terminology can be exported to TBX (the standard terminology-exchange format) or CSV, so you can move your termbase into other translation tools or share it across projects.

Note

Word export needs a stored copy of your original .docx file on the server. Files imported before Word round-trip export existed may not have one. If Word isn’t offered for a file, re-import it to enable Word export. See Common issues for the same tip.