neulab/tldr huggingface dataset:
• dzslides (DZSlides HTML5 + JavaScript slide show),
• revealjs (reveal.js HTML5 + JavaScript slide show)
• s5 (S5 HTML and JavaScript slide show)
• tei (TEI Simple)
• xwiki (XWiki markup)
• zimwiki (ZimWiki markup)
• the path of a custom Lua writer, see Custom writers below
Note that odt, docx, epub, and pdf output will not be directed to stdout unless forced with -o -.
Extensions can be individually enabled or disabled by appending +EXTENSION or -EXTENSION to the format name.  See Extensions below, for a list of extensions and their names.  See --list- output-formats and --list-extensions, below.
-o FILE, --output=FILE Write output to FILE instead of stdout.  If FILE is -, output will go to stdout, even if a non-textual format (docx, odt, epub2, epub3) is specified.
--data-dir=DIRECTORY Specify the user data directory to search for pandoc data files. If this option is not specified, the default user data directory will be used.  On *nix and macOS systems this will be the pandoc subdirectory of the XDG data directory (by default, $HOME/.local/share, overridable by setting the XDG_DATA_HOME environment variable).  If that directory does not exist and $HOME/.pandoc exists, it will be used (for backwards compatibility).  On Windows the default user data directory is C:\Users\USERNAME\AppData\Roaming\pandoc.  You can find the default user data directory on your system by looking at the output of pandoc --version.  Data files placed in this directory (for example, reference.odt, reference.docx, epub.css, templates) will override pandoc’s normal defaults.
-d FILE, --defaults=FILE Specify a set of default option settings.  FILE is a YAML file whose fields correspond to command-line option settings.  All options for document conversion, including input and output files, can be set using a defaults file.  The file will be searched for first in the working directory, and then in the defaults subdirectory of the user data directory (see --data-dir).  The .yaml extension may be omitted.  See the section Default files for more information on the file format.  Settings from the defaults file may be overridden or extended by subsequent options on the command line.
--bash-completion Generate a bash completion script.  To enable bash completion with pandoc, add this to your .bashrc:
eval "$(pandoc --bash-completion)"
--verbose Give verbose debugging output.
--quiet Suppress warning messages.
--fail-if-warnings Exit with error status if there are any warnings.
--log=FILE Write log messages in machine-readable JSON format to FILE.  All messages above DEBUG level will be written, regardless of verbosity settings (--verbose, --quiet).
--list-input-formats List supported input formats, one per line.
--list-output-formats List supported output formats, one per line.
--list-extensions[=FORMAT] List supported extensions for FORMAT, one per line, preceded by a + or - indicating whether it is enabled by default in FORMAT.  If FORMAT is not specified, defaults for pandoc’s Markdown are given.
--list-highlight-languages List supported languages for syntax highlighting, one per line.
--list-highlight-styles List supported styles for syntax highlighting, one per line.  See --highlight-style.
-v, --version Print version.
-h, --help Show usage message.
Reader options --shift-heading-level-by=NUMBER Shift heading levels by a positive or negative integer.  For example, with --shift-heading-level-by=-1, level 2 headings become level 1 headings, and level 3 headings become level 2 headings. Headings cannot have a level less than 1, so a heading that would be shifted below level 1 becomes a regular paragraph.  Exception: with a shift of -N, a level-N heading at the beginning of the document replaces the metadata title.  --shift-heading-level-by=-1 is a good choice when converting HTML or Markdown documents that use an initial level-1 heading for the document title and level-2+ headings for sections.  --shift-heading-level-by=1 may be a good choice for converting Markdown documents that use level-1 headings for sections to HTML, since pandoc uses a level-1 heading to render the document title.
--base-header-level=NUMBER Deprecated. Use --shift-heading-level-by=X instead, where X = NUMBER - 1. Specify the base level for headings (defaults to 1).
--strip-empty-paragraphs Deprecated. Use the +empty_paragraphs extension instead. Ignore paragraphs with no content.  This option is useful for converting word processing documents where users have used empty paragraphs to create inter-paragraph space.
--indented-code-classes=CLASSES Specify classes to use for indented code blocks–for example, perl,numberLines or haskell.  Multiple classes may be separated by spaces or commas.
--default-image-extension=EXTENSION Specify a default extension to use when image paths/URLs have no extension.  This allows you to use the same source for formats that require different kinds of images.  Currently this option only affects the Markdown and LaTeX readers.
--file-scope Parse each file individually before combining for multifile documents.  This will allow footnotes in different files with the same identifiers to work as expected.  If this option is set, footnotes and links will not work across files.  Reading binary files (docx, odt, epub) implies --file-scope.
-F PROGRAM, --filter=PROGRAM Specify an executable to be used as a filter transforming the pandoc AST after the input is parsed and before the output is written.  The executable should read JSON from stdin and write JSON to stdout.  The JSON must be formatted like pandoc’s own JSON input and output.  The name of the output format will be passed to the filter as the first argument.  Hence,
pandoc --filter ./caps.py -t latex
pandoc -t json | ./caps.py latex | pandoc -f json -t latex
The latter form may be useful for debugging filters.
Filters may be written in any language.  Text.Pandoc.JSON exports toJSONFilter to facilitate writing filters in Haskell.  Those who would prefer to write filters in python can use the module pandocfilters, installable from PyPI.  There are also pandoc filter libraries in PHP, perl, and JavaScript/node.js.
In order of preference, pandoc will look for filters in
1. a specified full or relative path (executable or non- executable)
2. $DATADIR/filters (executable or non-executable) where $DATADIR is the user data directory (see --data-dir, above).
3. $PATH (executable only)
Filters, Lua-filters, and citeproc processing are applied in the order specified on the command line.
-L SCRIPT, --lua-filter=SCRIPT Transform the document in a similar fashion as JSON filters (see --filter), but use pandoc’s built-in Lua filtering system.  The given Lua script is expected to return a list of Lua filters which will be applied in order.  Each Lua filter must contain element- transforming functions indexed by the name of the AST element on which the filter function should be applied.
The pandoc Lua module provides helper functions for element creation.  It is always loaded into the script’s Lua environment.
See the Lua filters documentation for further details.
In order of preference, pandoc will look for Lua filters in
1. a specified full or relative path
2. $DATADIR/filters where $DATADIR is the user data directory (see --data-dir, above).
Filters, Lua filters, and citeproc processing are applied in the order specified on the command line.
-M KEY[=VAL], --metadata=KEY[:VAL] Set the metadata field KEY to the value VAL.  A value specified on the command line overrides a value specified in the document using YAML metadata blocks.  Values will be parsed as YAML boolean or string values.  If no value is specified, the value will be treated as Boolean true.  Like --variable, --metadata causes template variables to be set.  But unlike --variable, --metadata affects the metadata of the underlying document (which is accessible from filters and may be printed in some output formats) and metadata values will be escaped when inserted into the template.
--metadata-file=FILE Read metadata from the supplied YAML (or JSON) file.  This option can be used with every input format, but string scalars in the YAML file will always be parsed as Markdown.  Generally, the input will be handled the same as in YAML metadata blocks.  This option can be used repeatedly to include multiple metadata files; values in files specified later on the command line will be preferred over those specified in earlier files.  Metadata values specified inside the document, or by using -M, overwrite values specified with this option.
-p, --preserve-tabs Preserve tabs instead of converting them to spaces.  (By default, pandoc converts tabs to spaces before parsing its input.)  Note that this will only affect tabs in literal code spans and code blocks.  Tabs in regular text are always treated as spaces.
--tab-stop=NUMBER Specify the number of spaces per tab (default is 4).
--track-changes=accept|reject|all Specifies what to do with insertions, deletions, and comments produced by the MS Word “Track Changes” feature.  accept (the default) processes all the insertions and deletions.  reject ignores them.  Both accept and reject ignore comments.  all includes all insertions, deletions, and comments, wrapped in spans with insertion, deletion, comment-start, and comment-end classes, respectively.  The author and time of change is included.  all is useful for scripting: only accepting changes from a certain reviewer, say, or before a certain date.  If a paragraph is inserted or deleted, track-changes=all produces a span with the class paragraph-insertion/paragraph-deletion before the affected paragraph break.  This option only affects the docx reader.
--extract-media=DIR Extract images and other media contained in or linked from the source document to the path DIR, creating it if necessary, and adjust the images references in the document so they point to the extracted files.  Media are downloaded, read from the file system, or extracted from a binary container (e.g. docx), as needed.  The original file paths are used if they are relative paths not containing ...  Otherwise filenames are constructed from the SHA1 hash of the contents.
--abbreviations=FILE Specifies a custom abbreviations file, with abbreviations one to a line.  If this option is not specified, pandoc will read the data file abbreviations from the user data directory or fall back on a system default.  To see the system default, use pandoc --print- default-data-file=abbreviations.  The only use pandoc makes of this list is in the Markdown reader.  Strings found in this list will be followed by a nonbreaking space, and the period will not produce sentence-ending space in formats like LaTeX.  The strings may not contain spaces.
General writer options -s, --standalone Produce output with an appropriate header and footer (e.g. a standalone HTML, LaTeX, TEI, or RTF file, not a fragment).  This option is set automatically for pdf, epub, epub3, fb2, docx, and odt output.  For native output, this option causes metadata to be included; otherwise, metadata is suppressed.
--template=FILE|URL Use the specified file as a custom template for the generated document.  Implies --standalone.  See Templates, below, for a description of template syntax.  If no extension is specified, an extension corresponding to the writer will be added, so that --template=special looks for special.html for HTML output.  If the template is not found, pandoc will search for it in the templates subdirectory of the user data directory (see --data-dir).  If this option is not used, a default template appropriate for the output format will be used (see -D/--print-default-template).
-V KEY[=VAL], --variable=KEY[:VAL] Set the template variable KEY to the value VAL when rendering the document in standalone mode.  If no VAL is specified, the key will be given the value true.
-D FORMAT, --print-default-template=FORMAT Print the system default template for an output FORMAT.  (See -t for a list of possible FORMATs.) Templates in the user data directory are ignored.  This option may be used with -o/--output to redirect output to a file, but -o/--output must come before --print-default-template on the command line.
Note that some of the default templates use partials, for example styles.html.  To print the partials, use --print-default-data- file: for example, --print-default-data- file=templates/styles.html.
--print-default-data-file=FILE Print a system default data file.  Files in the user data directory are ignored.  This option may be used with -o/--output to redirect output to a file, but -o/--output must come before --print-default-data-file on the command line.
--eol=crlf|lf|native Manually specify line endings: crlf (Windows), lf (macOS/Linux/UNIX), or native (line endings appropriate to the OS on which pandoc is being run).  The default is native.
--dpi=NUMBER Specify the default dpi (dots per inch) value for conversion from pixels to inch/centimeters and vice versa.  (Technically, the correct term would be ppi: pixels per inch.) The default is 96dpi. When images contain information about dpi internally, the encoded value is used instead of the default specified by this option.
--wrap=auto|none|preserve Determine how text is wrapped in the output (the source code, not the rendered version).  With auto (the default), pandoc will attempt to wrap lines to the column width specified by --columns (default 72).  With none, pandoc will not wrap lines at all.  With preserve, pandoc will attempt to preserve the wrapping from the source document (that is, where there are nonsemantic newlines in the source, there will be nonsemantic newlines in the output as well).  Automatic wrapping does not currently work in HTML output. In ipynb output, this option affects wrapping of the contents of markdown cells.
--columns=NUMBER Specify length of lines in characters.  This affects text wrapping in the generated source code (see --wrap).  It also affects calculation of column widths for plain text tables (see Tables below).
--toc, --table-of-contents Include an automatically generated table of contents (or, in the case of latex, context, docx, odt, opendocument, rst, or ms, an instruction to create one) in the output document.  This option has no effect unless -s/--standalone is used, and it has no effect on man, docbook4, docbook5, or jats output.
Note that if you are producing a PDF via ms, the table of contents will appear at the beginning of the document, before the title. If you would prefer it to be at the end of the document, use the option --pdf-engine-opt=--no-toc-relocation.
--toc-depth=NUMBER Specify the number of section levels to include in the table of contents.  The default is 3 (which means that level-1, 2, and 3 headings will be listed in the contents).
--strip-comments Strip out HTML comments in the Markdown or Textile source, rather than passing them on to Markdown, Textile or HTML output as raw HTML.  This does not apply to HTML comments inside raw HTML blocks when the markdown_in_html_blocks extension is not set.
--no-highlight Disables syntax highlighting for code blocks and inlines, even when a language attribute is given.
--highlight-style=STYLE|FILE Specifies the coloring style to be used in highlighted source code.  Options are pygments (the default), kate, monochrome, breezeDark, espresso, zenburn, haddock, and tango.  For more information on syntax highlighting in pandoc, see Syntax highlighting, below.  See also --list-highlight-styles.
Instead of a STYLE name, a JSON file with extension .theme may be supplied.  This will be parsed as a KDE syntax highlighting theme and (if valid) used as the highlighting style.
To generate the JSON version of an existing style, use --print- highlight-style.
--print-highlight-style=STYLE|FILE Prints a JSON version of a highlighting style, which can be modified, saved with a .theme extension, and used with --highlight-style.  This option may be used with -o/--output to redirect output to a file, but -o/--output must come before --print-highlight-style on the command line.
--syntax-definition=FILE Instructs pandoc to load a KDE XML syntax definition file, which will be used for syntax highlighting of appropriately marked code blocks.  This can be used to add support for new languages or to use altered syntax definitions for existing languages.  This option may be repeated to add multiple syntax definitions.
-H FILE, --include-in-header=FILE|URL Include contents of FILE, verbatim, at the end of the header. This can be used, for example, to include special CSS or JavaScript in HTML documents.  This option can be used repeatedly to include multiple files in the header.  They will be included in the order specified.  Implies --standalone.
-B FILE, --include-before-body=FILE|URL Include contents of FILE, verbatim, at the beginning of the document body (e.g. after the <body> tag in HTML, or the \begin{document} command in LaTeX).  This can be used to include navigation bars or banners in HTML documents.  This option can be used repeatedly to include multiple files.  They will be included in the order specified.  Implies --standalone.
-A FILE, --include-after-body=FILE|URL Include contents of FILE, verbatim, at the end of the document body (before the </body> tag in HTML, or the \end{document} command in LaTeX).  This option can be used repeatedly to include multiple files.  They will be included in the order specified. Implies --standalone.
--resource-path=SEARCHPATH List of paths to search for images and other resources.  The paths should be separated by : on Linux, UNIX, and macOS systems, and by ; on Windows.  If --resource-path is not specified, the default resource path is the working directory.  Note that, if --resource- path is specified, the working directory must be explicitly listed or it will not be searched.  For example: --resource-path=.:test will search the working directory and the test subdirectory, in that order.  This option can be used repeatedly.  Search path components that come later on the command line will be searched before those that come earlier, so --resource-path foo:bar --resource-path baz:bim is equivalent to --resource-path baz:bim:foo:bar.
--request-header=NAME:VAL Set the request header NAME to the value VAL when making HTTP requests (for example, when a URL is given on the command line, or when resources used in a document must be downloaded).  If you’re behind a proxy, you also need to set the environment variable http_proxy to http://....
--no-check-certificate Disable the certificate verification to allow access to unsecure HTTP resources (for example when the certificate is no longer valid or self signed).
Options affecting specific writers --self-contained Produce a standalone HTML file with no external dependencies, using data: URIs to incorporate the contents of linked scripts, stylesheets, images, and videos.  Implies --standalone.  The resulting file should be “self-contained,” in the sense that it needs no external files and no net access to be displayed properly by a browser.  This option works only with HTML output formats, including html4, html5, html+lhs, html5+lhs, s5, slidy, slideous, dzslides, and revealjs.  Scripts, images, and stylesheets at absolute URLs will be downloaded; those at relative URLs will be sought relative to the working directory (if the first source file is local) or relative to the base URL (if the first source file is remote).  Elements with the attribute data-external="1" will be left alone; the documents they link to will not be incorporated in the document.  Limitation: resources that are loaded dynamically through JavaScript cannot be incorporated; as a result, --self- contained does not work with --mathjax, and some advanced features (e.g. zoom or speaker notes) may not work in an offline “self- contained” reveal.js slide show.
--html-q-tags Use <q> tags for quotes in HTML.  (This option only has an effect if the smart extension is enabled for the input format used.)
--ascii Use only ASCII characters in output.  Currently supported for XML and HTML formats (which use entities instead of UTF-8 when this option is selected), CommonMark, gfm, and Markdown (which use entities), roff ms (which use hexadecimal escapes), and to a limited degree LaTeX (which uses standard commands for accented characters when possible).  roff man output uses ASCII by default.
--reference-links Use reference-style links, rather than inline links, in writing Markdown or reStructuredText.  By default inline links are used. The placement of link references is affected by the --reference- location option.
--reference-location=block|section|document Specify whether footnotes (and references, if reference-links is set) are placed at the end of the current (top-level) block, the current section, or the document.  The default is document. Currently only affects the markdown writer.
--markdown-headings=setext|atx Specify whether to use ATX-style (#-prefixed) or Setext-style (underlined) headings for level 1 and 2 headings in Markdown output.  (The default is atx.) ATX-style headings are always used for levels 3+.  This option also affects Markdown cells in ipynb output.
--atx-headers Deprecated synonym for --markdown-headings=atx.
--top-level-division=default|section|chapter|part Treat top-level headings as the given division type in LaTeX, ConTeXt, DocBook, and TEI output.  The hierarchy order is part, chapter, then section; all headings are shifted such that the top- level heading becomes the specified type.  The default behavior is to determine the best division type via heuristics: unless other conditions apply, section is chosen.  When the documentclass variable is set to report, book, or memoir (unless the article option is specified), chapter is implied as the setting for this option.  If beamer is the output format, specifying either chapter or part will cause top-level headings to become \part{..}, while second-level headings remain as their default type.
-N, --number-sections Number section headings in LaTeX, ConTeXt, HTML, Docx, ms, or EPUB output.  By default, sections are not numbered.  Sections with class unnumbered will never be numbered, even if --number-sections is specified.
--number-offset=NUMBER[,NUMBER,...] Offset for section headings in HTML output (ignored in other output formats).  The first number is added to the section number for top-level headings, the second for second-level headings, and so on.  So, for example, if you want the first top-level heading in your document to be numbered “6”, specify --number-offset=5. If your document starts with a level-2 heading which you want to be numbered “1.5”, specify --number-offset=1,4.  Offsets are 0 by default.  Implies --number-sections.
--listings Use the listings package for LaTeX code blocks.  The package does not support multi-byte encoding for source code.  To handle UTF-8 you would need to use a custom template.  This issue is fully documented here: Encoding issue with the listings package.
-i, --incremental Make list items in slide shows display incrementally (one by one). The default is for lists to be displayed all at once.
--slide-level=NUMBER Specifies that headings with the specified level create slides (for beamer, s5, slidy, slideous, dzslides).  Headings above this level in the hierarchy are used to divide the slide show into sections; headings below this level create subheads within a slide.  Note that content that is not contained under slide-level headings will not appear in the slide show.  The default is to set the slide level based on the contents of the document; see Structuring the slide show.
--section-divs Wrap sections in <section> tags (or <div> tags for html4), and attach identifiers to the enclosing <section> (or <div>) rather than the heading itself.  See Heading identifiers, below.
--email-obfuscation=none|javascript|references Specify a method for obfuscating mailto: links in HTML documents. none leaves mailto: links as they are.  javascript obfuscates them using JavaScript.  references obfuscates them by printing their letters as decimal or hexadecimal character references.  The default is none.
--id-prefix=STRING Specify a prefix to be added to all identifiers and internal links in HTML and DocBook output, and to footnote numbers in Markdown and Haddock output.  This is useful for preventing duplicate identifiers when generating fragments to be included in other pages.
-T STRING, --title-prefix=STRING Specify STRING as a prefix at the beginning of the title that appears in the HTML header (but not in the title as it appears at the beginning of the HTML body).  Implies --standalone.
-c URL, --css=URL Link to a CSS style sheet.  This option can be used repeatedly to include multiple files.  They will be included in the order specified.
A stylesheet is required for generating EPUB.  If none is provided using this option (or the css or stylesheet metadata fields), pandoc will look for a file epub.css in the user data directory (see --data-dir).  If it is not found there, sensible defaults will be used.
--reference-doc=FILE Use the specified file as a style reference in producing a docx or ODT file.
Docx   For best results, the reference docx should be a modified version of a docx file produced using pandoc.  The contents of the reference docx are ignored, but its stylesheets and document properties (including margins, page size, header, and footer) are used in the new docx.  If no reference docx is specified on the command line, pandoc will look for a file reference.docx in the user data directory (see --data- dir).  If this is not found either, sensible defaults will be used.
To produce a custom reference.docx, first get a copy of the default reference.docx: pandoc -o custom-reference.docx --print-default-data-file reference.docx.  Then open custom-reference.docx in Word, modify the styles as you wish, and save the file.  For best results, do not make changes to this file other than modifying the styles used by pandoc:
Paragraph styles:
• Normal
• Body Text
• First Paragraph
• Compact
• Title
• Subtitle
• Author
• Date
• Abstract
• Bibliography
• Heading 1
• Heading 2
• Heading 3
• Heading 4
• Heading 5
• Heading 6
• Heading 7
• Heading 8
• Heading 9
• Block Text
• Footnote Text
• Definition Term
• Definition
• Caption
• Table Caption
• Image Caption
• Figure
• Captioned Figure
• TOC Heading
Character styles:
• Default Paragraph Font
• Body Text Char
• Verbatim Char
• Footnote Reference
• Hyperlink
• Section Number
Table style:
• Table
ODT    For best results, the reference ODT should be a modified version of an ODT produced using pandoc.  The contents of the reference ODT are ignored, but its stylesheets are used in the new ODT.  If no reference ODT is specified on the command line, pandoc will look for a file reference.odt in the user data directory (see --data-dir).  If this is not found either, sensible defaults will be used.
To produce a custom reference.odt, first get a copy of the default reference.odt: pandoc -o custom-reference.odt --print-default-data-file reference.odt.  Then open custom- reference.odt in LibreOffice, modify the styles as you wish, and save the file.
PowerPoint Templates included with Microsoft PowerPoint 2013 (either with .pptx or .potx extension) are known to work, as are most templates derived from these.
The specific requirement is that the template should begin with the following first four layouts:
1. Title Slide
2. Title and Content
3. Section Header
4. Two Content
All templates included with a recent version of MS PowerPoint will fit these criteria.  (You can click on Layout under the Home menu to check.)
You can also modify the default reference.pptx: first run pandoc -o custom-reference.pptx --print-default-data-file reference.pptx, and then modify custom-reference.pptx in MS PowerPoint (pandoc will use the first four layout slides, as mentioned above).
--epub-cover-image=FILE Use the specified image as the EPUB cover.  It is recommended that the image be less than 1000px in width and height.  Note that in a Markdown source document you can also specify cover-image in a YAML metadata block (see EPUB Metadata, below).
--epub-metadata=FILE Look in the specified XML file for metadata for the EPUB.  The file should contain a series of Dublin Core elements.  For example:
<dc:rights>Creative Commons</dc:rights> <dc:language>es-AR</dc:language>
By default, pandoc will include the following metadata elements: <dc:title> (from the document title), <dc:creator> (from the document authors), <dc:date> (from the document date, which should be in ISO 8601 format), <dc:language> (from the lang variable, or, if is not set, the locale), and <dc:identifier id="BookId"> (a randomly generated UUID).  Any of these may be overridden by elements in the metadata file.
Note: if the source document is Markdown, a YAML metadata block in the document can be used instead.  See below under EPUB Metadata.
--epub-embed-font=FILE Embed the specified font in the EPUB.  This option can be repeated to embed multiple fonts.  Wildcards can also be used: for example, DejaVuSans-*.ttf.  However, if you use wildcards on the command line, be sure to escape them or put the whole filename in single quotes, to prevent them from being interpreted by the shell.  To use the embedded fonts, you will need to add declarations like the following to your CSS (see --css):
@font-face { font-family: DejaVuSans; font-style: normal; font-weight: normal; src:url("DejaVuSans-Regular.ttf"); } @font-face { font-family: DejaVuSans; font-style: normal; font-weight: bold; src:url("DejaVuSans-Bold.ttf"); } @font-face { font-family: DejaVuSans; font-style: italic; font-weight: normal; src:url("DejaVuSans-Oblique.ttf"); } @font-face { font-family: DejaVuSans; font-style: italic; font-weight: bold; src:url("DejaVuSans-BoldOblique.ttf"); } body { font-family: "DejaVuSans"; }
--epub-chapter-level=NUMBER Specify the heading level at which to split the EPUB into separate “chapter” files.  The default is to split into chapters at level-1 headings.  This option only affects the internal composition of the EPUB, not the way chapters and sections are displayed to users.  Some readers may be slow if the chapter files are too large, so for large documents with few level-1 headings, one might want to use a chapter level of 2 or 3.
--epub-subdirectory=DIRNAME Specify the subdirectory in the OCF container that is to hold the EPUB-specific contents.  The default is EPUB.  To put the EPUB contents in the top level, use an empty string.
--ipynb-output=all|none|best Determines how ipynb output cells are treated.  all means that all of the data formats included in the original are preserved.  none means that the contents of data cells are omitted.  best causes pandoc to try to pick the richest data block in each output cell that is compatible with the output format.  The default is best.
--pdf-engine=PROGRAM Use the specified engine when producing PDF output.  Valid values are pdflatex, lualatex, xelatex, latexmk, tectonic, wkhtmltopdf, weasyprint, prince, context, and pdfroff.  If the engine is not in your PATH, the full path of the engine may be specified here.  If this option is not specified, pandoc uses the following defaults depending on the output format specified using -t/--to:
• -t latex or none: pdflatex (other options: xelatex, lualatex, tectonic, latexmk)
• -t context: context
• -t html: wkhtmltopdf (other options: prince, weasyprint; see print-css.rocks for a good introduction to PDF generation from HTML/CSS.)
• -t ms: pdfroff
--pdf-engine-opt=STRING Use the given string as a command-line argument to the pdf-engine. For example, to use a persistent directory foo for latexmk’s auxiliary files, use --pdf-engine-opt=-outdir=foo.  Note that no check for duplicate options is done.
Citation rendering -C, --citeproc Process the citations in the file, replacing them with rendered citations and adding a bibliography.  Citation processing will not take place unless bibliographic data is supplied, either through an external file specified using the --bibliography option or the bibliography field in metadata, or via a references section in metadata containing a list of citations in CSL YAML format with Markdown formatting.  The style is controlled by a CSL stylesheet specified using the --csl option or the csl field in metadata. (If no stylesheet is specified, the chicago-author-date style will be used by default.) The citation processing transformation may be applied before or after filters or Lua filters (see --filter, --lua-filter): these transformations are applied in the order they appear on the command line.  For more information, see the section on Citations.
--bibliography=FILE Set the bibliography field in the document’s metadata to FILE, overriding any value set in the metadata.  If you supply this argument multiple times, each FILE will be added to bibliography. If FILE is a URL, it will be fetched via HTTP.  If FILE is not found relative to the working directory, it will be sought in the resource path (see --resource-path).
--csl=FILE Set the csl field in the document’s metadata to FILE, overriding any value set in the metadata.  (This is equivalent to --metadata csl=FILE.) If FILE is a URL, it will be fetched via HTTP.  If FILE is not found relative to the working directory, it will be sought in the resource path (see --resource-path) and finally in the csl subdirectory of the pandoc user data directory.
--citation-abbreviations=FILE Set the citation-abbreviations field in the document’s metadata to FILE, overriding any value set in the metadata.  (This is equivalent to --metadata citation-abbreviations=FILE.) If FILE is a URL, it will be fetched via HTTP.  If FILE is not found relative to the working directory, it will be sought in the resource path (see --resource-path) and finally in the csl subdirectory of the pandoc user data directory.
--natbib Use natbib for citations in LaTeX output.  This option is not for use with the --citeproc option or with PDF output.  It is intended for use in producing a LaTeX file that can be processed with bibtex.
--biblatex Use biblatex for citations in LaTeX output.  This option is not for use with the --citeproc option or with PDF output.  It is intended for use in producing a LaTeX file that can be processed with bibtex or biber.
Math rendering in HTML The default is to render TeX math as far as possible using Unicode characters.  Formulas are put inside a span with class="math", so that they may be styled differently from the surrounding text if needed. However, this gives acceptable results only for basic math, usually you will want to use --mathjax or another of the following options.
--mathjax[=URL] Use MathJax to display embedded TeX math in HTML output.  TeX math will be put between \(...\) (for inline math) or \[...\] (for display math) and wrapped in <span> tags with class math.  Then the MathJax JavaScript will render it.  The URL should point to the MathJax.js load script.  If a URL is not provided, a link to the Cloudflare CDN will be inserted.
--mathml Convert TeX math to MathML (in epub3, docbook4, docbook5, jats, html4 and html5).  This is the default in odt output.  Note that currently only Firefox and Safari (and select e-book readers) natively support MathML.
--webtex[=URL] Convert TeX formulas to <img> tags that link to an external script that converts formulas to images.  The formula will be URL-encoded and concatenated with the URL provided.  For SVG images you can for example use --webtex https://latex.codecogs.com/svg.latex?. If no URL is specified, the CodeCogs URL generating PNGs will be used (https://latex.codecogs.com/png.latex?).  Note: the --webtex option will affect Markdown output as well as HTML, which is useful if you’re targeting a version of Markdown without native math support.
--katex[=URL] Use KaTeX to display embedded TeX math in HTML output.  The URL is the base URL for the KaTeX library.  That directory should contain a katex.min.js and a katex.min.css file.  If a URL is not provided, a link to the KaTeX CDN will be inserted.
--gladtex Enclose TeX math in <eq> tags in HTML output.  The resulting HTML can then be processed by GladTeX to produce SVG images of the typeset formulas and an HTML file with these images embedded.
pandoc -s --gladtex input.md -o myfile.htex gladtex -d image_dir myfile.htex # produces myfile.html and images in image_dir
Options for wrapper scripts --dump-args Print information about command-line arguments to stdout, then exit.  This option is intended primarily for use in wrapper scripts.  The first line of output contains the name of the output file specified with the -o option, or - (for stdout) if no output file was specified.  The remaining lines contain the command-line arguments, one per line, in the order they appear.  These do not include regular pandoc options and their arguments, but do include any options appearing after a -- separator at the end of the line.
--ignore-args Ignore command-line arguments (for use in wrapper scripts). Regular pandoc options are not ignored.  Thus, for example,
pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
pandoc -o foo.html -s
If pandoc completes successfully, it will return exit code 0.  Nonzero exit codes have the following meanings:
Code   Error ─────────────────────────────────────── 3   PandocFailOnWarningError 4   PandocAppError 5   PandocTemplateError 6   PandocOptionError 21   PandocUnknownReaderError 22   PandocUnknownWriterError 23   PandocUnsupportedExtensionError 24   PandocCiteprocError 31   PandocEpubSubdirectoryError 43   PandocPDFError 44   PandocXMLError 47   PandocPDFProgramNotFoundError 61   PandocHttpError 62   PandocShouldNeverHappenError 63   PandocSomeError 64   PandocParseError 65   PandocParsecError 66   PandocMakePDFError 67   PandocSyntaxMapError 83   PandocFilterError 91   PandocMacroLoop 92   PandocUTF8DecodingError 93   PandocIpynbDecodingError 94   PandocUnsupportedCharsetError 97   PandocCouldNotFindDataFileError
99   PandocResourceNotFound
The --defaults option may be used to specify a package of options.  Here is a sample defaults file demonstrating all of the fields that may be used:
from: markdown+emoji # reader: may be used instead of from: to: html5 # writer: may be used instead of to:
# leave blank for output to stdout: output-file: # leave blank for input from stdin, use [] for no input: input-files: - preface.md - content.md # or you may use input-file: with a single value
# Include options from the specified defaults files. # The files will be searched for first in the working directory # and then in the defaults subdirectory of the user data directory. # The files are included in the same order in which they appear in # the list. Options specified in this defaults file always have # priority over the included ones. defaults: - defsA - defsB
template: letter standalone: true self-contained: false
# note that structured variables may be specified: variables: documentclass: book classoption: - twosides - draft
# metadata values specified here are parsed as literal # string text, not markdown: metadata: author: - Sam Smith - Julie Liu metadata-files: - boilerplate.yaml # or you may use metadata-file: with a single value
# Note that these take files, not their contents: include-before-body: [] include-after-body: [] include-in-header: [] resource-path: ["."]
# turn on built-in citation processing.  Note that if you need # control over when the citeproc processing is done relative # to other filters, you should instead use `citeproc` in the # list of `filters` (see below). citeproc: true csl: ieee bibliography: - foobar.bib - barbaz.json citation-abbreviations: abbrevs.json
# Filters will be assumed to be Lua filters if they have # the .lua extension, and json filters otherwise.  But # the filter type can also be specified explicitly, as shown. # Filters are run in the order specified. # To include the built-in citeproc filter, use either `citeproc` # or `{type: citeproc}`. filters: - wordcount.lua - type: json path: foo.lua
file-scope: false
data-dir:
# ERROR, WARNING, or INFO verbosity: INFO log-file: log.json
# citeproc, natbib, or biblatex. This only affects LaTeX # output.  If you want to use citeproc to format citations, # you should also set 'citeproc: true' (see above). cite-method: citeproc
# part, chapter, section, or default: top-level-division: chapter abbreviations:
pdf-engine: pdflatex pdf-engine-opts: - "-shell-escape" # you may also use pdf-engine-opt: with a single option # pdf-engine-opt: "-shell-escape"
# auto, preserve, or none wrap: auto columns: 78 dpi: 72
extract-media: mediadir
table-of-contents: true toc-depth: 2 number-sections: false # a list of offsets at each heading level number-offset: [0,0,0,0,0,0] # toc: may also be used instead of table-of-contents: shift-heading-level-by: 1 section-divs: true identifier-prefix: foo title-prefix: "" strip-empty-paragraphs: true # lf, crlf, or native eol: lf strip-comments: false indented-code-classes: [] ascii: true default-image-extension: ".jpg"
# either a style name of a style definition file: highlight-style: pygments syntax-definitions: - c.xml # or you may use syntax-definition: with a single value listings: false
reference-doc: myref.docx
# method is plain, webtex, gladtex, mathml, mathjax, katex # you may specify a url with webtex, mathjax, katex html-math-method: method: mathjax url: "https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js" # none, references, or javascript email-obfuscation: javascript
tab-stop: 8 preserve-tabs: true
incremental: false slide-level: 2
epub-subdirectory: EPUB epub-metadata: meta.xml epub-fonts: - foobar.otf epub-chapter-level: 1 epub-cover-image: cover.jpg
reference-links: true # block, section, or document reference-location: block markdown-headings: setext
# accept, reject, or all track-changes: accept
html-q-tags: false css: - site.css
# none, all, or best ipynb-output: best
# A list of two-element lists request-headers: - ["User-Agent", "Mozilla/5.0"]
fail-if-warnings: false dump-args: false ignore-args: false trace: false
Fields that are omitted will just have their regular default values.  So a defaults file can be as simple as one line:
verbosity: INFO
In fields that expect a file path (or list of file paths), the following syntax may be used to interpolate environment variables:
csl:  ${HOME}/mycsldir/special.csl
${USERDATA} may also be used; this will always resolve to the user data directory that is current when the defaults file is parsed, regardless of the setting of the environment variable USERDATA.
${.} will resolve to the directory containing the default file itself. This allows you to refer to resources contained in that directory:
epub-cover-image: ${.}/cover.jpg epub-metadata: ${.}/meta.xml resource-path: - .             # the working directory from which pandoc is run - ${.}/images   # the images subdirectory of the directory # containing this defaults file
This environment variable interpolation syntax only works in fields that expect file paths.
Default files can be placed in the defaults subdirectory of the user data directory and used from any directory.  For example, one could create a file specifying defaults for writing letters, save it as letter.yaml in the defaults subdirectory of the user data directory, and then invoke these defaults from any directory using pandoc --defaults letter or pandoc -dletter.
When multiple defaults are used, their contents will be combined.
Note that, where command-line arguments may be repeated (--metadata-file, --css, --include-in-header, --include-before-body, --include-after-body, --variable, --metadata, --syntax-definition), the values specified on the command line will combine with values specified in the defaults file, rather than replacing them.
When the -s/--standalone option is used, pandoc uses a template to add header and footer material that is needed for a self-standing document. To see the default template that is used, just type
pandoc -D *FORMAT*
where FORMAT is the name of the output format.  A custom template can be specified using the --template option.  You can also override the system default templates for a given output format FORMAT by putting a file templates/default.*FORMAT* in the user data directory (see --data-dir, above).  Exceptions:
• For odt output, customize the default.opendocument template.
• For pdf output, customize the default.latex template (or the default.context template, if you use -t context, or the default.ms template, if you use -t ms, or the default.html template, if you use -t html).
• docx and pptx have no template (however, you can use --reference-doc to customize the output).
Templates contain variables, which allow for the inclusion of arbitrary information at any point in the file.  They may be set at the command line using the -V/--variable option.  If a variable is not set, pandoc will look for the key in the document’s metadata, which can be set using either YAML metadata blocks or with the -M/--metadata option.  In addition, some variables are given default values by pandoc.  See Variables below for a list of variables used in pandoc’s default templates.
If you use custom templates, you may need to revise them as pandoc changes.  We recommend tracking the changes in the default templates, and modifying your custom templates accordingly.  An easy way to do this is to fork the pandoc-templates repository and merge in changes after each pandoc release.
Template syntax Comments Anything between the sequence $-- and the end of the line will be treated as a comment and omitted from the output.
Delimiters To mark variables and control structures in the template, either $...$ or ${...} may be used as delimiters.  The styles may also be mixed in the same template, but the opening and closing delimiter must match in each case.  The opening delimiter may be followed by one or more spaces or tabs, which will be ignored.  The closing delimiter may be followed by one or more spaces or tabs, which will be ignored.
To include a literal $ in the document, use $$.
Interpolated variables A slot for an interpolated variable is a variable name surrounded by matched delimiters.  Variable names must begin with a letter and can contain letters, numbers, _, -, and ..  The keywords it, if, else, endif, for, sep, and endfor may not be used as variable names.  Examples:
$foo$ $foo.bar.baz$ $foo_bar.baz-bim$ $ foo $ ${foo} ${foo.bar.baz} ${foo_bar.baz-bim} ${ foo }
Variable names with periods are used to get at structured variable values.  So, for example, employee.salary will return the value of the salary field of the object that is the value of the employee field.
• If the value of the variable is simple value, it will be rendered verbatim.  (Note that no escaping is done; the assumption is that the calling program will escape the strings appropriately for the output format.)
• If the value is a list, the values will be concatenated.
• If the value is a map, the string true will be rendered.
• Every other value will be rendered as the empty string.
Conditionals A conditional begins with if(variable) (enclosed in matched delimiters) and ends with endif (enclosed in matched delimiters).  It may optionally contain an else (enclosed in matched delimiters).  The if section is used if variable has a non-empty value, otherwise the else section is used (if present).  Examples:
$if(foo)$bar$endif$
$if(foo)$ $foo$ $endif$
$if(foo)$ part one $else$ part two $endif$
${if(foo)}bar${endif}
${if(foo)} ${foo} ${endif}
${if(foo)} ${ foo.bar } ${else} no foo! ${endif}
The keyword elseif may be used to simplify complex nested conditionals:
$if(foo)$ XXX $elseif(bar)$ YYY $else$ ZZZ $endif$
For loops A for loop begins with for(variable) (enclosed in matched delimiters) and ends with endfor (enclosed in matched delimiters.
• If variable is an array, the material inside the loop will be evaluated repeatedly, with variable being set to each value of the array in turn, and concatenated.
• If variable is a map, the material inside will be set to the map.
• If the value of the associated variable is not an array or a map, a single iteration will be performed on its value.
$for(foo)$$foo$$sep$, $endfor$
$for(foo)$ - $foo.last$, $foo.first$ $endfor$
${ for(foo.bar) } - ${ foo.bar.last }, ${ foo.bar.first } ${ endfor }
$for(mymap)$ $it.name$: $it.office$ $endfor$
You may optionally specify a separator between consecutive values using sep (enclosed in matched delimiters).  The material between sep and the endfor is the separator.
${ for(foo) }${ foo }${ sep }, ${ endfor }
Instead of using variable inside the loop, the special anaphoric keyword it may be used.
${ for(foo.bar) } - ${ it.last }, ${ it.first } ${ endfor }