How to Convert PDF Pages to Images: Scenarios, Resolution & Format

Converting a PDF to a set of images is one of those tasks that almost everyone needs to do at some point — but it is rarely obvious which settings produce the right result for the job at hand. Should you choose JPG or PNG? Does 72 dpi look good enough, or do you need 220? Does it matter whether the conversion happens in your browser or on a remote server?

This guide works through the most common real-world scenarios, explains the settings that matter, and shows you how to get the best output every time — using a converter that runs entirely in your browser so your documents never leave your device.

---

The scenarios where PDF-to-image conversion actually helps

Sharing a document page when the recipient cannot open a PDF

Not every situation calls for opening a PDF viewer. When you post in a Slack channel, send a WhatsApp message, or reply on Twitter/X, an inline image is far more likely to be seen than a file attachment. Images render immediately in the feed; PDF attachments require a tap, a download, and a separate viewer. For announcements, event flyers, certificates, one-page summaries, or policy excerpts, converting the page to a JPG and sharing the image removes the friction entirely.

The same logic applies to email. Embedding an image inline in the body of an email gets read more reliably than a PDF attachment that many spam filters flag or that recipients are too busy to open.

Inserting a page into a presentation or a Word document

Microsoft PowerPoint, Google Slides, Keynote, and LibreOffice Impress all let you insert images natively. None of them let you insert a live PDF page that reflows correctly. When you need to embed a page from a technical specification, a legal clause, a financial table, or a product screenshot that exists only in a PDF, converting it to a PNG gives you a high-quality image you can position, resize, and layer on slides without any rendering dependency.

Similarly, Word and Google Docs treat inserted images as first-class objects. You can wrap text around them, add captions, and crop them. An inserted PDF page is harder to work with and can look different across operating systems.

Submitting documents to platforms that only accept image uploads

Government portals, HR systems, freelance marketplaces, university applications, and insurance claim forms frequently limit uploads to JPEG or PNG. The reason is usually that their backend does not have a PDF rendering library and cannot generate a consistent preview. If you need to submit a proof of address, a bank statement page, an ID scan, or a signed consent form, and the form rejects PDFs, converting the relevant page to a JPG is the most straightforward solution.

One tip here: check the platform's maximum file size before choosing your resolution settings. Many upload forms cap files at 2 MB or even 1 MB. At 150 dpi, a typical text-heavy A4 page as a JPG at 90% quality comes in well under 500 KB, which comfortably fits most limits.

Building thumbnail previews for a document library

If you maintain a website or internal tool that lists PDF documents — research papers, product catalogues, company reports — showing a cover thumbnail dramatically improves usability. Users can immediately see what a document looks like before clicking. This is standard practice on academic repositories, legal databases, and real estate listing sites where floor-plan PDFs are common.

Generating a cover thumbnail means converting page 1 of each PDF to a JPG at a modest resolution (72–100 dpi is more than sufficient for a card-sized thumbnail) and saving it alongside the document. The file sizes are small and the visual payoff is significant.

Extracting a figure or chart from a paper or report

Academic papers, financial reports, and technical documents often contain charts that you need for a presentation or a follow-up document. Taking a screenshot of a PDF page works, but the result is limited to your screen resolution and often has the browser chrome or taskbar accidentally captured. Converting the whole page to a high-resolution image and then cropping to the figure in any image editor gives a much cleaner, higher-quality result.

---

Understanding resolution: why DPI is the most important setting

Resolution is expressed in DPI — dots per inch — and describes how many pixels represent each inch of the rendered page. A higher DPI means more pixels, which means sharper detail and a larger file.

Here is a concrete illustration using a standard A4 page (8.27 × 11.69 inches):

Resolution	Approximate pixel dimensions	Typical JPG size	Recommended for
72 dpi (1×)	595 × 842 px	50–150 KB	Web thumbnails, quick chat sharing
150 dpi (2×)	1240 × 1754 px	150–500 KB	Presentations, social media, email
220 dpi (3×)	1820 × 2575 px	400 KB – 1.5 MB	Print, archiving, zoomed-in text
300 dpi (4×)	2480 × 3508 px	1–4 MB	Professional print, large-format

The key insight is that file size grows roughly with the square of the resolution. Doubling the DPI produces roughly four times as many pixels and therefore a roughly four-times-larger file. This is why resolution choice is a genuine trade-off, not just a "higher is always better" decision.

When 72 dpi is enough

