keptlocal
· 6 min read · PDFImages

PDF to JPG: When (and When Not) to Convert

HM
Hiten Mahalwar
Founder, keptlocal · Technical Lead, Healthcare IT

PDF to JPG conversion is one of the most-requested file operations online — and one of the most misused. Converting a text-based PDF to a series of JPEG images discards everything that makes a PDF valuable: the ability to search it, copy text from it, read it with a screen reader, and compress it efficiently. Before you convert, it is worth asking whether you should.

What you give up when you convert PDF to JPG

A PDF containing text stores that text as actual characters — a stream of Unicode code points associated with font data and position information. This means:

  • Text is selectable and copyable. You can highlight a paragraph and paste it elsewhere.
  • The document is searchable. Ctrl+F finds any word in the file, and search engines can index the text.
  • Screen readers can read it. Accessibility tools parse the text stream to render audio output for visually impaired readers.
  • The file is compact. A page of text as PDF might be 50–200 KB. The same page rendered at 150 DPI and saved as JPEG might be 300–800 KB. Images are larger than the text they represent.
  • It scales without degradation. Vector text in a PDF is resolution-independent. Zoomed to 400%, it is still sharp. A JPEG zoomed to 400% shows pixels and compression artefacts.

When you convert a PDF to JPG, you get a photograph of the document. That photograph is less functional, larger, and lower quality than the PDF it came from — for most use cases.

When PDF to JPG conversion is the right choice

Embedding PDF content in a document that does not support PDFs

Word documents, PowerPoint slides, and Google Docs cannot embed a PDF as a native object that renders correctly across all viewers. Converting the relevant PDF page to a high-resolution JPG and inserting it as an image is the reliable workaround. Use the Best quality setting (3× scale, ~216 DPI) to keep text legible when the image is scaled down in the presentation.

Sharing a page on social media or messaging apps

Social platforms accept images universally; PDF uploads are unsupported on most consumer platforms (Twitter, Instagram, WhatsApp). Converting a single relevant page to JPG is the standard workflow for sharing document content on these platforms.

Creating a preview thumbnail

Web applications that handle document uploads often display a thumbnail preview of the first page. The thumbnail generation pipeline — whether in a CMS, a document management system, or a custom app — typically converts the first page to a JPEG. A standard quality setting (1.5× scale) is sufficient for thumbnails.

Sending a document you do not want the recipient to modify

A JPEG cannot be edited with standard text editors or PDF tools. Converting a finalised document to images before sending is a crude form of content protection — the recipient can view it but cannot easily extract and reuse the text. This is particularly common for final invoices, certificates, and formal notices. Note that this is not security: the text is visible and can be transcribed or OCR'd. It is a deterrence, not a barrier.

Working with PDF viewers that render incorrectly

Some legacy or embedded PDF viewers struggle with complex PDFs: unusual fonts, transparent layers, form fields, or non-standard PDF versions. Converting to images bypasses the rendering chain entirely — what you see is what the conversion tool rendered, independent of the viewer's interpretation.

The source PDF is already a scan

A scanned PDF is already a sequence of images. The PDF wrapper adds structure but the underlying content is pixels, not selectable text (unless OCR has been applied). Converting a scanned PDF to JPG extracts those underlying images with no meaningful loss — you are just changing the container format. In this case, the trade-offs listed above do not apply.

How to convert PDF to JPG without uploading the file

The keptlocal PDF to JPG tool renders each page using pdf.js — the same PDF rendering engine used in Firefox — and exports them as JPEG images. The rendering happens inside your browser; no file is uploaded to a server.

Choose the quality setting based on how you will use the images:

  • Standard (1.5× scale, ~108 DPI): suitable for screen display, thumbnails, and social media sharing. File sizes are small — typically 100–400 KB per page.
  • High (2× scale, ~144 DPI): good for email attachments, presentation embeds, and web content. A clear step up in quality without the file size of the Best setting.
  • Best (3× scale, ~216 DPI): the closest you can get to print quality from a browser-based converter. Use this for any context where the image will be displayed at sizes larger than the original page — a zoomable web viewer, a printed handout, a high-resolution embed.

A single-page PDF downloads as a single JPEG. Multi-page PDFs download as a ZIP archive containing one JPEG per page.

Alternatives to conversion worth considering

Before converting, consider whether one of these meets your need without discarding the PDF's capabilities:

  • Share the PDF directly. Every modern operating system and most mobile devices have native PDF viewers. Email clients display PDFs as attachments. Slack, Teams, and most professional messaging tools show PDF previews. Unless there is a specific reason JPG is required, the PDF is usually the better share format.
  • Use your PDF viewer's screenshot function. Most viewers let you select a region and copy it to the clipboard as an image. This gives you exactly the part of the page you need without converting the whole document.
  • Export at source. If the PDF was generated from Word, PowerPoint, or a design tool, re-export from the source application as an image. The source application's image export pipeline typically produces better results than PDF-to-image conversion because it bypasses the PDF rendering step entirely.

Quality expectations and browser limitations

pdf.js renders PDFs using the browser's graphics pipeline. The quality of the output is limited by:

  • Font rendering: if the PDF embeds unusual or proprietary fonts, pdf.js may substitute a standard font for rendering. The layout will usually be correct, but the exact letterforms may differ from a native PDF viewer.
  • Transparency and blend modes: complex transparency effects in PDFs occasionally render differently across different PDF engines. pdf.js handles standard cases well.
  • Very large PDFs: rendering at Best quality (3×) is memory-intensive for large page sizes. A tabloid-size (A3) page at 3× scale produces a canvas of approximately 3500 × 5000 pixels — around 50 megapixels. This is within browser limits on most devices but may take several seconds per page.

Convert your PDF pages to images in your browser — no upload, no watermark, no account — with the keptlocal PDF to JPG tool.