This is the official manual for the latest Org-mode release.
Export options can be set: globally with variables; for an individual file by
making variables buffer-local with in-buffer settings (see In-buffer settings), by setting individual keywords, or by specifying them in a
compact form with the
#+OPTIONS keyword; or for a tree by setting
properties (see Properties and Columns). Options set at a specific level
override options set at a more general level.
In-buffer settings may appear anywhere in the file, either directly or
indirectly through a file included using ‘#+SETUPFILE: filename’ syntax.
Option keyword sets tailored to a particular back-end can be inserted from
the export dispatcher (see The Export Dispatcher) using the
template command by pressing <#>. To insert keywords individually,
a good way to make sure the keyword is correct is to type
#+ and then
to use M-<TAB> for completion.
The export keywords available for every back-end, and their equivalent global variables, include:
org-export-default-language). E.g., ‘#+LANGUAGE: fr’ will tell Org to translate File (english) into Fichier (french) in the clocktable.
org-export-select-tags). The default value is
:export:. Within a subtree tagged with
:export:, you can still exclude entries with
:noexport:(see below). When headlines are selectively exported with
:export:anywhere in a file, text before the first headline is ignored.
org-export-exclude-tags). The default value is
:noexport:. Entries with the
:noexport:tag will be unconditionally excluded from the export, even if they have an
#+OPTIONS keyword is a compact2 form that
recognizes the following arguments:
headlineto only process the headline, skipping its contents (
org-export-headline-levels). Below that level, headlines are treated differently. In most back-ends, they become list items.
org-export-with-section-numbers). It can also be set to a number ‘n’, so only headlines at that level or above will be numbered.
org-export-with-planning). “Planning information” is the line containing the
CLOSED:cookies or a combination of them.
nilto remove all tasks,
todoto remove DONE tasks, or a list of keywords to keep (
When exporting only a subtree, each of the previous keywords3 can be overriden locally by special node properties. These begin with ‘EXPORT_’, followed by the name of the keyword they supplant. For example, ‘DATE’ and ‘OPTIONS’ keywords become, respectively, ‘EXPORT_DATE’ and ‘EXPORT_OPTIONS’ properties. Subtree export also supports the self-explicit ‘EXPORT_FILE_NAME’ property4.
org-export-allow-bind-keywords is non-
nil, Emacs variables
can become buffer-local during export by using the BIND keyword. Its syntax
is ‘#+BIND: variable value’. This is particularly useful for in-buffer
settings that cannot be changed using specific keywords.
 The variable
org-export-date-timestamp-format defines how this time-stamp will be
 If you want to configure
many options this way, you can use several
 With the exception of ‘SETUPFILE’.
 There is no buffer-wide equivalent for this property. The file name in this case is derived from the file associated to the buffer, if possible, or asked to the user otherwise.