For thumbnails in a document library, avatar-sized previews, or low-stakes sharing in chat where the recipient will only glance at the image, 72 dpi is perfectly adequate. On standard HD screens (96 dpi logical resolution), a 72 dpi image looks sharp. Most people will not notice any difference at typical viewing sizes.

When 150 dpi is the sweet spot

For most everyday use — inserting into a slide deck, sharing on social media, attaching to an email for a business contact to read — 150 dpi provides images that look sharp at full screen on any modern monitor and on retina/HiDPI mobile screens. The file sizes are manageable (usually under 500 KB for a text-heavy page), and the quality is noticeably better than 72 dpi when the recipient zooms in.

When you need 220 dpi or higher

If the image will be printed, even on a standard inkjet printer, go to 220 dpi minimum. Printers operate at 300 dpi or higher natively; feeding them a 72 dpi image results in a visibly blurry print. For archival purposes — preserving a document in image form for long-term storage — use 300 dpi to ensure the image is as faithful as possible to the original.

For pages that contain very fine print, dense tables, or small footnotes that readers will need to zoom into, 220 dpi also provides the headroom for digital zoom without pixelation.

---

JPG vs PNG: matching the format to the page content

Both formats are universally supported, but they compress differently, and the right choice depends on what is on the page.

JPG: lossy compression optimised for photographs

JPG achieves its small file sizes by discarding subtle colour information that the human eye struggles to perceive, particularly in areas of gradual colour transition — exactly the kind of content found in photographs, watercolour illustrations, and scanned pages. For a page that is mostly a large image, a JPG at 85–92% quality looks virtually identical to lossless output while being 5–10 times smaller.

The downside of JPG compression is visible artefacts along sharp, high-contrast edges. The block-based encoding algorithm introduces small colour halos and blotches around crisp black lines and text characters. At high quality settings these are barely visible, but at lower quality settings — or when the image is re-compressed multiple times — they become distracting.

PNG: lossless compression optimised for graphics and text

PNG never discards image data. Every pixel in the output file is exactly what was rendered. This makes it ideal for pages dominated by text, line drawings, technical diagrams, code listings, or any content where the sharpness of edges matters. Crisp black text on a white background compresses extremely well with PNG's algorithm (which exploits repeating patterns), so PNG files for text-heavy pages are often only moderately larger than equivalent JPGs.

For pages with large photographic images, PNG files are typically significantly larger than JPGs because PNG does not exploit the same human perception shortcuts that make JPG so efficient on photos.

A simple rule of thumb

• Scanned page or photo-heavy content: JPG at 90% quality
• Text, diagrams, charts, code, line art: PNG
• Mixed content (some text, some images): PNG at 150 dpi or higher, or JPG at 92%+
• Uploading to a form with a strict file size limit: JPG at 85–90%

---

JPG quality: what the percentage actually means

The quality slider in the converter controls how aggressively JPG compression discards information. 100% quality is near-lossless (file sizes comparable to PNG). 50% quality produces very small files with obvious artefacts. The practical range for most uses is 80–95%.

Here is a rough guide:

• 95%+: Near-lossless. Use for archiving or when the image will be re-edited and re-saved multiple times (each re-save of a JPG accumulates artefacts).
• 88–94%: Excellent quality, small visible artefact risk only at pixel-level inspection. Good for professional sharing and presentations.
• 80–87%: Very good quality for on-screen viewing. Small text at the edges of a page might show slight softness. Good for email and web.
• Below 80%: Visible quality loss, especially around text and fine lines. Only justified when file size is severely constrained.

For most purposes, 90% is a safe default — it produces noticeably smaller files than 95% while maintaining quality that holds up at reasonable zoom levels.

---

Why privacy matters: local conversion vs server-based tools

Most PDF conversion tools you find through a search engine work by uploading your PDF to their servers. The workflow is: you select the file, your browser sends it over the internet to their infrastructure, their server renders it and stores the resulting images, and then you download them. This is simple to implement and works fine for publicly available documents.

The problem is that a very large proportion of PDFs people want to convert are not public documents. Consider the kinds of PDFs that appear in day-to-day life:

• Monthly bank statements and credit card bills
• Pay stubs from your employer
• Tax returns and filings
• Tenancy agreements and property contracts
• Medical letters, test results, and prescriptions
• Identity documents and passports
• NDAs and commercial contracts
• Due diligence materials and financial models

Uploading any of these to a third-party server involves a transfer of trust. You are trusting that the service encrypts the upload in transit (not all do). You are trusting that the file is deleted after conversion and not retained (privacy policies are often vague on timelines). You are trusting that their infrastructure is secure and not subject to a breach that could expose your document. You are trusting that a future owner of the service, if it is acquired, honours the same privacy commitments.

