Convert PDF to JPG Images Online for Free

PDF to JPG: Turn Every Page of a PDF into an Image You Can Drop Anywhere

A PDF to JPG converter renders each page of a document as a picture — the exact visual layout, fonts, images, and colors, captured as a JPG (or PNG) file instead of a page inside a PDF viewer. This tool does that rendering right in your browser: pick a PDF, and pdfjs draws each page onto a hidden canvas element at roughly twice the PDF's native resolution, then exports that canvas as a JPG. A single-page PDF gives you back one image; a multi-page PDF gives you back a ZIP archive holding one JPG per page, named so the order is obvious at a glance.

Rasterizing a page this way is useful anywhere a PDF viewer isn't welcome or convenient — a slide deck exported as a PDF that needs to become individual images for a presentation tool, a scanned form that needs to be dropped into an image editor, or a single page of a report that needs to appear inline in an email or a chat message where attaching a whole PDF would be overkill. The same conversion is also available as a metered API endpoint that rasterizes server-side through a different engine (mupdf), with configurable resolution — useful when you need this behavior from a script rather than a browser tab, which the comparison further down covers in detail.

How to Convert a PDF to JPG with This Tool

1. Drop or select the PDF you want to convert. Everything from here happens inside the same browser tab.
2. The tool loads pdfjs and opens the document, then processes each page in order: it computes a viewport at roughly double the PDF's default scale (a reasonable middle ground between file size and legibility) and renders that page onto an off-screen canvas element.
3. Each rendered canvas is exported as a JPG at high quality (92%), which balances sharp text and images against a manageable file size.
4. If the source PDF has exactly one page, you get a single page.jpg ready to download immediately. If it has more than one page, every rendered page is bundled together into a single pages.zip archive, with each entry named page-1.jpg, page-2.jpg, and so on.
5. Need this behavior from outside a browser — a script, a backend job, a batch pipeline? The metered API accepts a PDF upload plus optional dpi (capped at 300) and format (jpeg or png) parameters, and either returns one image directly (when you specify a single page) or a ZIP of every page (when you don't).

Both paths bound the source PDF to 500 pages, so an oversized document is rejected with a clear message rather than silently generating hundreds of megabytes of images in the background.

Why People Convert PDF Pages into Images

• Dropping a document page into a presentation or design file. Slide software and design tools generally accept images far more gracefully than embedded PDFs — converting first avoids fighting with an unsupported file type mid-project.
• Sharing a single page without sending the whole file. Pasting one page as an image into a chat thread or an email is often faster and more readable for the recipient than attaching a multi-page PDF and pointing them to "page 4."
• Feeding a page into an image-editing workflow. Cropping, annotating, or color-adjusting a document page is far easier with tools built for images than with a PDF-native editor.
• Producing thumbnails for a document library or a preview grid. A folder of scanned forms or reports becomes much easier to browse visually once every page has a corresponding image thumbnail.
• Archiving a printed or scanned form as individually retrievable page images. Some record-keeping systems expect image files per page rather than a single multi-page PDF, and rasterizing bridges that gap.

Resolution, Format, and What Rasterizing Actually Does

Rendering a PDF page to an image means deciding, ahead of time, how many pixels will represent the page — there's no such thing as a single "correct" resolution, because a PDF page is defined in points (a resolution-independent unit), and a raster image is defined in pixels. The browser tool on this page renders at a fixed scale chosen to be sharp enough for on-screen viewing and casual printing without producing an unnecessarily large file; the API version exposes this as an explicit dpi parameter instead, letting you request anywhere up to 300 dots per inch — the point past which the API caps the value regardless of what's requested, since resolution climbs the same way file size and render time do, and 300 DPI already covers standard print-quality output.

Setting	What it changes	Trade-off
Higher DPI / resolution	Sharper text and finer image detail	Larger file size, slower render
JPG format	Smaller files for photographic content	Lossy compression can soften fine text edges
PNG format (API only)	Lossless, crisper for text-heavy pages	Noticeably larger files than JPG at the same resolution
Single page vs. every page	One image vs. a ZIP of one image per page	Multi-page output takes proportionally longer

It's also worth being clear about what rasterizing does not preserve: once a page becomes a JPG or PNG, the text is no longer text — it's pixels shaped like letters. You can't select, search, or copy words out of the resulting image the way you could from the original PDF (or from this site's separate text extraction tool). Rasterizing trades that searchability away in exchange for a format that any image viewer, editor, or slide tool can open without needing to understand the PDF format at all.

