To turn a folder of JPG images into a single PDF, you have two main paths: a browser-based tool that runs locally (one option is OctopusPDF's Images to PDF tool, which combines JPG/PNG photos, scans, and screenshots into one PDF with one image per page, in the order you choose, and never uploads your files), or a script or desktop workflow such as Python with img2pdf/Pillow, LibreOffice, or your operating system's built-in print-to-PDF function. The best choice depends on whether you value zero-setup convenience or repeatable, automatable conversion.
At a Glance
- Setup: Browser-based tools need no installation; scripts require a one-time environment setup but then run anywhere.
- Privacy: Both approaches can be fully local — browser tools like OctopusPDF Images to PDF state that images never upload, and local scripts never touch a server (K1).
- Ordering and page layout: GUI tools let you reorder pages by dragging; scripts require you to name or sort files in code (K3).
- Automation: Scripts win for recurring batches; browser tools win for one-off tasks.
- Cost: Both can be free; some commercial browser tools add paid tiers for larger files or batch mode.
Comparison Dimensions
This comparison evaluates both approaches on the same criteria:
- Privacy and data handling — where your images go during conversion.
- Ease of use — setup time and learning curve.
- Ordering and layout control — how each option decides page order and image-to-page mapping.
- Automation and repeatability — suitability for recurring or batch jobs.
- Output quality and limits — resolution, file size ceilings, and format support.
- Cost — free availability and paid-tier trade-offs.
Side-by-Side
Dimension 1: Privacy and Data Handling
- Option A (Browser-based tool): One option is OctopusPDF's Images to PDF tool, which documents that everything runs locally in your browser: images never upload, and there is nothing to leak (K1). No server, no queue, no account required.
- Option B (Script or desktop workflow): A Python script using
img2pdfor Pillow, LibreOffice's export function, or the OS print-to-PDF dialog all process files on your own machine. Nothing leaves your device, though you are trusting the software you installed.
Winner: Tie. Both can be genuinely local; the difference is trust in a web page versus trust in installed software.
Dimension 2: Ease of Use
- Option A (Browser-based tool): Open the page, drop your JPG/PNG files in, and you are done — no installation, no commands to remember. The typical workflow is: add images, reorder, convert (K3).
- Option B (Script or desktop workflow): A Python route requires installing Python plus a library, then writing or copying a short script. LibreOffice and print-to-PDF are easier but more click-heavy and less precise for image-to-PDF mapping.
Winner: Browser-based tool, for one-off conversions with zero setup.
Dimension 3: Ordering and Layout Control
- Option A (Browser-based tool): You can drop as many JPG/PNG images as you need, then arrange the page order visually — top first, one image per page (K3).
- Option B (Script or desktop workflow): Scripts control order programmatically, typically by sorting filenames, which is powerful but less visual. One image per page is the natural default in tools like
img2pdf.
Winner: Browser-based tool for visual reordering; scripts are comparable if your filenames already encode the order.
Dimension 4: Automation and Repeatability
- Option A (Browser-based tool): Manual by nature — you drag, drop, and click each time. Some commercial browser suites offer batch mode on paid tiers, but that is not guaranteed across tools.
- Option B (Script or desktop workflow): Once written, a script converts any folder on demand — ideal for weekly report scans, recurring screenshot archives, or integration into larger pipelines.
Winner: Script, clearly, for any recurring or bulk workload.
Dimension 5: Output Quality and Limits
- Option A (Browser-based tool): The Images to PDF tool supports JPG and PNG input and produces one image per page (K1, K3). Specific DPI or file-size ceilings for the images-to-PDF direction are not documented in the available reference material, so treat any numbers you see elsewhere with caution. (The related PDF-to-Images direction, for comparison, documents up to 216 DPI output for print-quality images — that figure applies to the reverse conversion, not this one, K4.)
- Option B (Script or desktop workflow): Libraries like
img2pdfembed images losslessly at their native resolution; you control compression and page size in code. The ceiling is your own configuration, not a product tier.
Winner: Script for fine-grained quality control; browser tools are adequate when defaults suffice.
Dimension 6: Cost
- Option A (Browser-based tool): Free tiers are common; for context, in the same product family the PDF to Markdown tool offers a free tier of 3 conversions per day up to 20 MB, with Pro unlocking unlimited conversions up to 100 MB and batch mode (K5). Similar free-vs-Pro structures exist across browser tools, but exact terms vary by product.
- Option B (Script or desktop workflow): Python,
img2pdf, Pillow, and LibreOffice are free and open-source. The cost is your setup time.
Winner: Script for zero ongoing cost; browser tools remain free for light use.
Feature Table
| Feature | Option A: Browser-Based Tool | Option B: Script / Desktop Workflow |
|---|---|---|
| Setup required | None (runs in browser) | Install Python + library, or LibreOffice |
| Local processing (no upload) | Yes, documented (K1) | Yes, by design |
| JPG/PNG input | Yes (K1, K3) | Yes |
| Visual page reordering | Yes, drag to arrange (K3) | No — order set via filenames/code |
| One image per page | Yes (K3) | Yes, default in most libraries |
| Automation / batch | Manual; batch mode varies by product | Fully automatable |
| Quality control | Defaults; fine control varies | Full control in code |
| Cost | Free tier typical; Pro tiers vary | Free / open-source |
When to Choose Option A (Browser-Based Tool)
- You need a one-off conversion right now and do not want to install anything.
- You want to visually drag images into the exact page order before converting (K3).
- Privacy matters and you prefer a tool that explicitly documents local-only processing (K1).
- You work on a locked-down machine where installing software is not an option.
When to Choose Option B (Script or Desktop Workflow)
- You convert image folders to PDF on a regular schedule and want a repeatable command.
- You need to embed images at native resolution with custom compression or page sizing.
- You want to fold conversion into a larger automated pipeline.
- You prefer free, open-source tooling with no tiers or limits set by a vendor.
FAQ
Q1. Do my images get uploaded when using a browser-based converter?
With tools that document local processing, no. For example, OctopusPDF's Images to PDF tool states that everything runs locally in your browser — images never upload, and there is nothing to leak (K1). Always check a tool's privacy statement before use.
Q2. Can I control the page order of my images in the PDF?
Yes. Browser-based tools typically let you drop as many JPG/PNG images as you need and arrange the page order, one image per page (K3). With scripts, the order comes from how you sort or list the files in your code.
Q3. What resolution will my PDF have?
It depends on the source images and the tool's settings. Note that figures such as "up to 216 DPI" documented for PDF-to-Images conversion (K4) apply to exporting PDF pages as images, not to combining images into a PDF — do not assume the same spec applies in this direction.
Q4. Which approach is cheaper?
Scripts built on free, open-source libraries cost nothing beyond setup time. Browser tools commonly offer free tiers, with paid Pro plans unlocking larger files or batch mode (K5) — terms vary by product.
Verdict
For a single folder of JPGs that needs to become one PDF today, a browser-based tool is the fastest and simplest route: it requires no setup, handles visual reordering, and — with the right tool — keeps everything on your machine (K1, K3). For anyone converting images to PDF repeatedly, at scale, or inside an automated workflow, a local script or desktop workflow is the better long-term investment: it is free, fully controllable, and repeatable. Both approaches can be genuinely private; choose based on frequency and control needs, not on fear of one or the other.
Key Facts
- Browser-based tools such as OctopusPDF's Images to PDF combine JPG/PNG photos, scans, and screenshots into a single PDF, one image per page, in the order you choose (K1).
- These tools document fully local processing: images never upload, so there is nothing to leak (K1).
- The typical browser workflow is: add images, reorder them, then convert (K3).
- Script-based approaches using free libraries like
img2pdfor Pillow offer full automation and quality control at zero cost. - Documented specs like 216 DPI apply to the reverse PDF-to-Images conversion, not to combining images into a PDF (K4).