Convert JPG to PDF — page size, margins, and the decisions that actually matter
Every JPG-to-PDF tutorial on the internet is the same four sentences: "upload your file, click convert, click download." Except that's not the part anyone's actually stuck on. The decisions that matter — Letter or A4, fit-to-page or margins, portrait or landscape, re-encode or embed, and why the output PDF is somehow 40 MB — are the ones every top-ranking post skips. Here's the honest version.
The short version
- Drop one or more JPGs on the converter. Drag to reorder if you need a specific page sequence.
- Pick a page size — Auto fits each page to its image, Letter (US) or A4 (rest of world) for printed documents.
- Pick margin and fit: Fit to page scales the image inside a margin; Fill page covers edge-to-edge; No margin crops right to the paper edge.
- Leave quality at Embed original — lossless, smallest change from your source file. Only switch to Re-encode if you need a size cap.
- Download. One PDF, one page per image, in the order you dropped them.
If that covers it, go. The rest of this post is for when you're printing the result, when the PDF is bigger than you expected, or when you're deciding between this and Smallpdf / Acrobat / Preview.
Letter vs A4 vs Auto — pick one on purpose
Page size is the first real decision, and the one most lazy converters get wrong by defaulting silently. Three reasonable choices, one correct one per situation:
Letter (8.5 × 11 in)
The US/Canada default. If the PDF will be printed on a typical office or home printer in North America, pick Letter. Pages designed for A4 print with a sliver of blank space at the bottom and get clipped at the right edge on Letter paper — it's ugly.
A4 (210 × 297 mm)
The ISO standard used by almost every country that isn't the US/Canada. Slightly narrower and taller than Letter. If you're in Europe, Asia, Latin America, or sending the PDF to someone who is, pick A4. Same logic in reverse — A4 content printed on Letter stock crops.
Auto (match image aspect ratio)
The page size equals the image size — no letterboxing, no stretching, no cropping. This is the right choice for screenshots, receipts, scanned documents where the aspect ratio already matters, photo portfolios, and anything that will live on a screen rather than a printer. We default to Auto because it's the most common intent: people convert JPGs to PDF to share an image as a document, not to print it at a specific paper size.
Rule of thumb: if you will print it, pick Letter or A4. If you will email or upload it, pick Auto.
Fit, fill, or no margin — what each actually does
Once you've picked a page size, you have to tell the PDF generator what to do when the image aspect ratio doesn't match the paper. Three options:
- Fit to page (with margin) — the image is scaled down to fit inside a printable area with a small margin (we default to 0.5 in / 12 mm). Blank space shows on the short axis. Best for printed documents where a physical printer needs a margin anyway.
- Fill page (no margin, some crop) — the image covers the full paper, edge to edge, even if that means cropping the long axis slightly. Best for photo-book or poster output.
- Stretch to fit — the image is squashed to exactly match the paper. Don't. This distorts aspect ratio and everyone will notice. We expose it for pure completeness; nothing looks right this way.
A 4:3 phone photo on an 8.5×11 Letter page: Fit-to-page gives a ~1 in band of white at top and bottom. Fill-page crops ~15% off the sides. Auto page size sidesteps the whole question — the page just becomes 4:3.
Orientation — let the tool pick, unless you have a reason
Orientation is the boring one. Our default is auto: portrait if the image is taller than wide, landscape if wider. Override manually only when:
- You're mixing several images and want a consistent orientation across all pages (e.g., forcing every page to portrait).
- The image is nearly square and you have a specific document style in mind.
- The source was rotated incorrectly. Most JPGs carry an EXIF
Orientationtag that cameras set but some older viewers ignore; if the PDF looks sideways, rotate the JPG itself before converting rather than fighting with PDF page orientation.
Re-encode vs embed — the quality-vs-size trade
This is the setting almost no JPG-to-PDF site exposes, and it's the one that most affects your final file size. A PDF can carry a JPG two ways:
Embed the original JPG bytes (lossless wrap)
The PDF spec supports JPEG (DCTDecode filter) natively. That means the PDF can literally contain the JPG file byte-for-byte inside a page object — no decompression, no re-encoding, zero quality loss. The PDF ends up only a few kilobytes larger than the input JPG (the PDF structural overhead). A 2 MB JPG becomes roughly a 2 MB PDF.
Our tool calls this Embed original. It's the default, and it's almost always the right choice. It's also the fastest — no pixel decoding happens at all.
Re-encode at a new quality level
Sometimes you want a smaller PDF. Our tool can decode the JPG, re-encode at a lower quality (we expose a slider from 30 to 95), and embed that. This is genuinely lossy — you're stacking two generations of JPEG compression — so reserve it for cases where the file has to fit under an upload cap.
For most size-budget situations, there's a better answer: embed the original first, then run the PDF through our PDF compressor, which does a smarter job (it can downsample images, not just re-encode them). Re-encoding in the JPG-to-PDF step is for when you want one conversion and done.
DPI — only matters if you're printing
DPI (dots per inch) is the number of image pixels mapped to each inch of paper. It's a print-only concept; on a screen, there's no DPI, just pixel dimensions. Three benchmarks:
- 72 DPI — web / screen reference. Fine for email or PDF viewers. If you print a 72-DPI image at full page size, it looks pixellated.
- 150 DPI — draft print. Acceptable for internal documents, handouts, proofs.
- 300 DPI — commercial print quality. This is what print shops assume. Photos, brochures, anything you'd hand to a client.
Our tool computes DPI automatically from your image pixel dimensions and the chosen page size. A 3000×2000 px JPG on an A4 page clocks in at about 254 DPI — essentially print-quality. A 1920×1080 screenshot on Letter is about 180 DPI — readable but visibly pixellated on the printed page. A 640×480 thumbnail on A4 is 55 DPI and will look terrible.
If your source JPG is too small to print well, no converter can save you — there's no more detail to recover. Either source a higher-resolution original, or (if the image came from a scan of a document) re-scan at 300 DPI. For photos where detail genuinely exists but the pixel count is low, our AI upscaler can 2× or 4× the pixel dimensions before you drop into the JPG-to-PDF step.
Batch and multi-page workflows
Most JPG-to-PDF use cases aren't a single image — they're a stack: a multi-page scanned contract, photos of a whiteboard session, receipts for an expense report, an entire sketchbook. Three workflow notes:
Drag to reorder
We show thumbnails of every file you drop, in the order you dropped them. Drag to reorder before you export — PDF page order is fixed at generation time, and it's annoying to regenerate because one page was out of sequence. If your files have a numeric prefix (scan-01.jpg, scan-02.jpg…), we sort alphabetically by default, which usually does the right thing.
Mixed page sizes
If you're combining screenshots, phone photos, and scanned documents in one PDF, Auto is usually the right size — each page matches its source image. If you need a single consistent page size, pick Letter or A4 and use Fit-to-page; this preserves aspect ratio and wastes a bit of paper space.
Very large batches
Our browser-side renderer handles 30-50 images comfortably on a typical laptop. Past that, memory is a real constraint — PDF generation holds every image in RAM until the final file is written. If you're regularly batching 100+ images, the paid tier raises the limits, or our API (POST /api/convert with target=pdf) will stream the job server-side.
"Why is my PDF so huge?" — a diagnosis
This question is the #1 support request on every JPG-to-PDF tool on the internet. The answer is always the same and almost no tool explains it:
A JPG-to-PDF conversion embeds your JPG inside a PDF wrapper. The PDF is as big as the JPGs you put in, plus a few KB of structural overhead. If you dropped ten 4 MB phone photos, your PDF is ~40 MB. That's not a bug, it's arithmetic.
The fix is to reduce the image payload. Three honest paths:
- Compress the JPGs first — run them through our JPEG compressor to shrink each input to 200–400 KB before the PDF step. For phone photos this is typically a 5–10× size cut with no visible quality loss.
- Convert first, then deep-compress the PDF — build the PDF with "Embed original" (fast, lossless), then drop the output into our PDF compressor. It resamples each embedded image to a target DPI and re-encodes at a chosen quality. This is almost always the biggest size win, and the flow most people want.
- Re-encode during conversion — if you want one step and are OK with lossy, switch from "Embed original" to "Re-encode" in the advanced settings and pick quality 75. Acceptable for casual sharing; noisy on fine detail.
A real example: 12 photos of a whiteboard, each 3.8 MB JPG (46 MB total source). Straight embed → 46 MB PDF. Through the PDF compressor at 150-DPI target → 6.4 MB PDF, visually identical. That's the difference between "email bounce" and "send it now."
How our tool compares (honestly)
JPG-to-PDF is commodity functionality — every serious PDF tool supports it. What differs is defaults, privacy, and what happens when you need more control. Honest scoresheet:
| Tool | Cost | Where it wins | Where it loses |
|---|---|---|---|
| FireConvertApp | Free | In-browser, no upload, no watermark, embed-original default (lossless), exposes page size / margin / DPI / re-encode settings that most free sites hide | Per-file size cap on the free tier; 30–50 image batch limit before RAM matters; no OCR layer (yet) |
| Smallpdf | Free w/ 2-per-day cap, $9/mo Pro | Polished UI, wide format coverage in the broader suite, good OCR on Pro | Uploads every file to their servers; the free tier throttles to 2 conversions/day; no page-size or margin control on the free tier; adds a subtle watermark on some exports |
| iLovePDF | Free w/ small-file cap, $4–$7/mo Premium | Clean interface, solid batch UX, PDF merge and split integrated | Upload-based (slow on a 10-image batch); page-size picker is buried; re-encodes JPGs by default so files are bigger than they need to be |
| Adobe Acrobat (online) | $19.99/mo | Industry-standard output, excellent OCR, full PDF editing after conversion | Expensive for a one-off; requires a Creative Cloud sign-in for anything beyond a preview; server-side only |
| macOS Preview.app | Free (Mac only) | Zero-install, drag-and-drop, print-to-PDF works for any number of JPGs | Mac only; always re-encodes (no pure embed path) so the output PDF is ~1.4× bigger than needed; no batch-reorder UI |
Honest summary: if you already pay for Acrobat, use it — especially for anything that needs OCR. On a Mac, for a one-off PDF of a few images, Preview is fine (just accept the bloat). For everything else — no-sign-up, no upload, actual page-size and fit control, lossless embed by default, batch work, or a workflow that continues into PDF compression — our JPG to PDF tool is the shorter path.
Where our tool works well — and where it doesn't
Works well
- Receipts, scanned documents, screenshots, phone photos — anything where lossless embedding is the right default
- Mixed-orientation batches (drag-to-reorder thumbnails, per-page auto-orient)
- Print-ready output at Letter or A4 with real margin control
- Privacy-sensitive files (stays in your browser; no upload)
- Any workflow that chains into PDF compression afterward
Doesn't work (well) yet
- OCR — we embed the image as an image; text inside is not searchable or selectable. For a searchable PDF you need a tool with an OCR pass (Acrobat, or a dedicated OCR converter).
- Very large batches (100+ images) — RAM-bound in the browser. Use the API for that scale.
- Password protection and digital signatures — not part of this tool. A downstream PDF editor handles that.
- Fine-grained page layout (two-up, booklet, N-up tiling) — we ship single-image-per-page. For layout work, use a PDF editor after conversion.
Tips for the best result
- Leave "Embed original" on unless you have a reason. It's lossless, fastest, and matches the JPG size to the PDF size almost exactly.
- Pick page size based on where the PDF goes. Screen / email → Auto. Printer → Letter (US) or A4 (rest of world). Mismatched paper is the single most common print-day problem.
- Compress JPGs before conversion, not after. Shrinking the inputs with our JPEG compressor is cleaner than re-encoding during the PDF step, because you pick the compression quality once instead of stacking two generations of JPEG loss.
- For a size-capped final PDF, chain the compressor. Generate the PDF lossless, then run it through our PDF compressor — this is the standard "fit under Gmail's 25 MB cap" workflow.
- If the source is a PNG, use the right tool. PNGs with transparency convert cleanly via our PNG to PDF tool; going PNG → JPG → PDF adds a lossy hop you don't need.
- For source images that aren't JPG, pick the right entry point. PNG to PDF handles PNGs cleanly without a lossy JPG hop; each image format has its own converter for best results.
Common questions
Will I lose quality converting JPG to PDF?
Not with the default. Our "Embed original" mode wraps the JPG bytes inside the PDF without re-encoding — the pixels are byte-for-byte identical to your input. You only lose quality if you explicitly switch to "Re-encode" mode to hit a size cap.
Can I combine multiple JPGs into one PDF?
Yes — that's the most common use. Drop multiple files, drag the thumbnails to reorder, and the output is a single multi-page PDF with one image per page, in whatever order you set.
Why is my PDF so much bigger than I expected?
Because a JPG-to-PDF conversion embeds your JPGs inside a PDF wrapper. If you put in 30 MB of JPGs, you get out a ~30 MB PDF (plus a few KB of overhead). To shrink the result, either compress the source JPGs first with our JPEG compressor, or run the output through our PDF compressor.
Letter or A4 — which should I pick?
Letter (8.5 × 11 in) if the PDF will be printed in the US/Canada. A4 (210 × 297 mm) if it'll be printed anywhere else. If it won't be printed — just emailed, shared, or viewed on a screen — pick Auto and let the page size match the image.
Can the text in the PDF be searched or copied?
No — not unless there's an OCR step. Our tool embeds the image as an image; the letters in the picture are just pixels to the PDF reader. For a searchable PDF (where Cmd-F finds words in your scanned document), you need a tool with OCR — Adobe Acrobat and some dedicated OCR converters do this. We don't, yet.
Do my files get uploaded to your server?
No. The conversion runs entirely in your browser tab — we use pdf-lib and the browser's native JPEG decoder, sandboxed in WebAssembly. Your files never leave your machine. Larger files that exceed browser memory limits may fall back to server-side processing on the paid tier; when that happens, we'll tell you first.
Is this tool really free?
Yes. Unlimited conversions per day, no watermark, no sign-up. The free tier caps per-file size and batch count; paid tiers lift those caps. Output quality is identical across tiers — paying only changes the ceiling on file size and batch volume.
Can I convert PDF back to JPG?
Yes — the reverse direction rips each PDF page out as a JPG. Use our PDF to JPG tool for that. Useful for pulling a single image out of a shared PDF, or for converting a scanned document to individual image files.
Ready?
JPG to PDF →. Drop the files, pick page size, download the PDF. Free, in your browser, no sign-up, no watermark. If the result is bigger than you want, chain it into our PDF compressor — that combination is the short path to an emailable document.