PDF vs JPG: When to Convert and When to Stay

June 20, 2026 · JPG.now Editorial · Format Comparisons

PDF vs JPG: When to Convert and When to Stay

You are about to email a signed lease to a tenant. You exported the contract as a JPG from your phone scanner app because that is what came up first in the share sheet. The tenant emails back a polite "could you send a PDF?" and now you are juggling three apps trying to convert a stack of JPGs into one document without flattening the signatures. This is the dance most people do, more often than they admit, because picking the right format upfront feels harder than it actually is.

PDF and JPG solve different problems, but they overlap enough that people convert between them constantly — often in the wrong direction. A PDF is a page, designed to be printed or read as a document. A JPG is an image, designed to be displayed or embedded. Picking the right one in the first place saves you a conversion step; picking the wrong one and converting later usually costs quality, searchability, or both.

Background: what each format is built for

PDF, invented by Adobe in 1993, packages text, vector graphics, embedded fonts, and raster images into a single file that renders identically on any device. The text inside a PDF is selectable, searchable, and indexable by Google. It supports multiple pages, hyperlinks, form fields, and digital signatures. Typical sizes range from 50 KB for a one-page invoice to 30 MB for a fully laid-out magazine.

JPG, the format we all know, dates back to 1992 and was designed for photographic compression. It is a single rasterized image with lossy compression. It is small, universally supported, and ideal for photographs. It cannot contain selectable text, cannot be multi-page, and cannot be signed. Typical sizes are 100 KB to 4 MB depending on resolution and quality.

The formats coexist because they have non-overlapping strengths. Trying to use one for the other's job is what creates round-trip mess.

Use PDF when

  • The document has text you want to keep searchable. Contracts, manuals, resumes, reports.
  • Layout precision matters. Invoices, tickets, certificates, anything where pixel-perfect positioning of letters across devices matters.
  • You need multiple pages in one file. Portfolios, ebooks, brochures.
  • The recipient will print it. Print drivers handle PDFs much better than JPGs.
  • Forms or signatures are involved. DocuSign, Adobe Sign, and HelloSign all consume PDF.

Use JPG when

  • It is a photograph, period. Camera output, social media uploads, product listings.
  • You need it inline on a webpage. Browsers display JPGs natively; PDFs require a plugin or new tab.
  • The image is decorative. Hero images, background art, blog post illustrations.
  • Email attachment size matters. A 200 KB JPG opens on every phone; a 12 MB PDF does not.
  • You are texting it to your mom. She wants to see a photo, not download a PDF.

Step-by-step: the conversion you actually need

  1. Identify the source. Is it a phone scan, a screenshot, an exported document, or a real photograph? Phone scans almost always belong in PDF.
  2. Identify the destination. Will it be printed, signed, embedded inline, or archived?
  3. Pick the direction. Scanned pages going to a filing system: JPG -> PDF via JPG to PDF. Page extracted from a manual for a blog post: PDF -> JPG via PDF to JPG.
  4. Choose the page range. Most converters let you select pages — extract only what you need.
  5. Set the resolution. 150 DPI for screen viewing, 300 DPI for print, 200 DPI if you are unsure.
  6. Run the conversion. Wait. Multi-megabyte PDFs can take 30 seconds.
  7. Optimize the output. JPG output goes through Compress JPG; PDF output goes through a PDF optimizer.
  8. Verify before sending. Open the file on a different device or browser to confirm it renders as expected.

Common conversion scenarios that actually make sense

Scanned documents: JPG to PDF

You scanned a contract or receipt as a JPG (or your phone camera did). The right destination is almost always PDF — it preserves the multi-page nature of the scan, prints cleanly, and integrates with your filing system. Push the JPGs through JPG to PDF and you get a single multi-page document. Add OCR after that if you need the text searchable.

Portfolio image extraction: PDF to JPG

A photographer sends you a 40-page PDF portfolio. You want to grab page 12 for a moodboard. Convert with PDF to JPG and you get one image per page that you can drop into Pinterest, Notion, or Figma. Set the export DPI to 150 for screen use, 300 for print reuse.

Product manual screenshots

You are writing a blog post and need to show a diagram from a 200-page manufacturer PDF. Converting the entire PDF is overkill — most converters let you extract a page range. Pull pages 47 to 48, convert to JPG, embed in your post.

Web display of contracts

If you must show a contract on a webpage and worry that visitors will not click a PDF link, convert page 1 to JPG and use it as a preview thumbnail that links to the actual PDF. Best of both worlds.

