Convert PDF pages to JPG images

Plenty of Indian portals — from school admissions to local property registrations — accept only images, often a single JPG under 100 KB. Rendering locally lets you test several qualities in seconds.

Photocopy shops and printing kiosks want images, not PDFs, when they are producing a single sheet.

A rendered page is also the fastest way to grab a chart or a signature block out of a report for a presentation.

Some portals accept only JPG for a document that exists as a perfect PDF, usually the ones built around identity photographs. Rendering the pages is the only way to satisfy that, and the resolution you pick at that moment is the last chance to control detail.

Conversion also matters for previews: a thumbnail of page one, a signature image for a form, or a page pasted into a presentation all need pixels rather than PDF objects.

Rendering happens locally, which is what makes it usable for documents that should not travel — a bank statement, a medical report, a contract. The pages are drawn on your own device and never uploaded for conversion.

This tool exists for PDF documents handled in a hurry: no queue, no account, no upload, and a result you can verify on the spot. The explanation below is the same one we would give a colleague who asked how it works.

Password-protected and encrypted PDFs are not supported by these tools. If you are authorised to do so, use your PDF reader to make an unlocked copy and try that copy instead. Preserve the original, especially if it has a digital signature.

Scanned documents behave differently from every other file you have. Each page is a photograph, typically 1–3 MB at 300 dpi in colour, with no text layer unless your scanner ran OCR. That means there is no lossless cleverness available — the bytes genuinely are the picture. The cheapest wins on a scan are usually cropping the grey table edge out of every page and turning off colour where the document is black ink on white paper.

Accepted inputs are PDF files up to 50 MB. SVG, HTML and other script-bearing formats are refused outright rather than sanitised, because a file that can execute code has no business being re-encoded — and an upload field that accepts one is a security hole rather than a feature. The tool works on one file at a time, which keeps the result unambiguous.

We run pdf.js (the same engine Firefox uses) inside a Web Worker, so rendering never blocks the UI thread and a 100-page document will not freeze the tab. Each page is rasterised onto an OffscreenCanvas at your chosen scale, then encoded as JPEG at the quality you pick. Note the honest trade-off: rasterising text means it stops being selectable in the output — that is inherent to the JPG format, not to this tool. Pages are rendered with pdf.js at the chosen scale, sequentially, and encoded as JPEG. The output contains pictures of pages, not selectable or searchable text. Page and pixel limits apply, and large jobs can still exhaust device memory. Pages are rendered with pdf.js at the resolution you choose, so a 150 dpi export gives you roughly 1240 × 1754 pixels per A4 page — enough to read comfortably on screen. Rendering happens in a worker on your device, and the exported images keep the page aspect ratio exactly, which matters when the images will be reassembled into a PDF later.