PJPEG to Haddock Converter
FileFlip converts PJPEG 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 a PJPEG file to Haddock?#
- Drop your PJPEG 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 PJPEG to Haddock lose quality?#
No. The PJPEG 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 PJPEG files online?#
Yes, because nothing is uploaded. FileFlip converts PJPEG 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 PJPEG to Haddock actually does to the file#
Converting PJPEG 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, and drops EXIF metadata and ICC colour profile.
| Engine | ImageMagick, MuPDF and Pandoc |
|---|---|
| Conversion path | 3 steps: PJPEG → 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 |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| EXIF metadata | Dropped | The target format has nowhere to put it. |
| ICC colour profile | Dropped | The target format has nowhere to put it. |
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 a PJPEG file?#
PJPEG is progressive JPEG, a JPEG encoding choice rather than a different file format, where the image is built up through several increasingly detailed scans across the whole picture instead of filling in top to bottom in one pass.
Choose progressive encoding for images shown over a slow or uncertain connection, where a quick blurry preview beats a slow top-down reveal.
Convert to baseline JPEG when a downstream tool or embedded device only supports the simpler sequential scan order.
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.
PJPEG to Haddock questions people ask#
What is PJPEG?
PJPEG is progressive JPEG, a JPEG file encoded in a handful of increasingly detailed scans instead of one pass from top to bottom. It's still a JPEG file, just encoded differently, and opens anywhere JPEG does.
What's the difference between PJPEG and a regular JPEG?
A regular, baseline JPEG fills the image in from top to bottom as it loads. PJPEG encodes several scans of the whole picture, each adding sharper detail, so a rough version of the entire image appears almost immediately and refines as more data arrives.
Does progressive JPEG reduce image quality?
No, PJPEG uses the same lossy JPEG compression as baseline JPEG at a given quality setting, and often produces a slightly smaller file because each scan can use its own optimized Huffman table.
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.