Common mistakes and their fixes

  1. Mistake: Converting a text-heavy PDF to JPG and losing searchability. The PDF had selectable text; the JPG has none. Fix: keep the PDF and generate a JPG preview, do not throw away the source.
  2. Mistake: Converting a JPG to PDF when the recipient wanted to see it inline. You sent an "image" but they have to download and open a document viewer. Fix: ask first or default to JPG for photographic content.
  3. Mistake: Letting JPG quality drop during round-trips. JPG to PDF to JPG to PDF compounds compression artifacts. Fix: pick one direction and keep the highest-quality master.
  4. Mistake: Forgetting OCR. A PDF of scanned pages is just a stack of images until you OCR it. Fix: use Image to Text on the JPG version if you need extracted text.
  5. Mistake: Embedding 600 DPI scans when 150 is enough. Bloats the file by 16x. Fix: scan at the resolution you actually need.
  6. Mistake: Using JPG for receipts with critical numbers. Compression artifacts can blur small text. Fix: PDF preserves crisp text regardless of zoom.

Real-world examples

Apple's App Store listing requirements ask for screenshot JPGs because the listing is a visual display. Try uploading a PDF and the form rejects it. The right call here is JPG, period.

IRS tax filings require PDF because the form layout, signatures, and field values need to be preserved exactly. A JPG of the same form would not be accepted.

Etsy product pages accept JPG only — submitting a PDF gets the listing rejected. Etsy sellers using a designer who sends PDFs need a conversion step via PDF to JPG before upload.

Format comparison at a glance

PropertyPDFJPG
Multi-page supportYesNo
Selectable textYesNo
Searchable contentYes (if text-based)No (without OCR)
Native browser displayPlugin/new tabInline
Email attachment sizeLargerSmaller
Print fidelityBestOK
Form fields / signaturesYesNo
Compression efficiency for photosDecentBest

File-size considerations

A 10-page PDF of mostly text might be 200 KB. The same content as 10 separate JPG screenshots could easily be 8 MB — text rasterized as JPG also looks fuzzy at the edges because JPG was designed for photos, not crisp glyphs. This is why "save the report as JPG" is almost always the wrong instinct.

Conversely, a PDF that wraps a single high-resolution photograph can balloon to 15 MB when the same photo as JPG would be 1.5 MB. PDF is doing extra work that does not help you.

SEO and accessibility differences

Google indexes both PDF and JPG, but in different ways. PDFs surface in regular web search with their internal text contributing to ranking. JPGs surface in Image Search, ranked partly by alt text and surrounding page context. If you want a brochure to be findable via "best 2026 product guide," ship it as PDF. If you want it findable via image searches for the cover, ship the cover as JPG.

Screen readers handle PDF text natively if the PDF is properly tagged. A scanned PDF with no OCR is just as inaccessible as a JPG. Both need explicit alt text or document-tagging work.

Advanced tips

  1. Use PDF/A for archival. The /A subset embeds all fonts and disables external dependencies — a contract from 2026 will render the same in 2046.
  2. Linearize PDFs for web display. A linearized PDF starts rendering page 1 before the whole file downloads.
  3. Generate a JPG cover thumbnail from any PDF by converting page 1 only; ship as the OG image so link cards on Twitter and LinkedIn show a real preview.
  4. Combine multiple JPGs into a single PDF via drag-and-drop in JPG to PDF rather than emailing five attachments.
  5. Strip metadata from JPGs before converting to PDF with Compress JPG so the resulting PDF does not carry EXIF GPS data.
  6. Use the image info tool to verify DPI before you commit a PDF to print.
  7. Pre-shrink JPGs before bundling. A 10-image PDF where each JPG is 4 MB is a 40 MB PDF. Run through compress image first.

FAQ

Can I edit text inside a JPG?

Not directly. You need OCR via Image to Text first, then edit the extracted text in a word processor.

How do I make a PDF from multiple JPGs in one shot?

Upload all JPGs to JPG to PDF, drag to reorder, and export. The tool handles the merge.

Does converting PDF to JPG lose quality?

It rasterizes vector content, so logos and text become pixel-based. At 300 DPI the loss is invisible on screen.

Why does my PDF look fine on screen but pixelated when printed?

The embedded images are likely 72 DPI. Re-scan or re-export at 300 DPI for print.

Can I password-protect a JPG the way I can a PDF?

Not natively. JPG has no encryption layer. Wrap it in a password-protected PDF if confidentiality matters.

How big should a JPG be for a typical PDF page?

