To convert a PDF to JPG on Windows, open the PDF to JPG Converter in any modern browser, choose the file, set a render scale and a JPEG quality, then click Convert to JPG. Every page of the PDF is rendered as a separate JPEG image directly on your computer, so the document never gets uploaded to a remote server. The tool is built around three verifiable inputs (one PDF up to 25 MiB, a scale value, and a quality value between 0.60 and 1.00) and three matching outputs (a per-page preview, exact pixel dimensions, and an individual download button per image). Filenames include a zero-padded page number so the downloads sort in the original document order. Because the conversion runs in your browser rather than in a cloud queue, the result depends on your machine's memory and your PDF's page count, not on a third party's queue or quota.
Why Windows Has No Built-In Way to Save a PDF as a JPG
Windows does not ship a tool that exports a PDF page straight to a JPEG image. The closest built-in trick is to open the PDF in Microsoft Edge and use the Print dialog, but the printer list only includes Microsoft Print to PDF and the system's hardware printers, none of which produce a JPG. Adobe Acrobat Reader DC adds a Save As Other and Image option, yet the free reader either blocks that path behind a paid upgrade or downscales the output aggressively. WPS Office can export images, but it requires an install, an account prompt, and a sign-in screen on some image paths. Every one of these routes either forces a software install, sends the document to a third party, or produces output you cannot tune.
A browser-based local converter avoids all three problems. The PDF to JPG Converter runs entirely in Edge, Chrome, Firefox, or any other modern browser on Windows. PDF parsing, page rendering, and JPEG encoding happen on your machine through PDF.js, the same rendering engine that powers Mozilla's PDF viewer. Nothing is uploaded because there is no upload step in the workflow at all.
How the Converter Renders Pages Instead of Extracting Images
It is worth being clear about what the tool does and does not do. It does not pull embedded image objects out of the PDF, sort them, and save them as JPEGs. That operation belongs to a different tool. The converter renders each page, which means it asks PDF.js to draw the full visible content, including text, vector paths, photographs, annotations, transparency layers, and the coordinate system underneath, onto an HTML canvas, then encodes that canvas as a JPEG using the browser's built-in encoder. The Mozilla PDF.js project documents how its PDFPageProxy render call combines those layers into the final canvas bitmap.
Because the page is rendered rather than disassembled, the output is a flat picture of what the page looks like. Editable text, vector objects, layers, hyperlinks, form fields, and accessibility tags are not preserved in the JPEG. If any of those features is what you actually need, the conversion is the wrong step. Every page is also deliberately flattened onto a white background before encoding. JPEG has no transparency channel, so a transparent region in the source PDF would otherwise become an unpredictable dark area in the output. Flattening onto white keeps every result looking consistent regardless of how the source PDF handled transparency.
Convert a PDF to JPG on Windows in Three Steps
- Pick one non-empty PDF up to 25 MiB. The browser checks both the file size and the page count before it starts. A file outside those limits is rejected up front, which is faster than a mid-conversion failure. The PDF is read locally by PDF.js once you select it; it is not transmitted to any server, and the conversion only begins after you press the button.
- Choose a rendering scale and a JPEG quality, then click Convert to JPG. Scale controls output resolution: a higher scale produces more pixels and a sharper image but uses more memory. Quality controls the JPEG encoder between 0.60 and 1.00; higher values keep more detail at the cost of file size. Setting the fields does not start the job; the button press does.
- Preview the generated pages and download each JPG separately. Each rendered page appears in the result panel along with its exact pixel dimensions and its own download button. Filenames include a zero-padded page number so the images sort in document order. Changing the file, the scale, or the quality invalidates the previous result, so stale previews cannot be misread as fresh output.
Tuning Scale and JPEG Quality Without Wasting Memory
Two numbers decide almost everything about the output: the render scale and the JPEG quality. They are independent, and they affect very different things. A small PDF page rendered at scale 2.0 produces twice the width and twice the height, which is four times the pixel count of a 1.0 render of the same page. A 2.0 scale on a 40-page document therefore quadruples the work the browser does compared to a 1.0 scale on the same document. Higher scale is useful when the page contains small text you want to read later, or when you plan to print the image, because more pixels preserve fine edges and reduce visible stair-stepping on curves.
JPEG quality, by contrast, cannot invent detail that the source PDF did not contain. Raising it from 0.85 to 1.00 will keep more of the subtle shading in a photograph, but it will not recover a blurry logo or sharpen a low-resolution scan. The trade-off is purely about file size versus visible compression artifacts. For most office documents, slide decks, and screenshots, a quality between 0.85 and 0.92 is a sensible starting point. For archival screenshots where banding shows up in flat regions, push it to 1.00 and accept the larger file.
One last note: the tool does not promise a specific DPI, file size, or print quality. Those outcomes depend on the page dimensions in the source PDF and the visual content on each page. What it does promise is the pixel dimensions of the rendered canvas, which the result panel shows next to each preview.
Browser Safety Limits That Apply Before Conversion Starts
The browser enforces a fixed set of limits to keep the page responsive and prevent a runaway PDF from locking up your machine. They are processing limits, not statements about whether the PDF is trustworthy. A damaged, encrypted, unsupported, or unusually complex PDF can still fail even when every limit is satisfied, and password protection is never bypassed. The table below lists the values the tool itself enforces.
| Limit | Maximum | Why it exists |
|---|---|---|
| File size | 25 MiB | Bounds memory use during PDF parsing |
| Page count | 40 pages | Bounds total rendering work per conversion |
| Per-page dimension | 12,000 pixels on either side | Prevents a single oversized viewport allocation |
| Per-page pixel count | 40 megapixels | Caps any single canvas's pixel buffer |
| Total planned output | 100 megapixels across all pages | Caps the aggregate work before rendering starts |
Picking the Right Output Format for the Same Page
JPG is not always the right target, even when the page needs to become an image. The converter produces JPEG because that is the format the task names, but Lizely runs sibling tools for the cases where JPG is the wrong trade-off. The right choice depends on what you plan to do with the image next.
| Format | When it is the right call | Lizely tool |
|---|---|---|
| JPG | The destination expects a common photographic image, transparency is not needed, and a smaller lossy file is acceptable | PDF to JPG Converter |
| PNG | Lossless output is required for crisp diagrams, screenshots, or anything with sharp text edges | PDF To PNG |
| Long Image | You want every page stacked into a single vertical graphic instead of separate files | PDF to Long Image |
For a deeper comparison of the trade-offs between these formats on a local Windows workflow, the practical guide on converting a PDF to JPG or PNG without uploading walks through the same decision from a different angle.
Pitfalls That Trip Up First-Time Users
A handful of predictable mistakes account for most failed attempts on Windows. Skipping them saves time and produces better output.
- Trying to extract embedded images instead of rendering pages. If you only need the photos inside a PDF, the converter is the wrong tool. The pages get rendered whole, with text and vector backgrounds baked in alongside any photographs. Use a dedicated embedded-image extractor when that is the goal.
- Cranking scale to the maximum and expecting better source content. Higher scale means more output pixels, not more source detail. A 72-DPI scan rendered at scale 4.0 is still a 72-DPI scan in disguise, just with bigger pixels and a bigger file.
- Forgetting that the JPEG is not editable text. Anything you wanted to copy, search, or reflow as text is gone in the output. If the PDF has a real text layer, extracting it to a UTF-8 file first and then turning pages into images is usually the right order of operations.
- Re-clicking Convert and trusting an old result. Changing any input invalidates the old result panel and removes its download buttons. The fix is to click Convert again so the previews match the current settings before you download anything.
- Uploading a password-protected PDF and expecting the converter to crack it. Password protection is not bypassed. The browser hands the file to PDF.js, PDF.js refuses it, and the conversion fails with no preview produced.
Quick Recap
On a Windows machine, the cleanest path from a PDF to a JPG is to stay inside the browser. Open the converter, pick a PDF up to 25 MiB, choose a scale and a quality, press the button, and download each rendered page as its own zero-padded JPEG. The document never leaves your device, the limits are spelled out before the work starts, and the output is a faithful rendering of each page rather than a partial extraction. For lossless work, jump to PNG. For a single stacked graphic, jump to Long Image. For embedded-image extraction, use the dedicated extractor. The original PDF is never changed, and every downloaded file is a newly rendered derivative.
For a deeper look, see JPG to PDF for Multiple Files at Once.