Haddock to RST Converter
Processing entirely on your device — large files may take a moment.
Haddock is the documentation markup of the Haskell ecosystem: -- comment blocks attached to functions, rendered into the API docs every Hackage package ships. Convert RST docs to Markdown/Word for non-Sphinx audiences, or bring Markdown content into a Sphinx project as RST.
iLoveConverter processes everything locally on your computer, which makes it private and fast: no upload wait, no server storage, no limits. Add as many files as you like — batch conversion is built in.
How Haddock compares to RST
| Haddock | RST | |
|---|---|---|
| Structure | Comment markup (--, 'links', @mono@) | Plain text + directives |
| Best for | Haskell API documentation | Technical documentation |
How to convert Haddock to RST
- 1
Select your files
Select your Haddock file.
- 2
Convert instantly
The file is first converted to markdown (an interchange format that keeps headings, lists and paragraphs), then rebuilt into the target format.
- 3
Download results
Download the RST — structure preserved, heavy layout simplified.
About the Haddock format
Haddock is how Haskell explains itself: documentation comments in -- blocks, marked up with 'links' to identifiers, @monospace@ and /italics/, compiled into the API reference pages every package on Hackage publishes. The markup lives inside source files, but the format is its own small language.
Converted out of source comments, Haddock text becomes ordinary structured prose: Pandoc maps headings, code blocks and identifier links onto Markdown or HTML, so API knowledge can move into handbooks, wikis or static-site generators without retyping.
+Strengths
- ✓Documents live next to the code they describe
- ✓Identifier-aware linking across the API
- ✓Standard for the entire Haskell ecosystem
!Limitations
- −Meaningful only inside Haskell projects
- −Small grammar, few writers outside Haddock itself
- −Embedded in comments — needs extraction first
About the RST format
reStructuredText is the markup the Python world standardized on: Sphinx builds entire documentation sites from it, PyPI renders it as project descriptions, and tools like docutils parse it. Headings are underlined with punctuation, and directives like .. image:: and .. code-block:: extend the vocabulary without breaking plain-text readability.
RST is stricter than Markdown by design — that strictness is what makes large documentation trees consistent. Converting RST into Markdown or Word opens Sphinx projects to the rest of the team; converting Markdown back into RST feeds content into a Sphinx build.
+Strengths
- ✓The native format of Sphinx/Python docs
- ✓Consistent at scale: directives, roles, xrefs
- ✓Tables and admonitions as first-class syntax
!Limitations
- −Less widely known than Markdown
- −Stricter rules have a learning curve
- −Some directives are toolchain-specific
Why convert Haddock to RST?
There is a concrete reason this conversion exists: Meaningful only inside Haskell projects RST sidesteps that — The native format of Sphinx/Python docs If that is your situation, the tool above settles it in seconds, entirely on your device.
Frequently asked questions
Is this Haddock to RST converter really free?
Yes — completely free, with no sign-up, no watermark and no daily conversion limits. The site is supported by advertising.
Are my files uploaded to a server?
No. The conversion runs entirely inside your browser using WebAssembly, so your files never leave your device — that is what makes it instant and private.
Does it work on Windows, Mac, iPhone and Android?
Yes. Anything with a modern browser works: Windows, macOS, Linux, Android and iOS. No software installation is required.
Is there a file size limit for Haddock to RST?
The only limit is your device's memory, since nothing is uploaded. Files up to a few hundred megabytes work fine on a modern desktop browser; very large files simply take a little longer.
Can I edit the RST result afterwards?
That depends on the target: RST is designed for what it does, and this converter reproduces its content faithfully rather than inventing editable structure. For heavy re-editing, work from a format built for editing and export the final version here.
Will the layout of my Haddock file be preserved exactly?
This converter renders your Haddock content into RST with pages, proportions and images kept as close to the original as the target format allows. Use the preview before downloading to confirm it looks the way you expect.