The table below shows all the formats supported by Scrivener, with commentary on their usage.
For most word processor-based workflows, including Microsoft Word, RTF is the best option. Nearly every word processor provides solid RTF import and export capabilities, and some use RTF as their native file format. The one major exception to this is Pages, which has limited RTF support. (Note that if you double-click on RTF files in the Finder, they will most likely be opened in TextEdit by default, which doesn’t support all RTF features—to open an RTF file in your desired word processor, you should open the word processor first and use File ▸ Open.)
Format | Extension | Description |
---|---|---|
General Purpose Formats | ||
Printing/PDF | N/A | Use to print the compiled draft, or to save it as a PDF using the Print dialogue’s PDF features. |
Rich Text | .rtf | General purpose rich text format supporting multiple fonts, images, tables, bullet points, footnotes and comments. Almost always the best option when exporting for use in a general-purpose word processor, including Microsoft Word. |
Rich Text with Attachments | .rtfd | Apple’s proprietary extended RTF format. Useful mainly for exporting to other Apple Cocoa applications such as TextEdit, especially if image support is needed. Incompatible with most word processors and all other computing platforms. |
Plain Text | .txt | UTF-8 (Unicode) plain-text file. Plain text contains no formatting but can be opened almost anywhere, on all platforms. |
Microsoft Word | .doc | Simple Word format exporter. It is usually better to export using RTF format—see the note below on exporting to Word .doc format. |
Microsoft Word XML | .docx | Simple Word DOCX exporter. This uses Apple’s default exporter, which loses much of the formatting, including indents and line spacing. It is always better to use RTF if possible. |
Open Office | .odt | Simple ODT exporter. This uses Apple’s default exporter, which loses much of the formatting, including indents and line spacing. It is always better to use RTF if possible. |
Scriptwriting Formats | ||
Final Draft 8 | .fdx | For transferring your script to Final Draft, this is the best option unless you have an older version of Final Draft than version 8. Maintains synopses (as scene summaries), scene titles and custom script element formatting. |
Final Draft 5–7 Converter | .fcf | Use the FCF converter when working with an older copy of Final Draft. Supports only basic screenplay formatting. |
E-book & Web Support | ||
ePub eBook | .epub | Generate feature-rich eBooks for use in portable reading devices that support the ePub format, such as the Sony Reader or iPad (ePub files can be dragged into the iTunes Library to import them into iBooks). |
HTML | .html | Creates a single HTML file suitable for web-publishing. |
Web Archives | .webarchive | Much like HTML, but conveniently packages exported image files into a single bundle, using Apple’s webarchive format, which can be opened by Safari (including the Windows version) and various Mac OS X applications. Not compatible with most other browsers. |
MultiMarkdown Post-processing | ||
MultiMarkdown | .md | Export a plain-text MultiMarkdown file, useful for archiving, or further custom post-processing. |
MultiMarkdown -> LaTeX | .tex | Exports a LaTeX format file with full MultiMarkdown parsing. Note that if you are intending to export a LaTeX file that has been handwritten in Scrivener (without MMD), you should use the plain-text exporter, above. |
MultiMarkdown -> RTF | .rtf | Export an HTML-derived RTF file with partial MultiMarkdown support. Note that the RTF files generated in this fashion will be limited in features and formatting support in the same way as HTML, and is not equivalent to Scrivener’s standard RTF exporter in the word processor compatibility tables. |
MultiMarkdown -> HTML | .html | Generates a W3C compliant XHTML file, suitable for web-publishing or further XML post-processing. |
The following table shows which file format constitutes the best option when exporting for use with several popular applications, and which features are supported by those programs.
Supported Features | ||||||||
---|---|---|---|---|---|---|---|---|
Application | Best Format | Comments | Footnotes | Lists | Tables | Images | Headers/Footers | ToC |
Microsoft Word | RTF | X | X | X | X | X | X | X |
Nisus Writer Pro | RTF | X | X | X | X | X | X | X |
OpenOffice.org | RTF | X | X | X | X | X | ||
RedleX Mellel | RTF | X | X | X | X | X | X | |
Papyrus | RTF | X1 | X | X | X | |||
Apple Pages | RTFD | X | X | X | ||||
TextEdit (Cocoa Misc.) | RTFD | X | X | X |
Explanation of features and how compatibility is determined:
Not included in the table are basic formatting features. Most word processors support these with only a few exceptions, as listed below (if the word processor is listed next to the formatting feature, it does not support it):
Note on Exporting to Word .doc Format: Because RTF is preferred, the Word .doc exporter uses RTF internally, meaning that .doc files exported from Scrivener are essentially just renamed RTF files which will open in Word by default. This is useful when you need to send .doc files to someone who is not aware that Word fully supports RTF. If you require native .doc support, then you should adjust the application preferences in the “Import & Export” tab for “Microsoft .doc export”. This will force the export process to use Apple’s more basic exporter, which will produce a native .doc file, but at the expense of dropped features and altered formatting (in particular, indents and line-spacing will be lost). Only use this option if you absolutely need native .doc files and RTF does not work with the target word processor.
Pages is a unique word processor in that it has limited RTF support. Compounding this, its proprietary .pages format is unpublished, and has no officially supported mechanisms for allowing applications to read and save to the format. However there is one loophole that can be used to get information from Scrivener to Pages with minimal loss of formatting: its support of Microsoft Word’s .doc and .docx formats.
Unfortunately, as noted in the previous section, Scrivener does not actually produce native .doc files as this is a proprietary format for which only basic exporters are available to most Mac programs, and for the same reasons its .docx export is very basic and involves the loss of certain formatting. So while Scrivener allows access to these basic exporters, they will not suffice for what most people need.
This means that if you use the RTF format for exporting to Pages, formatting will be lost because Pages does not fully support RTF; but if you use .doc or .docx, formatting will be lost because Scrivener only has basic exporters for these formats.
The preferred method for getting data from Scrivener to Pages thus takes three steps:
It can, however, be beneficial to give plain RTF a try first. While Pages doesn’t fully support the RTF specification, for many authors this won’t be a problem in practice. With the exception of page breaks, the features it omits are features not often used in works of fiction, such as images and footnotes. Another option, as recommended above, is to use RTFD. This will give you images, but no true footnotes (which will be flattened into pure text endnotes, and so will require further formatting in Pages if you wish to convert them into real footnotes).
The following table shows which file format constitutes the best option when exporting for use with several popular scriptwriting applications.
Application | Best Format | Notes |
---|---|---|
Final Draft 8 | FDX | Supports comments and footnotes (as script notes), synopses (which become scene summaries), titles, dual dialogue (dialogue marked using “Preserve Style” in Scrivener becomes dual dialogue in Final Draft), revision marks, custom element formats. |
Final Draft 5–7 | FCF | FDX is always better, so only use this if you don’t have access to Final Draft 8. FCF is essentially a plain text format and so any formatting such as bold or italics will be lost. Also note that it only supports the basic script elements—Scene Heading, Action, Character, Dialogue, Parenthetical and Transition. See below for important tips which will help avoid strange characters appearing in the export. |
Movie Magic Screenwriter | TXT | See below for important tips which will help avoid strange characters appearing in the export, and ensure proper element conversion. |
CeltX | TXT | As for Movie Magic Screenwriter. |
Montage | RTF or TXT | Montage will do a decent job of importing script files saved in either the RTF or TXT formats (if you use TXT, follow the same rules as for Movie Magic Screenwriter and CeltX). |
The guidelines below should be followed when exporting to the FCF or TXT formats for use with scriptwriting programs:
To avoid strange characters appearing in the export, the following preferences should be enabled in the Text Options compile pane:
In the Separators pane:
When using the TXT format, along with the above settings, “Convert indents and paragraph spacing to plain text” should be enabled when exporting to scriptwriting programs such as Movie Magic Screenwriter and CeltX. This ensures that they will recognise the elements correctly, as these programs read the whitespace and use it to convert the text to the relevant script types.
Endnotes are not recognised, and will be lost with Papyrus. Always use footnotes. ↩