A Compiling Philosophy

The easiest way to think about compiling your project is that Scrivener give you multiple preset outputs for different ways to export your project. You can export it as a PDF, a simple text file, several different Microsoft Word formats, screenplays and various e-book formats. You can also use multi-markdown as well. These preset compile settings cannot be edited, however they can be duplicated. A duplicated copy of the default Compile Format settings can be edited and adjusted to fit your needs.

This series will review some of the same information in several different ways. By doing this, I hope this complex topic will become easier to understand. If one of my explanations does not make sense, then looking another way may help you understand.

The Compile command is probably the safest place in all of Scrivener to experiment with. It can’t and doesn’t change the underlying project, and you can’t change the Compile Formats that come with Scrivener only duplicate and then edit them.

My strong suggestion is to try one of the default templates for a sample output in any of the different formats you are thinking of outputting to. Look at the results to see if they already meet your needs. If the result is way off of what you want, then try a different one of the default templates. First check the Section Types and the Include in Compile status of all the documents in the Manuscript/Draft. The easiest way to do this is in the Outliner view and check the Include in Compile and Section Type columns. It should like the image below.

Now check the third panel to make sure you have chosen the Manuscript to Compile and NOT something else.

#1. This is what you are compiling. Normally you are choosing the Draft/Manuscript folder for your novel. (A). However, you can choose the Current Selection (B) which will be the currently highlighted files in the Binder. Or you could choose (C) which is a Collection. This can be useful if you set up a test Compile collection. (see below)

#2. This is the Filter Icon and using this will further refine what documents are included to be compiled. There are various settings here which will be discussed later in this series.

Don’t leave setting up the compiler to the last minute, close to a deadline. Use Collections to create a mini version of your book elements to test the Compile Formats ahead of your deadline to work out the kinks. Include one or two chapters, your Front and Back Matter, any cover art, and an Acts (or Parts) page if have one. Having a small slice of the future book to practice on allows you to fine tune the appearance of the Compile output quickly and make adjustments as you go.

For example, for e-book formatting you should include a cover image, front matter, back matter and at least an Act, 1-2 Chapters, and several scenes with text. This will give you all the main elements you would find with an e-book. Trying a sample Compile will allow you to customize how your book outputs. The key point to remember with e-books is that each reader will view your file differently and may use different fonts as well so don’t worry so much about the perfect font. With e-books, the other element’s appearance, such as Chapters with Scenes with or without titles, is more important.

For more choices and freedom about how you format your output other programs are available as well. Basic formatting for sharing projects for editing and beta reading are all well within Scrivener's capabilities. The basic settings for e-book should function reasonably well also.

These compile formats can be saved for just one project or be used systemwide. Project Formats are specific to one project. My Formats are systemwide. Whenever you are finished saving a format, you have the option to save it either as a Project Format or as a My Format.

You should export these custom Compile Formats and save them in a folder on your computer. Over time, Compile Formats can degenerate and begin to have errors. Keeping a pristine copy to use again and again will be helpful.

Pro Tip- As you are experimenting with a Compile Format, consider naming the versions, in case you decide you actually like an earlier version. By having the versions numbered or lettered, you can go back and select a version that you want rather than remembering what steps/settings you used to create it. When you are done, you can delete the version copies.

Essentially all settings not related to a specific Output type (word, pdf, ebook), are hidden when you switch file types. Any settings that would conflict or are not available for your current output type will not be shown in the Compile Format Designer, which is for editing aspects of the current format you are using. So, for example, the CSS pane will vanish when you switch to a PDF output format, but available if you switch formats. But if you change the font size for your Chapter Heading layout in one output, this will then change settings across various outputs. Settings which are universal across all Compile outputs will change if modified for a specific format. In most cases that is considered desirable. You wouldn’t want to have to redo everything if you switched from RTF to ODT for example.

When you are creating a project in Scrivener, you are creating CONTENT. You can give it (while writing) attributes that make it easier to create, such as comfortable fonts for you, spacing, notes, tags, etc. Those are for YOU (only) while you CREATE.

But sharing with others is a whole separate thing, and Scrivener knows it. That's why Compiling tends to be rather complicated. Here are some examples of different targets for compiling:

A submission to an editor or publisher using their required formatting rules

Putting the manuscript into the format required for Kindle Direct Publishing

Submitting just a section of your work to a critique group

Submitting the required first chapter to a writing contest using the required formatting