For context on what a given DPI actually buys you: 300 DPI is the long-standing benchmark for professional print output, which is why the API caps requests there rather than allowing an arbitrarily high number — pushing past it produces diminishing returns in visible quality while multiplying file size and render time. Screen-only viewing, by contrast, rarely benefits from anything above roughly 150 DPI, since most displays can't show the extra detail anyway; the browser tool's fixed scale lands close to that range deliberately, aiming at the resolution most people actually need rather than the highest number technically possible.

Browser Rendering (pdfjs) vs. the Server API (mupdf)

Both paths produce a raster image per page, but the engine and the controls available differ:

	Browser tool (this page)	Metered API
Rendering engine	pdfjs, drawn to an HTML canvas	mupdf, rasterized server-side
Resolution control	Fixed at a sensible default (no slider)	Configurable dpi parameter, capped at 300
Format choice	JPG only	JPG or PNG
File transfer	The PDF never leaves your device	The PDF is uploaded to the server to be rasterized
Multi-page output	A ZIP built in your browser (client-zip)	A ZIP built server-side, same one-file-per-page layout

Does Converting a PDF to Images Here Upload My File?

Not with the browser tool on this page. Rendering happens entirely inside your browser tab using pdfjs and an off-screen canvas element; the PDF's bytes are read locally to produce the images, and neither the source file nor the rendered pictures need to touch a network connection to be produced — the ZIP for a multi-page document is even assembled client-side. That makes this the right choice whenever you're converting a document you have open right now and don't want it leaving your machine. The metered API, by contrast, is built for automation rather than a single manual conversion, and necessarily receives the uploaded PDF on the server so mupdf can rasterize it there — a reasonable trade for being callable from a script or backend job instead of a browser tab, but a real difference from the fully local browser path worth knowing about before you pick one.

Why did I get a ZIP file instead of a single image?

Because your source PDF has more than one page. The tool renders every page and bundles the resulting images together into one ZIP archive so you don't have to download each page separately; a single-page PDF instead produces just one image file.

Can I control the resolution or output format of the browser conversion?

The browser tool renders at a fixed scale and always exports JPG, with no resolution slider in the interface. If you need a specific DPI or a PNG output, the metered API accepts explicit dpi (up to 300) and format (jpeg or png) parameters.

Will the text on the page still be selectable in the resulting image?

No. Rasterizing converts the page into pixels — the text is now part of the picture, not separate character data, so it can't be selected, searched, or copied the way it could in the original PDF. If you need selectable or searchable text instead of an image, use this site's PDF to text extractor on the same source file.

Is there a limit on how many pages I can convert at once?

Yes — the source PDF is bounded to 500 pages on both the browser tool and the API, so an unusually large document is rejected with a clear message rather than generating an enormous number of images silently in the background.

Why does the JPG look slightly softer than the original PDF page?

JPG uses lossy compression, which trades a small amount of sharpness — particularly around fine text edges — for a meaningfully smaller file size. At the resolution this tool renders at, the difference is rarely noticeable on screen; if you need a lossless result instead, the metered API's PNG output avoids that trade-off entirely.

What colors will the rendered image use — will they match the PDF exactly?

The rendering targets standard RGB color, matching how the page displays on a normal screen. This is a faithful on-screen reproduction of the page rather than a print-color simulation, so if your PDF was built with print-specific color assumptions, the rendered image reflects how it looks on a monitor rather than how it would look coming off a specific printer.

Can I rasterize just one specific page instead of the whole document?

The metered API supports this directly — pass a 1-based page number and you'll get back a single image for that page rather than a ZIP of every page. The browser tool on this page always renders the entire document; if you only need one page from it, extract that page first with the PDF split tool and then convert the resulting single-page file.

Related Tools

Going the other direction, the JPG to PDF tool combines images back into a single PDF document, one image per page. If what you actually need out of the source PDF is the words rather than a picture of them, the PDF to text extractor reads the document's underlying text layer instead of rendering it. Before converting a large document to images, running it through the PDF compress tool first can make the source file itself smaller and quicker to process. And if you only need a handful of pages rasterized rather than the whole file, use the PDF split tool to pull out just those pages beforehand.