For 8.5x11 at 200 DPI, roughly 1,700 by 2,200 pixels. Anything larger is wasted.

Can I extract a single page from a PDF as JPG without converting the whole file?

Yes — most converters accept a page range. Specify "page 7" and you get a single JPG.

The two-question decision

  1. Will the recipient need to select, search, or print the text?
  2. Will the file be displayed inline on a webpage or in a chat?

If the answer to question 1 is yes, choose PDF. If the answer to question 2 is yes, choose JPG. If both are yes, ship both: a PDF for the document, a JPG cover for the link card. Convert in either direction through JPG to PDF or PDF to JPG, and run the result through the image converter if you need a final format swap. Pair with compress JPG for output optimization. Pick the right one up front and you skip the round-trip entirely.

PDF/A and long-term archival

For documents that need to be readable in 20 or 30 years, the PDF/A subset is the right target. PDF/A embeds every font, prohibits external dependencies (no streaming video, no JavaScript), and locks down the rendering instructions so the document looks identical decades from now. The trade-off is larger file size — typically 1.5 to 2x a normal PDF — and slightly slower export. For legal contracts, medical records, and government filings, the size premium is worth the durability guarantee.

JPG has no archival subset because it never needed one. A JPG from 1995 still opens in any image viewer today. The format is so simple that it has effectively zero risk of becoming unreadable. The lesson: pick PDF for documents and JPG for photos, and you avoid the entire question of format rot for the lifetime of the file.

OCR: making a JPG searchable

If you have a JPG of a page of text and want the text extracted, OCR is the path. Modern OCR engines (Tesseract 5, Google Document AI, AWS Textract) hit 98 to 99 percent accuracy on clean printed text and 80 to 90 percent on handwriting. The output is usually plain text or hOCR (HTML with bounding boxes), which can be embedded into a PDF to produce a searchable document.

Push your JPG through Image to Text for a quick extraction, then paste into your document system. For batch jobs (a folder of scanned receipts), command-line Tesseract handles 100+ images in minutes. If accuracy is critical — legal discovery, contract review — pay for a commercial OCR service; the cost per page is under 5 cents and the accuracy bump is real.

Hybrid workflows: PDF with embedded JPGs

A common confusion is the assumption that PDF and JPG are mutually exclusive. A PDF can contain JPG-compressed images alongside vector text — that is how every camera-scanned PDF is structured. Photoshop's "Save As PDF" wraps a single JPG inside a PDF wrapper, giving you both the per-image compression of JPG and the document-management features of PDF.

The downside is that the wrapped JPG can be over-compressed by some PDF exporters, producing visible artifacts in the final document. If quality matters, export the original at JPG quality 95 first, then embed in the PDF without further re-compression. The Compress JPG tool lets you control quality precisely before embedding.

Some professional workflows take this further by generating a PDF/X file — a print-publishing variant that enforces CMYK color, embedded fonts, and specific image resolution minimums. PDF/X is what commercial printers ask for when you submit camera-ready artwork. The difference vs. a standard PDF is invisible on screen but prevents the printer from rejecting your file at press check.

Mobile camera scans: the modern convergence

The line between JPG and PDF gets blurriest on mobile. Apple's built-in Notes scanner, Microsoft Lens, Adobe Scan, and Google Drive's scanner all let you snap a JPG and convert to PDF on-device in one tap. The output is a multi-page PDF with cleaned-up perspective correction and contrast enhancement. This is the right default for most document capture today.

The trick is choosing the output format thoughtfully. Save as JPG when you want to share a single page inline (text message, Slack). Save as PDF when you want to file the document for records or send to someone who will print it. The tools default to PDF when multiple pages are captured, which is the correct heuristic. The error case is single-page scans saved as PDF when JPG would have been the better social-share format.

PDF compression and image-heavy documents

A common pain point: a PDF balloons to 40 MB because every embedded image is uncompressed or near-uncompressed. PDF optimizers like Ghostscript, Adobe Acrobat Pro, and pdfcpu can recompress embedded images in-place, often shrinking the file by 60 to 90 percent with no visible quality change. The Ghostscript command gs -sDEVICE=pdfwrite -dPDFSETTINGS=/ebook -o out.pdf in.pdf handles the common cases.

For PDFs you generate yourself, control the embedded image quality at export time rather than recompressing later. Word, Pages, Google Docs, and InDesign all expose a quality slider for embedded images during PDF export. Quality 85 is the safe default; below 75 produces visible artifacts in screenshots and diagrams. If the PDF is intended for print, use quality 95 or higher and embed at 300 DPI.

← All articles