What local conversion means in practice

The PDF to JPG converter on sourcecodestack runs entirely inside your browser using PDF.js, Mozilla's open-source rendering library. When you select a PDF:

1. The file is read from your disk directly into browser memory — it does not go to any server.
2. PDF.js parses the file structure and renders each page onto an HTML canvas element inside your browser tab.
3. The browser converts the canvas to image data and makes it available as a download link.
4. Nothing is transmitted over the network except the JavaScript code that powers the tool, which was already downloaded when you loaded the page.

You can confirm this with your own browser. Open the Network panel in developer tools (F12 in most browsers), start a conversion, and watch: there will be no outgoing request carrying your PDF. The conversion is computationally local from start to finish.

This is not a privacy policy claim — it is a technical constraint of the architecture. There is no server in the loop that could retain or misuse your document.

---

Common mistakes and how to avoid them

Converting when you should be using the PDF

The single biggest mistake is converting a PDF to images when the recipient actually needs the original PDF. Once you rasterize a page, the text is gone as machine-readable data. The recipient cannot select a word, search for a clause, copy a paragraph, or have a screen reader read it to them. If the use case involves reading, searching, editing, signing, or archiving for compliance, keep the document in PDF form.

Choosing too low a resolution for print

Many people pick Standard (72 dpi) because it is fast and produces small files, then are surprised that the printed output looks blurry. A printer working at 300 dpi receives a 72 dpi image and has to scale it up roughly 4×, which produces visible pixelation. For anything that will be physically printed, use at least 220 dpi and ideally 300 dpi.

Using JPG for text-heavy pages at low quality

If you set quality below 85% on a page with small text or fine lines, JPG artefacts cluster around the edges of characters and make the text look fuzzy even at normal viewing size. Either raise the quality to 90%+ or switch to PNG.

Forgetting to check platform file size limits before converting

Some upload forms enforce strict limits (1 MB, 2 MB). If you convert at Very high resolution and end up with a 3 MB file, you will have to reconvert at a lower resolution or higher compression. Check the platform's limits first and work back to the appropriate settings.

---

Step-by-step: converting a PDF using the sourcecodestack tool

1. Open the PDF to JPG converter in your browser.
2. Choose your output format — JPG for smaller files, PNG for lossless quality.
3. Choose your resolution — Standard (72 dpi) for quick web use, High (150 dpi) for everyday sharing, Very high (220 dpi) for print.
4. If you chose JPG, adjust the quality slider. 90% is a reliable starting point.
5. Click the upload area and select your PDF file. The file is never sent to any server.
6. Watch the progress indicator as each page is rendered.
7. When conversion is complete, preview each page thumbnail.
8. Download individual pages by clicking their download button, or use Download all to save every page at once.

There is no account required, no watermark added, and no page limit. The tool is completely free.

---

Frequently asked questions

Can I convert just one page of a multi-page PDF? Yes. After conversion, all pages are shown as individual thumbnails. You can download only the pages you need by clicking their individual download buttons.

Will the converter work on a phone or tablet? Yes. PDF.js runs in any modern browser including mobile browsers on iOS and Android. The rendering may be slower on older devices for large PDFs.

Is there a file size limit? The tool has no explicit file size limit, but very large PDFs (100+ pages at high resolution) will take longer to render because all processing happens on your device. For practical speed, consider working with the pages you need rather than a full document.

What happens if the PDF is password-protected? The converter needs to be able to read the PDF. If the document requires a password to open, you will need to enter the password or remove the protection before conversion. The tool does not decrypt password-protected files.

Does the image quality degrade if I convert the same PDF multiple times? No. Each conversion renders the page fresh from the PDF's vector and text data. Unlike re-saving a JPG (which accumulates artefacts), re-running the converter produces a clean render every time.

---

Summary

Converting PDF pages to images is a practical skill with a handful of genuine decisions inside it. The most useful things to remember:

• Use JPG for photographs and scanned pages; use PNG for text and diagrams.
• 72 dpi for web thumbnails, 150 dpi for everyday use, 220 dpi+ for print.
• JPG quality of 90% is a reliable default that balances file size and visual quality.
• Never convert when you need selectable text — images cannot be searched, copied, or read by screen readers.
• Local, browser-based conversion means your document never leaves your device, which matters for any private or sensitive file.

The PDF to JPG converter on sourcecodestack covers all of these scenarios — free, private, and without requiring an account.