Downloads of v


Last Update:

05 Sep 2012

Package Maintainer(s):

Software Author(s):

  • John MacFarlane


text markdown latex pdf docx restructuredText textil html docbook slides


This is not the latest version of Pandoc available.

  • 1
  • 2
  • 3 | Updated: 05 Sep 2012



Downloads of v



Software Author(s):

  • John MacFarlane

  • 1
  • 2
  • 3

This is not the latest version of Pandoc available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files


To install Pandoc, run the following command from the command line or from PowerShell:


To upgrade Pandoc, run the following command from the command line or from PowerShell:


To uninstall Pandoc, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade pandoc -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade pandoc -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure pandoc installed
    name: pandoc
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'pandoc' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: pandoc,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller pandoc
   Name     = 'pandoc'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'pandoc':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install pandoc version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 18 Jul 2016.


If you need to convert files from one markup format into another, pandoc is your swiss-army knife. Pandoc can convert documents in markdown, reStructuredText, textile, HTML, DocBook, or LaTeX

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Pandoc 2.14.1 12841 Tuesday, July 20, 2021 Approved
Pandoc 10942 Wednesday, June 23, 2021 Approved
Pandoc 4697 Monday, June 14, 2021 Approved
Pandoc 5727 Tuesday, June 1, 2021 Approved
Pandoc 2.14 1827 Sunday, May 30, 2021 Approved
Pandoc 2.13 23747 Monday, March 22, 2021 Approved
Pandoc 2.12 6238 Tuesday, March 9, 2021 Approved
Pandoc 2.11.4 16187 Sunday, January 24, 2021 Approved
Pandoc 9492 Wednesday, December 30, 2020 Approved

Don’t encode/decode file paths if base >= 4.4. Prior to base 4.4, filepaths and command line arguments were treated as unencoded lists of bytes, not unicode strings, so we had to work around that by encoding and decoding them. This commit adds CPP checks for the base version that intelligibly enable encoding/decoding when needed. Fixes a bug with multilingual filenames when pandoc was compiled with ghc 7.4 (#540).

Don’t generate an empty H1 after hrule slide breaks. We now use a slide-level header with contents [Str "\0"] to mark an hrule break. This avoids creation of an empty H1 in these contexts. Closes #484.

Docbook reader: Added support for “bold” emphasis. Thanks to mb21.

In, ensure citeproc-hs is built with the embed_data_files flag.

MediaWiki writer: Avoid extra blank lines after sublists (Gavin Beatty).

ConTeXt writer: Don’t escape &, ^, <, >, _, simplified escapes for } and { to { and } (Aditya Mahajan).

Fixed handling of absolute URLs in CSS imports with --self-contained. Closes #535.

Added webm to mime types. Closes #543.

Added some missing exports and tests to the cabal file (Alexander V Vershilov).

Compile with -rtsopts and -threaded by default.

This package has no dependencies.

Discussion for the Pandoc Package

Ground Rules:

  • This discussion is only about Pandoc and the Pandoc package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Pandoc, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus