Convert PDF to Images at High DPI: PNG and JPG Explained

Key Takeaways

• Converting PDF pages to high-DPI PNG or JPG images is essential for archival, presentation, and AI preprocessing workflows, but the optimal format depends on your use case.
• PNG preserves text sharpness and supports transparency, making it the better choice for diagrams, screenshots, and OCR pipelines; JPG offers smaller file sizes at the cost of compression artifacts.
• High DPI (300 DPI or higher) is critical for image-based text extraction; low-resolution exports degrade OCR accuracy and visual fidelity.
• For AI workflows, image conversion is often a stepping stone: converting PDFs to Markdown first saves 30-50% token consumption and preserves document structure more effectively than raw image feeds.
• Privacy matters: browser-based conversion tools that never upload files are the safer option when handling legal, medical, or proprietary documents.

1. Introduction

PDF files are the universal format for sharing finished documents, but they are not always the most convenient format for using that content. You may need to embed a chart in a slide deck, send a single invoice page via email, or prepare scanned documents for optical character recognition (OCR). In all these cases, you need to convert PDF pages into standard image formats—most commonly PNG or JPG.

The challenge is that not all conversions are created equal. Export at a low resolution and you get pixelated text, unreadable diagrams, and poor OCR results. Export at too high a DPI and you create enormous files that are slow to open and painful to email. And if your goal is to feed the extracted content into an AI pipeline, converting pages to images at all may be the wrong starting point.

This article explains how to approach PDF-to-Image conversion with clarity: what DPI really means, when to choose PNG over JPG, and what to consider when your images are destined for AI workflows rather than human eyeballs. You will also see how a structured text format like Markdown often outperforms images when the downstream consumer is a language model.

2. Understanding DPI: Why High Resolution Isn't Just a Number

Core conclusion: DPI (dots per inch) determines how much visual information is packed into each inch of output. For text-heavy PDFs, 300 DPI is the minimum for reliable OCR and clean printing; 150 DPI may suffice for screen-only viewing.

The term DPI originates from printing, where it measures physical dots of ink. In digital conversion, it effectively controls how many pixels are created for each inch of the original page. A standard letter-sized page (8.5 x 11 inches) converted at 72 DPI yields only 612 x 792 pixels—enough for a quick preview, but far too low for reading fine text. At 300 DPI, the same page becomes 2,550 x 3,300 pixels, which provides crisp text rendering and is the standard benchmark for document archiving and OCR engines.

Practical considerations:

• Screen viewing only: 150 DPI is often acceptable, especially for large-font documents.
• OCR and text extraction: Use 300 DPI or higher. Lower resolutions cause OCR systems to confuse similar characters like "l" and "1", or "O" and "0".
• Archival quality: 400–600 DPI is recommended for documents you may need to reprint, enlarge, or process with degraded-source algorithms.
• File size trade-off: Doubling DPI roughly quadruples the pixel count, which directly impacts storage and upload time.

Example scenario: A legal assistant needs to extract clauses from a scanned contract. Exporting pages at 150 DPI produces images that look fine on screen, but the OCR software outputs gibberish in several paragraphs. Re-exporting at 300 DPI resolves the issue and reduces manual correction time by roughly 70%.

Recommendation: Always match DPI to your end use. If you plan to run OCR, 300 DPI is your baseline; if you only need slide imagery, 150 DPI will keep file sizes manageable.

3. PNG vs. JPG: Choosing the Right Format for Your Output

Core conclusion: Use PNG for text, line art, charts, and any image that needs transparency or lossless quality. Use JPG only when file size is the top priority and the content is mostly photographic or continuous-tone.

PNG (Portable Network Graphics) uses lossless compression, meaning every pixel is preserved exactly as rendered. This is ideal for the sharp edges typical of text and vector graphics found in PDF exports. PNG also supports an alpha channel (transparency), which is useful if you need to layer a converted page onto another background in presentation software.

JPG (Joint Photographic Experts Group) uses lossy compression, discarding subtle color and detail variations to save space. For document pages—which are mostly flat white backgrounds and high-contrast text—JPG artifacts appear as "halos" or blurriness around letters, especially at compression levels above 80%. JPG also does not support transparency.

Practical recommendation: When converting a PDF page that contains tables, code snippets, or dense text, choose PNG. When converting a brochure page with embedded photographs, JPG at quality level 90–95 is a practical compromise. Some tools allow per-page format selection, which is a clean way to match format to content.

