Convert Images to PDF in Your Browser

On this site nothing is uploaded — the converter is JavaScript running in your own tab, so image bytes are read from your disk, assembled into a PDF locally, and handed back as a download. There is no upload step to opt out of and no retention policy to read. Server-side tools like iLovePDF, Smallpdf, PDF24 and Adobe do receive your file, which is why they each publish one. The general question of converter safety is covered in depth on our sister site, pdftoword.appsoverflow.com. Learn more →

Most converters decode your image and compress it again on the way into the PDF. Here, a JPEG is written into the PDF byte for byte — the exact bytes you started with, no second round of compression. A PNG is rebuilt rather than copied, but it is rebuilt with lossless compression, so no pixel changes value. HEIC, WebP, AVIF, BMP and TIFF have to be decoded and re-encoded once, and the tool tells you per file which route ran. Learn more →

No account, no email and no daily cap. There is one honest ceiling: up to 200 images and 600MB in a single batch, because that is what a browser tab can hold in memory — not a metering decision. For comparison, iLovePDF caps its image-to-PDF task at 20 files and 40MB even for registered users, and FreeConvert and CloudConvert both stop free users at 10 operations a day. Learn more →

Windows can do it natively: select the images in File Explorer, right-click, choose Print, and pick Microsoft Print to PDF. The catch is that this route sends the image through the print pipeline, so it re-rasterises the picture, applies printer margins and crops to the paper frame. Converting in a browser tab skips the print pipeline entirely and lets you set page size and margins yourself. Learn more →

Preview's File then Export as PDF only saves the top image, which is the single most common Mac complaint here. Finder's Quick Actions then Create PDF does merge them, but decides the order for you and gives no control over page size. The browser tool lets you set the order explicitly and choose one merged PDF or a separate PDF per image, HEIC files included. Learn more →

Yes. Pick 50 KB, 100 KB, 200 KB or type your own figure, and the tool works JPEG quality down — then resolution, only if it has to — remeasuring the assembled PDF each pass. It reports the real byte count so you can check before uploading. This is the one mode that deliberately re-compresses; the default converter does not. A PDF's own structure costs a couple of kilobytes, so if your limit turns out to be unreachable the tool says so instead of handing you a file the portal will reject. Learn more →

Yes, and it is arguably the best answer on that device. A Chromebook cannot install a desktop converter, so a tool that runs inside the Chrome tab is the native solution rather than a workaround. Nothing is sent anywhere, which also means it works on managed school and work devices where installs are blocked. Learn more →

The browser tool works in Safari on iPad. The iOS app is built for the device: merge into one PDF or export separate files, reorder pages before converting, name the file, and scan paper documents with automatic edge detection, all without a network connection. The app is free to try with one conversion, then Premium unlocks unlimited conversions. Learn more →

Yes, and every frame becomes its own PDF page instead of only the first one, which is what most converters silently do. The tool counts the frames from the file header before it starts, so you can verify nothing was dropped, and it names any frame it cannot decode rather than skipping it quietly. Common scanner and fax compressions — CCITT G3/G4, LZW, PackBits and JPEG-in-TIFF — are handled. There is no OCR: the pages are images, not searchable text. Learn more →

Phone cameras usually store the picture in the sensor's orientation and add an EXIF tag saying which way to turn it. Photo apps honour that tag; a PDF page does not, so an image that looked upright can land rotated. The converter reads the EXIF orientation and applies it as a page rotation, and you can override it per image with the rotate control before you convert. Learn more →

DPI is not a setting stored in the image — it is pixel count divided by printed inches. A 1200 by 1600 pixel photo placed on A4 prints at roughly 145 DPI, so it simply cannot be a 300 DPI A4 page. For a true 300 DPI A4 you need about 2480 by 3508 pixels. The A4 tool reports the achieved print DPI for every page it builds, so you can check before sending it to a print shop. Learn more →

The pixel values are unchanged, but the embedded ICC color profile is not carried into the PDF, so a wide-gamut photo — a Display P3 iPhone shot or an AdobeRGB scan — is displayed as sRGB and can look flatter or shifted. This affects appearance, not data. If the PDF is going to a paid print run, ask for a proof rather than trusting the on-screen preview. Learn more →