About WebP to PDF
WebP to PDF decodes each WebP in the browser, writes the decoded pixels as PNG, and embeds that PNG on a PDF page. This preserves decoded pixels and transparency but can make the PDF larger than the original WebP. Choose A4, Letter or Match image, set fixed-sheet orientation, and reorder the images before saving.
WebP to PDF specs
| Price | Free ($0) — no paid tier |
|---|---|
| Account | Not required |
| Watermark | None |
| Where it runs | In your browser, on your device |
| File upload | No file is uploaded |
| Input | WebP (1 or more files) |
| Output | |
| File size limit | Limited only by your device's memory |
| Offline use | May work after all required code and assets have loaded; browser caching is not guaranteed |
How to use WebP to PDF
Add WebP files
Drop one or more .webp images.
Choose page geometry
Use A4, Letter or Match image; Auto, Portrait and Landscape apply to fixed sheets.
Reorder
Drag thumbnails into the required PDF page sequence.
Download
Press Download PDF to generate images.pdf.
Frequently asked questions about WebP to PDF
Does it choose between JPEG and PNG automatically?
No. Every accepted WebP is decoded through a canvas and re-encoded as PNG before PDF embedding. There is no quality slider or photographic JPEG path.
What happens to animation?
The browser bitmap decode used here produces a still image. The PDF does not retain WebP animation.
Why might the PDF be larger?
WebP is designed for compact web images. Re-encoding the decoded pixels as PNG can cost more space, especially for photographs, even though it avoids another lossy encode.
Why in-browser processing matters
Every PDFChamp tool runs inside this page: the file you choose is read by JavaScript in your own browser and is never sent to a server, so nothing is uploaded, queued, or stored anywhere. That removes the upload wait, the processing queue, and the question of what happens to your file afterwards — the PDFChamp overview compares this architecture with server-side PDF tools.
Last updated