Initializing... drag & drop files here
Supports: PDF
PDF is a container for vector text, embedded fonts, and layered images — ideal for printing and archival, but image editors, social platforms, and chat apps can't open it inline. Converting each page to JPEG rasterizes the document into a flat image that any tool can display, edit, or embed. The.jpeg extension specifically (not.jpg) is the form most macOS and Linux native screenshots use, and it's what some workflow systems and content-management pipelines expect to see when extensions are matched literally.
.jpeg extension — Some CMS uploaders, government e-filing portals, and asset-validation scripts compare extensions byte-for-byte; if the spec says .jpeg, .jpg may be rejected even though the file bytes are identical.If your downstream tool expects the three-letter extension, the sibling page PDF to JPG produces identical bytes with a .jpg suffix. For sharp text and diagrams, use PDF to PNG instead.
| Property | .jpeg | .jpg |
|---|---|---|
| Underlying format | JPEG / JFIF (ISO/IEC 10918) | JPEG / JFIF (ISO/IEC 10918) |
| File bytes | Identical | Identical |
| Origin of the suffix | UNIX, macOS, modern Windows | MS-DOS 8.3 / FAT-16 three-letter cap |
| When to choose it | Strict pipelines, native macOS screenshots, web pipelines that normalize to .jpeg |
Default for most Windows tools, Photoshop, GIMP, and most web hosts |
| Interchangeable? | Yes — rename either way and the file still opens | Yes |
Both extensions decode the same JPEG bitstream. The three-letter .jpg is a relic of MS-DOS and early FAT filesystems that capped extensions at three characters; UNIX and Mac never had the cap, so they kept .jpeg. Today the choice is purely cosmetic unless a specific tool or upload spec demands one form.
| DPI | Pixel dimensions | Typical JPEG size | Use case |
|---|---|---|---|
| 72 DPI | 612 × 792 | 50-150 KB | Web thumbnail, file-manager preview |
| 96 DPI | 816 × 1056 | 100-250 KB | Email inline, blog body image |
| 150 DPI | 1275 × 1650 | 200-600 KB | Screen viewing, slide embeds |
| 200 DPI | 1700 × 2200 | 400 KB-1 MB | OCR source, document portals |
| 300 DPI | 2550 × 3300 | 800 KB-2 MB | Print, magazines, photo paper |
| 600 DPI | 5100 × 6600 | 3-8 MB | Archival, fine-art reproduction |
| 1200 DPI | 10200 × 13200 | 12-30 MB | Forensic, museum-grade scans |
File-size estimates assume Very High quality on a mixed text-and-photo page. A pure-text page compresses much smaller; a full-bleed photo page can run larger.
No. They are the same format — JPEG / JFIF as defined by ISO/IEC 10918 — with two different filename extensions. The .jpg form exists only because MS-DOS and the FAT-16 filesystem capped extensions at three characters, so Windows tools historically dropped the trailing e. UNIX, classic macOS, and modern Windows all accept either. Rename photo.jpeg to photo.jpg (or vice versa) and every viewer still opens it.
Three real reasons. First, some upload validators and CMS pipelines match extensions literally — if the spec says .jpeg, a .jpg file gets rejected even though the bytes are identical. Second, macOS native screenshots and some Linux tools default to .jpeg, so picking the same extension keeps your folder consistent. Third, certain government e-filing and archival workflows publish style guides that prescribe .jpeg. If your downstream tool doesn't care, .jpg is the more common default — use PDF to JPG for that.
For screen viewing, slide decks, and email, 150 DPI is the sweet spot — sharp on any laptop or phone display without inflating file size. For print, use 300 DPI (the industry standard for offset and inkjet output). For tiny web thumbnails or file-browser previews, 72 or 96 DPI is enough. Going above 300 DPI only pays off if you'll zoom, crop, or print larger than the original page.
Yes. A 10-page PDF produces 10 JPEG images, one per page, named by page index. Download them individually or grab the full set as a ZIP. To combine them back into a single multi-page file, use Merge Image to PDF. To stitch them into one tall image, open them in any image editor and paste vertically.
No. JPEG is a flat pixel grid — text becomes part of the image and can no longer be selected, copied, or searched. If you need a searchable copy, keep the original PDF (it already has a text layer if it wasn't a scan), or run OCR on the JPEG output afterward. For preserving text plus layout, use PDF to DOCX instead.
Two usual causes. First, DPI is too low — bump from 72 to 150 or 300. Second, JPEG's lossy DCT compression creates soft halos around sharp text edges; that's inherent to the format. For text-heavy pages, switch to PNG (lossless) via PDF to PNG, or raise the Quality Preset to Very High to push the artifacts down to barely-visible.
JPEG has no alpha channel — it cannot store "transparent" pixels. If your PDF page has transparent regions (common in PDFs exported from Illustrator, InDesign, or Figma), the rasterizer must paint them onto a solid background before encoding. White is the default and matches most printed paper; pick black, gray, or another color from the dropdown if the rest of your design assumes a different page color.
No hard caps in normal usage. Conversion runs on our servers, so very large PDFs (hundreds of pages or hundreds of megabytes) are limited mainly by upload size and connection speed. If a 500-page book at 600 DPI exhausts RAM, drop to 150 DPI or split the PDF into chunks first with Split PDF.
Files transit to xconvert's processing edge for rasterization (browser-only PDF rendering for hundred-page documents is impractical) but are not retained after your session and are never used for training or sharing. No sign-up, no account, no watermark on the output.