INLINE to Haddock Converter
FileFlip converts INLINE to Haddock entirely inside your browser, using ImageMagick, MuPDF and Pandoc compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert an INLINE file to Haddock?#
- Drop your INLINE file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to Haddock and the conversion starts on its own. FileFlip downloads 79.9 MB of WebAssembly the first time and nothing after that, then runs ImageMagick, MuPDF and Pandoc on your own machine.
- Save the Haddock file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting INLINE to Haddock lose quality?#
No. The INLINE picture is placed into the Haddock document at its full resolution, so every pixel reaches it intact. What you give up is that it becomes a picture inside a document rather than text.
Is it safe to convert INLINE files online?#
Yes, because nothing is uploaded. FileFlip converts INLINE files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What INLINE to Haddock actually does to the file#
Converting INLINE to Haddock runs on ImageMagick, MuPDF and Pandoc, downloads 79.9 MB of WebAssembly the first time and nothing after that, places the picture into the document at full resolution.
| Engine | ImageMagick, MuPDF and Pandoc |
|---|---|
| Conversion path | 3 steps: INLINE → PNG → HTML → Haddock |
| Downloaded to your browser | 79.9 MB, once, then cached by your browser |
| Quality | Pixels preserved |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
Worth knowing before you start:
- the picture is placed in the document as a picture; no text is recognised out of it
- the file passes through HTML on the way, so anything HTML cannot express does not survive
What is an INLINE file?#
An INLINE reference is not a file at all but ImageMagick's own syntax, inline:, for handing it an image that already exists as base64 text, such as a data: URI copied out of an HTML page or an API response.
Use the inline: syntax when an image already exists as base64 text, such as a data: URI pulled from HTML or JSON, and it needs to be read without writing a temporary file first.
There is nothing to convert away from: inline: is a way of pointing ImageMagick at an image, not a format a finished file is ever saved in.
What is a Haddock file?#
A Haddock file holds documentation written in Haddock markup, the comment syntax Haskell's own documentation generator reads out of source files to build a module's API reference.
Write Haddock markup directly in Haskell source comments so `cabal haddock` can generate the package's API documentation.
Convert Haddock markup to Markdown when the same text needs to appear in a README or a project website outside the generated API docs.
INLINE to Haddock questions people ask#
What is an INLINE file?
INLINE isn't a file format, it's ImageMagick's inline: syntax for reading an image supplied as base64 text, most often a data: URI. The base64 data can come from a text file or be typed directly after inline: on the command line.
Can I save or write a file as INLINE?
No. The inline: mechanism in ImageMagick only reads base64-encoded images; there is no corresponding way to write one back out, so a converter that reads INLINE decodes the base64 into whichever image format was actually encoded inside it.
Why does my base64 image fail when pasted as inline:?
Typing a base64 string directly after inline: on a command line is limited to 5000 characters in ImageMagick, so a photo-sized data URI will fail there even though it works from a text file. The comma after the MIME type is also required to mark where the base64 data starts, even though ImageMagick otherwise ignores the MIME type itself.
What is a .haddock file?
A .haddock file holds text written in Haddock markup, the comment syntax Haskell's documentation generator reads. In practice this markup normally lives inside `-- |` and `-- ^` comments in a .hs source file rather than a standalone file, so a .haddock file usually appears when that text has been extracted or converted on its own.