PDF to JIFF Converter

The short version

There is no image format called JIFF. The name is a variant spelling of JFIF, which itself is a thin convention wrapped around JPEG. So this page does not run a JIFF encoder — it draws each PDF page and saves it through the JPEG encoder, then labels the download with a .jiff extension. If you opened the file in a hex editor you would find the familiar JPEG start marker, not a separate codec.

That is not a trick. Legacy archives, scanned document bundles and a few old cataloguing tools contain files ending in .jiff, and someone eventually has to produce one. This page exists so that the extension matches without a second conversion step.

Where the name comes from

The JPEG standard defined how to compress a picture but not how to describe its pixel layout, so an interchange layer was needed on top. An early proposal used the name JIF. The JFIF convention — JPEG File Interchange Format — became the version that tools actually implemented, adding a header segment that states the sample precision, the pixel density and the aspect ratio.

The extension was never governed tightly. Files circulated as .jfif, .jif and .jiff depending on the software that wrote them, and some of those spellings were simply typos that stuck in a product's save dialog. The bytes stayed JPEG throughout. That is why a file called scan.jiff from 1998 and a file called page.jpg from today can be decoded by the same library without any conversion.

What this page writes

• Encoding: the browser's JPEG encoder, at the quality percentage you set.
• Extension: .jiff, applied to the page filename.
• MIME type on the blob: image/jpeg, so any consumer that inspects content sees JPEG.
• Channel: entirely local. Nothing is posted to the server, unlike the GIF and BMP variants of this tool.
• One file per page: archive-page-7.jiff, with the ZIP named archive-selected-pages.zip.

The format dropdown is shared across this family of tools, so JIFF and JFIF are both listed. Switching between them changes only the extension, because the underlying encoder is identical. Switching to PNG or WebP changes the encoder; switching to GIF or BMP changes both the encoder and the route, since those two are finished on the server.

Four extensions that look alike

None of these is a different compression. The only meaningful differences are the header convention and the string after the dot. A program that decodes one can decode all four; a program that checks the name may accept only one.

Choosing quality for document pages

JPEG is lossy, and the setting is a budget rather than a guarantee. At 90 percent, body text on a white page stays crisp at normal reading distance and the file is a fraction of a lossless PNG. At 70, letters begin to show faint halos on curved strokes and thin rules can waver. At 50, small print on a scan becomes muddy.

Scanned pages behave differently from born-digital pages. A scan already carries sensor noise, which JPEG spends bits on; dropping to 75 to 80 often saves a lot of size with no visible change. A vector-clean page of 9-point type has hard edges that JPEG handles badly, so keep it at 85 or higher, or use PNG instead. There is no benefit above about 95 for either case — you pay bytes for detail nobody can see.

The render scale is the other lever. Setting 150 percent gives the encoder more pixels to work with and produces a more legible page when zoomed, at roughly twice the linear size. Setting 60 percent makes a small file that is fine for a thumbnail strip and useless for reading.

Working the page

1. Choose the PDF by dropping it on the panel or clicking the upload area.
2. Leave the format on JIFF, then set quality and scale. Defaults are 90 and 100 percent.
3. Press Render Pages and wait for the counter to reach the last page.
4. Click a page to mark it, or use the single, range and manual entry fields to build a selection.
5. Use a card's download button for one file, or the ZIP button to collect the marked pages.

Every page is rendered even if you only want one. On a long report, that is the slowest part of the job; page selection does not reduce it. The status line reports the current page while rendering, and the progress bar tracks the overall count.

Renaming and sending

If the recipient turns out to want .jpg, renaming the file is enough. In Windows Explorer or macOS Finder, change the suffix; the image does not need re-encoding and loses nothing. Do not "convert" a .jiff to .jpg in an image editor at high quality — that would decode and re-encode, throwing away a generation of detail for a cosmetic change.

Some upload forms validate by extension and some by MIME type. If a form rejects .jiff but accepts .jpg, rename. If it accepts the upload and then fails to display it, the problem is more likely the form's thumbnail library than the file. If an email client warns about an unknown attachment type, renaming also resolves it, because mail software consults the extension when choosing an icon.

When not to use this output

For anything modern, .jpg is the safer label. For pages with small text, diagrams, tables or screenshots, PNG is sharper and often smaller. For a single shareable document, sending the original PDF is better than a folder of page images — the PDF keeps text selectable, retains links and stays one file.

Use the JIFF extension only when a system, an archive rule or a colleague explicitly asks for it. It is a compatibility choice, not a quality choice.

Limits

One document per run, every page rendered, still images only, no animation, no transparency, no text layer, no OCR and no DPI metadata. Password-protected PDFs cannot be opened. There is no batch mode across several PDFs, no background colour control and no option to add a margin around the page. Very large pages at high scale can exhaust browser memory, and a document of several hundred pages will render slowly because each page is encoded in turn.

Privacy

The file never leaves the browser. PDF.js reads it locally, the canvas produces the JPEG, and the download is assembled from a local blob. There is no server request for this format, so the page suits confidential documents better than the GIF or BMP versions of the same converter.

Common mistakes

• Believing .jiff is a distinct format. It is a JPEG with an unusual extension.
• Converting a .jiff to .jpg through an editor. Rename it instead; re-encoding costs quality.
• Using 100 percent quality for scans. It inflates the file without visible gain.
• Expecting page-range rendering. The range fields only affect which pages are downloaded.
• Sending .jiff to an automated portal. Extension whitelists are the most common cause of rejection.
• Assuming the server received the document. It did not; this format is handled locally.

Frequently Asked Questions