Export transcripts: DOCX, TXT, Markdown and JSON
After the review you can export your transcript in several formats: Word, text, Markdown or JSON.
Open a transcript and click Export at the bottom right of the footer bar. The Export Transcript window then opens and offers several options. You choose the file format and three extra functions.
Four export formats
First choose the export format you want. You can choose among the following formats:
- Word Document (.docx). A regular text document, for example for a file, a report or an expert opinion.
- Text Document (.txt). A simple text document without specific formatting, for example for archiving or a simple search.
- Markdown (.md). A text format with simple markup for bold and italic, for example for documentation, wikis and programs that read Markdown.
- JSON Data (.json). A machine-readable, compatible format, for example for further processing in other programs.
In every format a new paragraph starts at each speaker change. In the Word document these paragraphs are numbered in sequence, which makes later citation easier. Each section starts with the speaker name you assigned in the editor. Deleted words do not appear in the export.
DOCX
The Word document is the default and the most common format in modern word processing. It uses Arial at 11 pt. At the top you find a title paragraph and a table with file name, duration, word count and speaker count. The transcript then follows with one numbered paragraph per speaker section. Numbered speaker labels are taken over automatically. A speaker name is bold, italic or underlined when every word by that speaker has that formatting. The same rule applies in the editor. You can then continue editing the transcript in Word as usual.
TXT
The text file starts with the fixed header block “TRANSCRIPTION RESULT” with file name, duration, word count and speaker count. Under “FULL TRANSCRIPT” each speaker section is a line in the pattern [HH:MM:SS] Name: Text. Without timestamps it remains Name: Text. TXT is the leanest format and fits any tool that reads plain text.
Markdown
Markdown starts with the file name as a heading and a metadata table. Each speaker section gets a heading in the pattern Name (HH:MM:SS). Bold, italic and underline remain as **bold**, _italic_ and <u>underline</u>.
JSON
JSON always contains the full data set: file name, metadata, the speaker list with ID, raw label and assigned name, and every single word with index, start time, end time, speaker, confidence and the three formatting flags.
Three extra functions
Three special or extra functions sit under the format list. They apply equally to all four formats:
- Include your comments (off by default). Adds your comments to the file, including resolved ones.
- Include word-level timestamps (on by default). Gives every word an exact timestamp. For JSON this option has no effect, because JSON always contains the times.
- Include processing details (on by default). Records the model, settings, version and date of the transcription. Turn the option on if you need these details in the file.
The metadata header is included in every format.
memozero remembers the values from your last selection and uses them for the next export.
What is taken from the editor and what is not
Speaker colours and comment colours do not appear in the DOCX. The colours stay in the app. In the Word document the speaker name is black and only takes the formatting that every word by that speaker has, and every commented place is highlighted in a uniform yellow.
| Property | DOCX | TXT | Markdown | JSON |
|---|---|---|---|---|
| Bold, italic, underline | yes | no | yes | yes, as fields |
| Speaker colours | no | no | no | no |
| Comment colours | no, automatically yellow | no | no | no |
| Comments | real Word comments | as text | as text | as objects |
| Speaker numbering | yes | no | no | no |
Comments in the export
This is how comments appear in the four formats when Include your comments is on:
- DOCX: real Word comments with author, initials and date, anchored at the correct place in the text. The comment text does not also appear in the body.
- TXT: commented words appear in
[[double brackets]], and a summary line[Comments: …]follows at the end of the section. - Markdown: commented words are marked
==like this==, and the summary line appears in italic underneath. - JSON: the complete comment objects.
A symbol mark without text appears as a line in the pattern Mark [symbol] at "quote".