Pick the wrong side of PDF vs JPEG and you pay in one of two currencies: wasted kilobytes or broken compatibility. The spec table below settles the facts; the verdict sections tell you which way to lean for photos, graphics and the web.
Side by side
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| Document | No | No | every operating system and browser | |
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
Two rows, but they hide the biggest practical gap: file size on real images, covered next.
The kilobyte question
For PDF, the working reality: an image-based one-pager is typically 200 KB - 2 MB. For JPEG: a 12-megapixel photo lands around 3-4 MB at quality 85.
Averages mislead here — a logo and a sunset photo will rank these two formats in opposite order. Convert one of each and look at the readouts.
For pure web delivery, measure both against WebP before deciding: at over 96% of browsers in use in 2026 (caniuse), it often makes this whole debate academic.
Whichever way the kilobytes fall, remember they compound: a saving of 200 KB per image across a forty-image page is eight megabytes a visitor never downloads.
Quality and features
PDF is document, strongest at documents, presentations, print-ready files, official forms; its known costs are not a true image format, can be large, harder to edit.
JPEG is lossy, aimed at photographs, social media, web images; the trade-off there: lossy compression, no transparency, quality degrades on re-saving.
Neither list is a flaw — formats are tools, and a hammer is not a bad screwdriver. The question is only which job sits on your desk.
The verdict
Choose PDF when your job looks like documents, presentations, print-ready files, official forms and the priority is universal format, preserves layout, supports text and images.
Choose JPEG when you are in photographs, social media, web images territory and need small file size, universal support, great for photos.
Switching sides costs nothing: the JPEG converter and the PDF converter each take seconds, so test both on a real file from your project.
Thirty seconds of compression theory
Container formats like this one wrap images alongside layout, text and other assets — a different job than pure image storage, with different trade-offs.
Lossy compression throws away detail the eye is bad at noticing — fine texture, subtle color steps — and keeps what perception cares about. That is how a photo drops 80% of its weight while looking identical at arm's length; it is also why each re-save discards a little more.
Once you see the mechanism, every size difference in this article stops being magic and starts being arithmetic.
Four real scenarios
The photographer delivering a wedding gallery cares about quality first and upload time second — the format whose profile reads "universal format, preserves layout, supports text and images" or "small file size, universal support, great for photos" closer to that wins the job.
The web developer chasing Core Web Vitals weighs file size above everything: between an image-based one-pager is typically 200 KB - 2 MB and a 12-megapixel photo lands around 3-4 MB at quality 85, the smaller real-world output gets shipped.
The office user attaching a file for an unknown recipient optimizes for one thing — that it opens. Whichever of the two enjoys broader support is the safe envelope.
The print shop reverses every web instinct: resolution and lossless data outrank file size completely, because a 60 MB master is cheaper than a reprint.
The Core Web Vitals angle
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
The compounding is what surprises people: 200 KB saved per image across a forty-image page is eight megabytes a visitor never downloads.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Converting between PDF and JPEG
Moving a file either way is the easy part: the JPEG converter and the PDF converter both take drag-and-drop batches and return a ZIP. Dimensions never change; only the encoding does.
The one rule that matters: keep whichever file is lossless as your archive master, and generate the lossy copies from it on demand.
Living with each format
PDF is handled by effectively every editor of its generation: support in 2026 means every operating system and browser.
For JPEG, the picture is every browser and device made in the last 25 years. That difference decides more real projects than any quality argument does.
When something looks wrong
Colors shifted. Usually a color-profile story: the source carried a wide-gamut profile and the viewer assumes sRGB. Convert from an sRGB master when the destination is the web, and the shift disappears.
The file will not open. Nine times out of ten the viewer is the limitation, not the file. Try a second viewer before blaming the conversion, or convert to JPEG — if that copy opens, the original was fine all along.
Transparent areas turned white. The target format has no alpha channel; flattening is the documented behaviour, not a bug. Re-convert to PNG or WebP if transparency must survive.
The file got bigger. Some content genuinely compresses worse in the new format — flat graphics in photo-oriented codecs, photos in graphics-oriented ones. The size readout before download is the early warning.
Frequently Asked Questions
Which is smaller, PDF or JPEG?
Depends on the image. The anchors: for PDF, an image-based one-pager is typically 200 KB - 2 MB; for JPEG, a 12-megapixel photo lands around 3-4 MB at quality 85. Photographs and flat graphics compress on opposite curves, so test one of your own files rather than trusting an average.
Can I convert between PDF and JPEG without quality loss?
Lossless-to-lossless conversions are perfect copies. The moment a lossy format is involved, some data is discarded — normally invisible at default settings, but keep your originals as the master copies.
Does transparency survive in both?
PDF: no alpha channel. JPEG: no alpha channel. Converting from a format with alpha into one without will flatten transparent areas, usually onto white.
Which one is safer for long-term archiving?
Archives want lossless data and broad software support, because the format must still open in twenty years. Between these two, lean toward the one whose compression does not discard information, and keep checksums either way.
Can I batch convert a mixed folder of PDF and JPEG?
Yes — converters key on each file's actual type, not the folder. Drop the mixed set, pick one target format, and the output comes back uniform in a single ZIP.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.