Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
JFIF (JPEG File Interchange Format) is the standard container for JPEG-compressed image data, standardized by ITU-T Recommendation T.871 and ISO/IEC 10918-5. Despite the different extension, a .jfif file is byte-identical in structure to a .jpg saved by the same encoder — both carry the same image/jpeg MIME type. Microsoft Edge, older Chrome builds, and some Vivaldi versions began saving downloaded images as .jfif because of a registry mapping under HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg, which is why a folder of "saved from web" images often has the .jfif extension instead of .jpg.
Merging those files into a single PDF gives you a portable, paginated document that is easy to email, archive, or print:
.jfif files. One PDF beats sending 30 attachments..jfif even though it's a JPEG. PDF sidesteps the extension confusion entirely.| Property | .jfif | .jpg | .jpeg |
|---|---|---|---|
| Underlying format | JPEG (with JFIF APP0 segment) | JPEG (typically with JFIF or Exif segment) | JPEG (typically with JFIF or Exif segment) |
| MIME type | image/jpeg | image/jpeg | image/jpeg |
| Standard | ITU-T T.871 / ISO/IEC 10918-5 | Same JPEG bitstream; extension is DOS 8.3 convention | Same JPEG bitstream; original 4-letter extension |
| Common origin | Edge / Chrome saved images on Windows; image/jpeg MIME default | Cameras, phones, most software exports | macOS, some pro photography software, web servers |
| Quality vs JPG | Identical bitstream | Identical bitstream | Identical bitstream |
| App support | Some legacy apps reject the extension | Universal | Universal |
Renaming a .jfif to .jpg does not re-encode the file or lose quality — it's the same bytes with a different extension. Merging them to PDF gives you the same fidelity as merging the renamed JPGs would.
| Compression Type | Target use | Approx. quality | File size |
|---|---|---|---|
| Screen | On-screen viewing only | 72 dpi, lower JPEG quality | Smallest |
| Ebook | Tablets, e-readers | 150 dpi | Small |
| Default | Mixed-use, balanced | 150-300 dpi | Medium |
| Prepress | Print shops, color-critical | 300 dpi, color preserved | Large |
| Printer | High-quality desktop printing | 300 dpi | Largest |
These names mirror the Ghostscript PDF settings presets (/screen, /ebook, /default, /prepress, /printer) — the same presets used across most server-side PDF tools, so output sizing is predictable.
The encoded image data is the same JPEG bitstream — same DCT coefficients, same quantization tables, same quality. JFIF adds a small APP0 marker segment that records resolution, pixel aspect ratio, and (optionally) a thumbnail. In practice, every modern viewer treats them identically. The reason your Edge downloads come out as .jfif is a Windows registry mapping, not a different image format.
Windows uses HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg to decide what extension to write when a browser saves an image/jpeg file. On many Windows installations that mapping is set to .jfif, so Edge (and Chrome and Vivaldi, which use the OS mapping) write the file with that extension. You can change the registry value to .jpg to fix it system-wide, or just merge the existing files to PDF and move on — the image data inside is identical.
Yes. The uploader accepts .jfif, .jpg, and .jpeg interchangeably and treats them as the same format. You can also drop in PNG or other images using the related Merge Image to PDF tool, or convert JPG-based files into the same workflow with Merge JPG to PDF and Merge JPEG to PDF.
Set Quality Percentage to 95-100 and Compression Type to Prepress or Printer. Choose paper size "Same as image size" so the tool doesn't re-sample to fit a fixed page. With Image placement set to Cover and Margin to No margin (0"), the resulting PDF page is the same pixel dimensions as the source image, so there's no resampling loss.
Lower Quality Percentage to 60-75 and pick Compression Type "Screen" or "Ebook". For images that contain transparency artifacts on the alpha channel, set Image Transparency to "Removed" — JPEG does not store alpha, but the option flattens any transparent metadata that crept in from the source. If you still need a smaller file, run the output through Compress PDF.
Cover fills the page; if the image's aspect ratio differs from the chosen paper size, the long side is cropped. Contained fits the whole image inside the page margins, leaving white space on the short side. Use Cover + No margin for full-bleed photo books and slide decks where every page is one image. Use Contained + Normal or Large margin for reports, evidence binders, and anything that will be printed and bound.
Yes — set Combine to "Individual PDFs" and the tool produces one PDF per input file in a downloadable batch. This is useful when each image needs to be archived as its own document (e.g., one PDF per receipt), but you still want the consistent paper-size, margin, and compression settings applied to all of them at once.
Yes — the order of thumbnails in the upload list is the order of pages in the output PDF. Drag thumbnails up or down to rearrange before clicking Merge. Filenames sort alphabetically by default, so naming your files 01_cover.jfif, 02_intro.jfif, etc. is the easiest way to enforce a specific order across large batches.
Browser-side processing means the only practical limit is your device's RAM. A few hundred 2-megapixel JFIFs merge cleanly on a typical laptop. For very large photo sets (1,000+ files at 24 MP each), it's faster to merge in batches of 50-100 and combine the resulting PDFs separately. If your source images are larger than they need to be, Compress JFIF first and the merge will be faster and the output PDF smaller.