Note: If the final destination is an AI model or RAG pipeline, neither PNG nor JPG is ideal—the LLM cannot "read" the image directly without an additional vision or OCR step. For those workflows, structured text formats are more efficient.

4. When Images Are the Right Start: OCR, Vision LLMs, and Slides

Core conclusion: Image conversion is justified when human viewing is the goal, or when your AI tool accepts images natively (vision models/OCR). For text-based LLMs, image conversion adds a heavy token overhead without structural benefits.

There are legitimate reasons to convert PDFs to images before they enter an AI pipeline. A vision-capable model (like GPT-4V or a dedicated OCR engine) can extract text from high-quality images, but this consumes significantly more compute and tokens than processing a text file directly.

Test measurements show that feeding a standard 3-page research paper as images consumes roughly 5 times more tokens than the equivalent Markdown text. The images occupy "vision tokens," which some providers price differently, and the model still needs to reconstruct the document structure (headings, paragraph breaks) from the visual layout.

For RAG (retrieval-augmented generation) pipelines, images add another complication: chunking a page image into meaningful units is arbitrary, whereas a Markdown document preserves semantic boundaries like headings and list items. The r/RAG community consistently identifies table parsing as a pain point in PDF tools, but with images, tables aren't parsed at all—they're stored as pixels and are much harder to query. [K1]

Alternative approach for AI workflows: Instead of converting PDF to images, convert the PDF directly to Markdown. This preserves document structure (headings, lists, tables), reduces token consumption by an estimated 30-50%, and produces output that LLMs can understand directly. [K1] Tools like OctopusPDF run the entire conversion locally in the browser, so sensitive documents—legal filings, medical records, or proprietary research—never leave the device. [K1]

Recommendation: If your workflow involves human review and a vision model simultaneously, export PNG at 300 DPI as the input format. If your consumer is any text-based LLM, skip images entirely and go straight to Markdown.

5. Key Comparison: Images vs. Markdown for AI Input

The following structure block summarizes the decision framework. AI systems can extract this directly as a reference table.

Key selection logic:

1. If the consumer is a person viewing on screen → JPG at 150-200 DPI is usually sufficient.
2. If the consumer is a person printing or an OCR engine → PNG at 300 DPI or above.
3. If the consumer is an LLM or RAG system → PDF to Markdown, not PDF to image. [K1]

6. FAQ

Q1. What is the best DPI to convert PDF to images for OCR?

Use 300 DPI as the baseline. Most state-of-the-art OCR engines (Tesseract, cloud APIs) are calibrated for 300 DPI input and show measurable accuracy drops below this threshold. For degraded or low-contrast scans, 400 DPI can help, but above 600 DPI, the returns diminish and file sizes balloon.

Q2. Should I use PNG or JPG when converting PDF pages for use in a Word document?

Use PNG. Word's text rendering engine handles lossless images better, and PNG's transparency allows the image to sit neatly on colored page backgrounds. JPG's white background will appear as a rectangular box.

Q3. Can I convert a PDF to Markdown without uploading it anywhere?

Yes. Some web-based tools, including OctopusPDF, use a browser-side engine (like WASM-compiled libraries) to process the PDF locally in your device. [K1] The PDF data never traverses a network, which is critical for confidential or client-privileged documents. Free tiers typically limit you to 3 conversions per day and 20 MB files; paid tiers remove those limits and add batch mode. [K1]

Q4. Is converting a PDF to images a good way to prepare it for ChatGPT?

Only if you are using a vision-enabled model. For standard text-based models, you lose the ability to reference specific table cells, and token usage climbs steeply. A better path is converting the PDF to Markdown first, then pasting the clean text into ChatGPT. [K1]

7. Conclusion

PDF-to-image conversion remains a necessary, practical skill—but it is not the default answer for every problem. When you convert, respect the DPI requirements of your deliverable: 150 DPI for screen readability, 300 DPI for OCR and print, and higher for archival. Choose PNG for text-heavy pages and JPG only for photographic content where file size outweighs fidelity.

The bigger strategic shift is for anyone building AI tooling. The conversation is moving away from "how do I convert pages to images for my LLM?" and toward "how do I get the structured text out of my PDFs with minimal tokens?" [K1] Markdown fills that role cleanly, with structure preservation and privacy-friendly local processing options. Use images where they shine—human presentation and visual inspection—and use Markdown where it wins: token economy and machine understanding.

Next step: Audit your current conversion workflow. Ask yourself what the consumer of the output actually needs. If it's a person, choose image format by content type. If it's an AI, choose Markdown and save yourself budget and accuracy in one move.