Skip to main content
Image Transformer

Image to PDF and Image Extension Converter

Convert up to 20 PNG, JPEG, WebP, or SVG files into resized PNG/JPEG/WebP downloads or an ordered A4, Letter, or Legal PDF entirely in the browser. Perfect for creating multi-page documents from screenshots, generating print-ready layouts, and preparing image collections for sharing or archiving.

Image tools

Drag and drop images here

PNG, JPEG, SVG, WebP up to 50 MB each

Browse files locally

Export Configuration

PDF Settings (A4 Output)
100%
90%
All conversion runs inside this browser tab using Canvas and local PDF export. Files are never uploaded.

In brief

Use Canvas for local image re-encoding and jsPDF for one-image-per-page PDF export, with explicit 20-file, 50 MB-per-file, and 10,000-pixel dimension limits.

What this tool supports

  • Accepts PNG, JPEG/JPG, WebP, and SVG by MIME type or .svg filename, with at most 20 queued files, 50 MB per file, and 10,000 pixels on either decoded dimension.
  • Exports each queued image as PNG, JPEG, or WebP at 25%–200% scale; the 35%–100% quality control applies to JPEG/WebP while PNG ignores it.
  • Builds one PDF page per image in queue order using A4, Letter, or Legal paper, portrait or landscape orientation, and 0, 5, 10, or 15 mm margins.
  • Reorders and removes queued files, shows decoded dimensions and status, and downloads each image result or a single PDF without an application-server upload.

How to use Image to PDF and Image Extension Converter

Follow this implementation-specific workflow for Local Image and Multi-Page PDF Converter; each step reflects the controls and limits in the current browser workspace.

  1. 1

    Step 1

    Provide the exact source

    Drop or choose one to 20 supported image files; reject any item over 50 MB or with a decoded width or height above 10,000 pixels.

  2. 2

    Step 2

    Choose the operation

    Select PDF for one ordered document, or PNG, JPEG, or WebP for one downloaded result per source image.

  3. 3

    Step 3

    Configure the available options

    For PDF, set paper size, orientation, and margin; for every output choose a 25%–200% raster scale and, where applicable, lossy quality.

  4. 4

    Step 4

    Run the local operation

    Reorder the queue before conversion, then start the process and keep the tab open while Canvas decodes, resizes, and exports every image.

  5. 5

    Step 5

    Verify and continue

    Open the downloaded artifact: confirm page order and margins for PDF, or inspect pixel dimensions, transparency, MIME type, and visual quality for image output.

Common mistakes

Expecting transparency in JPEG or PDF pages

Consequence: Transparent pixels become white because PDF pages are fed a JPEG render and direct JPEG export paints a white Canvas background.

Fix: Choose PNG/WebP when alpha must survive, or deliberately approve the white background before exporting PDF/JPEG.

Treating the quality slider as a resolution or file-size guarantee

Consequence: Quality controls encoder loss, while scale controls pixels; browser encoders may produce different byte sizes and unsupported WebP export can fall back to PNG bytes.

Fix: Set scale from required pixel dimensions, inspect the downloaded MIME/visual result, and measure the actual file size in the target browser.

Adding AVIF, GIF, TIFF, HEIC, or an oversized source

Consequence: Validation accepts only PNG, JPEG/JPG, WebP, and SVG and enforces the implemented file, count, and dimension caps.

Fix: Convert the source to a supported still-image format first and process large batches in groups of no more than 20.

Best practices

  • Keep original files until every downloaded page, color, alpha channel, and filename has been checked.
  • Use PNG for sharp graphics or transparency; use JPEG/WebP only after comparing quality at the final display size.
  • Order files before PDF conversion and test a representative page at the chosen paper, orientation, and margin settings.

Connected workflows

Browser limitations

  • Canvas codec support is browser-dependent: PNG is required, while JPEG/WebP encoding and SVG decoding can vary; the app does not inspect a fallback blob MIME before naming it.
  • Every source, data URL, decoded bitmap, Canvas, and PDF page is held in tab memory; several 50 MB or 10,000-pixel images can still exhaust a mobile device.
  • PDF creation rasterizes every page through JPEG, so searchable text, vector SVG structure, metadata, animation, and transparency are not preserved.

Authoritative resources

HTMLCanvasElement.toBlob()Publisher: MDN Web Docs · Reviewed: 2026-07-26PDF 2.0 (ISO 32000-2)Publisher: PDF Association · Reviewed: 2026-07-26

Concrete examples

Input
photo.png — 800×600 pixels; output JPEG; scale 50%; quality 90%
Result
A locally downloaded 400×300 JPEG; transparent source pixels are composited onto white.

getScaledDimensions rounds 800×0.5 and 600×0.5, then Canvas.toBlob requests image/jpeg at quality 0.9. Exact compressed bytes vary by browser encoder.

Frequently asked questions

Can this tool put several images into one PDF in a chosen order?

Yes. Move files up or down before conversion; each becomes one page in that queue order and the first filename supplies the PDF download name.

Why did transparency disappear from my converted document?

The PDF path first converts every image to JPEG, and JPEG has no alpha channel. Direct JPEG export also fills the Canvas white before drawing.

Does the PDF retain SVG vectors or selectable text?

No. SVG and every other source are decoded into pixels and embedded as JPEG page images, so vector paths and text semantics are lost.

What happens when WebP export is unsupported?

Canvas may return PNG instead of the requested format. The current workspace does not verify that fallback MIME before assigning the .webp filename, so inspect the file.

Are the 50 MB and 10,000-pixel limits a promise that conversion will fit in memory?

No. They are input guards, not a memory guarantee; decoded pixels can occupy far more memory than the compressed source, especially across a 20-file queue.

Privacy and offline behavior

Selected image bytes, decoded pixels, temporary data URLs, and PDF bytes stay in this browser. Conversion works offline after app assets and the bundled libraries are cached; files leave the device only if you explicitly download or share them.