Combine JPG to PDF Without Losing Image Quality
Step-by-step walkthrough for converting and merging multiple JPG images into a single PDF. Covers page sizing, DPI, and compression tradeoffs.
I needed to submit 8 scanned pages as a single PDF for a visa application. The embassy form specifically said "one PDF file, maximum 5 MB." My scans totaled 34 MB as separate JPGs. The challenge was not just combining them - it was doing so at a file size under 5 MB without turning the text into an unreadable blur.
After testing the process across several tools, I found that the quality loss most people complain about comes from one specific step - and it is avoidable.
Why combining JPG to PDF sometimes destroys quality
A JPG file is already compressed. When a conversion tool opens your JPG, it decompresses it into raw pixel data (a bitmap). To create the PDF, it then re-compresses that bitmap. This double compression is called generation loss, and it gets worse each time you re-encode.
The severity depends on the re-compression quality setting. If your original JPG was saved at 90% quality and the PDF tool re-encodes at 85%, you lose detail in two places: once when the camera saved the JPG, and again when the PDF tool re-encoded it. On photos, you will see it as increased blockiness around edges. On document scans, small text starts to blur.
The fix: Use tools that embed your JPG data directly into the PDF without re-encoding. The jsPDF library (used by browser tools like JPG Joiner's PDF converter) does exactly this - it takes your compressed JPG stream and wraps it in a PDF container. No decompression, no re-compression, no generation loss. The output PDF is almost exactly the same size as your combined JPGs.
Step-by-step: Combining JPG to PDF in a browser
1. Pick the right tool
Use a client-side converter if your images contain anything private - ID scans, medical records, financial documents. Server-based tools process your files on remote infrastructure where you have no visibility into data handling. JPG Joiner's PDF tool processes everything in your browser. You can verify: open your browser's Network tab (F12) and watch that zero image data leaves your machine.
2. Set the page size before adding images
Most people skip this and end up with pages that do not match their images. Three page size options work for different scenarios:
- A4 (210 x 297 mm) - standard for documents outside the US. Use this for form submissions, visa applications, and anything going to European/Asian institutions.
- Letter (8.5 x 11 in) - standard US paper size. Receipts, tax documents, and anything you might print on a US printer.
- Fit to image - the PDF page matches each image exactly. Best for photo portfolios or when you do not plan to print. Keeps the original aspect ratio without adding white margins.
3. Watch for DPI and margins
DPI (dots per inch) controls how large your image appears on the PDF page. A 3000 px wide photo at 300 DPI fills exactly 10 inches - perfect for A4 width. At 150 DPI, the same image would be 20 inches wide, spilling off the page unless the tool auto-scales.
Most browser-based tools handle this automatically by scaling images to fit within the page margins. But if you notice your images are tiny in the center of a large page, the tool is probably using the image's embedded DPI metadata (often 72 DPI from phone cameras) instead of scaling to fit. Switch to "fit to page" mode if available.
4. Order matters
The sequence of your images becomes the page order in the PDF. Drag to reorder before generating. I have submitted forms twice because I forgot to move a page. For multi-page documents, I now name files with a numerical prefix (001-front.jpg, 002-back.jpg) so they sort correctly on upload.
5. Compress if you need to hit a file size limit
Embassy forms, insurance claims, and university applications often cap PDF size at 2-5 MB. If your combined output exceeds the limit:
- Lower JPG quality to 80-85% before combining. On document scans, this is invisible. On photos, you lose some fine detail in hair and textures.
- Resize source images to 1500-2000 px on the long edge. For documents being read on screen, this resolution is more than enough. Only keep full resolution for print.
- Remove color from document scans. Converting to grayscale cuts file size by roughly 60% with zero impact on readability.
I compressed my 34 MB of visa scans to 4.8 MB by resizing to 1500 px wide and using 85% quality. Text remained perfectly legible. The embassy accepted it on the first try. For comparison, my first attempt used the images at full 4032 px resolution with 95% quality, which produced a 28 MB PDF - way over the 5 MB limit. Dropping resolution to 1500 px did the heavy lifting. The quality drop from 95% to 85% barely mattered for scanned documents, but it shaved off another 30% of file size.
Command-line approach for batch conversion
If you do this regularly - processing invoices, archiving receipts, building report decks - a command-line workflow saves time.
Using ImageMagick:
magick convert *.jpg -quality 90 -page A4 combined.pdfThis converts all JPGs in the current folder into a single A4-paged PDF at 90% quality. Processing time for 20 images: about 1.8 seconds on a modern laptop.
For maximum quality (no re-encoding), use img2pdf, a Python tool purpose-built for this job:
pip install img2pdf
img2pdf *.jpg -o combined.pdfimg2pdf wraps the raw JPEG stream into the PDF container. Zero decompression, zero re-encoding. The output file size equals the sum of your input JPGs plus a few kilobytes of PDF metadata. This is the closest you can get to truly lossless JPG-to-PDF conversion.
Common file size comparison
I converted the same 8 scanned documents (total: 34 MB as JPGs) using different methods:
| Method | Output PDF size | Quality loss |
|---|---|---|
| img2pdf (no re-encode) | 34.1 MB | None |
| Browser tool (jsPDF, direct embed) | 34.3 MB | None |
| ImageMagick at 95% | 29.7 MB | Minimal |
| ImageMagick at 80% | 11.2 MB | Visible on zoom |
| Online tool (generic) | 52.6 MB | None (but inflated) |
The last row is important. Some online tools convert your JPGs to uncompressed bitmaps before embedding them in the PDF, which inflates the file dramatically. A 4 MB JPG becomes a 48 MB bitmap. If your output PDF is larger than your combined input JPGs, the tool is doing unnecessary decompression.
Merging JPG to PDF on mobile phones
Phone cameras at 12 megapixels produce JPGs in the 4-6 MB range. Ten photos from a phone camera easily hit 40-60 MB combined - well past Gmail's 25 MB attachment limit and most form upload caps. You need to combine and compress on the phone itself, because transferring 50 MB of photos to a laptop just to merge them adds 15 minutes to a task that should take 2.
The fastest approach on any phone is a browser-based converter. Open the JPG to PDF tool in Safari or Chrome, tap to select your photos from the camera roll, set page size, and download the PDF. The entire process stays on-device. I converted 12 apartment listing photos into a single PDF on my phone while standing in the landlord's office. Total time from opening the browser to emailing the file: about 90 seconds.
iOS Files app workaround
iPhones have a hidden PDF trick built into the Files app. Select multiple images in Photos, tap Share, then "Save to Files." Open the Files app, select those images, tap the three-dot menu, and choose "Create PDF." iOS assembles them into a multi-page PDF automatically.
The catch: you get zero control over page sizing, compression, or image order. iOS uses the image dimensions as-is and defaults to a page size that matches each photo. For casual use - sending photos to a friend, backing up receipts - this works fine. For anything with a file size limit, the output is usually too large because iOS does not compress the images at all. My 8 receipt photos (22 MB total as JPGs) produced a 23 MB PDF through the Files app. The same images through a browser tool with 85% quality came out at 6.1 MB.
Android Print to PDF
Android has its own built-in path. Open your images in Google Photos, tap the three-dot menu, select "Print," then change the printer to "Save as PDF." Each image becomes one page.
This approach has the same limitation as iOS - no compression controls. Android's Print to PDF also forces portrait orientation on every page regardless of the photo's actual orientation. Landscape photos get letterboxed with thick white bars above and below, wasting about 40% of the page area. If your photos mix portrait and landscape, use a browser-based tool instead. The print-to-PDF shortcut only works well when all images are already portrait.
One thing I have learned from doing this on phones: always check the output PDF before sending it. Open the downloaded file and scroll through every page. Phone screens are small enough that problems like cut-off edges, wrong page order, or blurry text are easy to miss on a quick glance. I once submitted a rental application where two pages were swapped because my phone sorted the photos by date modified instead of file name. The property manager did not mention it, but it probably did not help my application.
Page orientation and rotation issues
This is the mistake I see most often, and I have made it myself. You have a mix of landscape and portrait photos - maybe document scans where you rotated the paper sideways for a wide table, or a combination of ID card scans (landscape) and letter-sized forms (portrait). You run them through a converter set to A4 portrait, and the landscape images get shrunk to fit within the narrow width of a portrait page.
The math shows why it looks so bad. An A4 page in portrait mode is 210 mm wide. A landscape photo that should span 297 mm gets scaled down to 210 mm - a 29% reduction. But height scales proportionally too, so the image only fills about 70% of the page height. You end up with a small image floating in the center of the page surrounded by white margins on all four sides. On a document scan, the text becomes noticeably smaller than the portrait pages.
Setting per-page orientation
The proper fix is per-page orientation, where each PDF page rotates to match its image. Some tools call this "auto-rotate" or "fit orientation to image." When enabled, a portrait photo gets a portrait page, and a landscape photo gets a landscape page. The PDF viewer handles the mixed orientations seamlessly - you just scroll through and each page fills your screen correctly.
On the command line, img2pdf handles this automatically. It reads the image dimensions and sets each page to match. ImageMagick requires the -auto-orient flag, which reads EXIF rotation data before conversion. Without that flag, photos taken with the phone held sideways appear rotated 90 degrees in the PDF even though they display correctly in your photo viewer.
The rotate-before-convert workaround
If your tool does not support per-page orientation, rotate the problem images before converting. Open the landscape images in any photo viewer or editor, rotate them to portrait, and save. Then convert all images as portrait pages. This works but has an obvious downside: the content is now sideways on the page. The reader has to rotate their screen or print the page and turn it. For formal submissions, this is not ideal.
A better workaround is to run two separate conversions. Group your images into portrait and landscape batches. Convert each batch with the correct orientation setting. Then merge the two PDFs together using a tool like pdftk or an online PDF merger. More steps, but the final document reads correctly on every page.
When to use JPG merge vs JPG-to-PDF
These solve different problems, and picking the wrong one wastes your time.
- Merge JPG to JPG when you need a single image file - product collages for Amazon listings, before/after comparisons for social media, screenshot compilations for bug reports. The output is one .jpg you can paste, embed, or share anywhere that accepts images. Use the JPG merger for this.
- Combine JPG to PDF when you need a multi-page document - visa applications, insurance claims, assignment submissions, or archiving scanned paperwork. Each image gets its own page with consistent sizing. Use the JPG to PDF tool for this.
Frequently asked questions
What DPI should I use when combining JPG to PDF?
For screen-only viewing (email, presentations), 72 DPI is fine and keeps file size small. For printing on a home inkjet, 150 DPI gives good results. For professional printing (brochures, posters), use 300 DPI. The DPI setting does not add detail to your images - it tells the PDF viewer how large to render each pixel. A 3000x2000 px image at 300 DPI prints at 10x6.67 inches. The same image at 72 DPI would fill a 41.7x27.8 inch area on screen.
Why is my PDF file so large after combining JPG images?
PDFs embed the full image data, and many tools re-encode your JPGs. If a tool decompresses your JPG, then re-compresses at a different quality, the file size changes unpredictably. Some tools embed images as uncompressed bitmaps inside the PDF, which inflates a 4 MB JPG into a 48 MB PDF page. Check your tool settings for a "compression" or "quality" slider. Browser-based converters typically produce PDFs in the 80-120% range of the original total JPG size.
Can I combine JPG and PDF files into one PDF?
Yes, but you need a tool that handles both formats. Most JPG-to-PDF converters only accept image inputs. For mixing existing PDFs with JPG images, tools like iLovePDF, Adobe Acrobat, or the command-line tool pdftk work. The process is: convert your JPGs to individual PDF pages first, then merge all PDFs together. On the command line: magick convert photo.jpg photo.pdf followed by pdftk existing.pdf photo.pdf cat output combined.pdf.
Need to combine JPG to PDF right now?
Free, private, no signup. Each image becomes a PDF page. Download instantly.