About PDFimage

PDFimage does one thing in two directions: images into PDFs, and PDF pages back into images. All of it runs inside the browser tab you’re reading this in.

How it works

• Images → PDF uses pdf-lib to write the PDF. JPEG and PNG data are embedded directly; other formats are decoded by your browser, by a WebAssembly build of libheif (HEIC) or by UTIF.js (TIFF) first.
• PDF → images uses Mozilla’s pdf.js, the engine behind Firefox’s PDF viewer, to draw each page onto a canvas at the DPI you choose, then your browser encodes it as JPG, PNG or WebP.
• ZIP downloads are packed locally with fflate.

What it deliberately doesn’t do

• No uploads, no accounts, no AI. Conversions are deterministic; there’s nothing a model would improve, and sending your documents to a server would defeat the point.
• No OCR. Text in images stays as pictures.
• No merging, splitting or compressing existing PDFs. This site sticks to converting between PDFs and pictures.

Honest limits

Your device’s memory is the real ceiling. Each rendered PDF page is capped at 16 megapixels so iPhone Safari can draw it; very large pages are rendered at a lower DPI and the result says so. HEIC decoding downloads a ~3 MB decoder the first time it’s needed.