PDF to WebP Converter

What comes out

Each PDF page is rendered in the browser and saved as a WebP image, named after the document: catalogue-page-4.webp. You set the render scale and a quality percentage, preview the pages, and download one file at a time or the whole selection as a ZIP.

WebP is the modern answer to the size problem: it usually produces a smaller file than JPEG at comparable visual quality, and unlike JPEG it can also carry transparency. For page images headed for a website, a slide deck or a chat, that combination is often the best size-to-fidelity deal available.

Browser-side encoding

The PDF is opened locally with PDF.js, drawn to a canvas at the scale you choose, and passed to the browser's WebP encoder. Nothing is uploaded — not the document, not the images. Encoding, previewing and zipping all happen on your device.

The previews therefore show the real WebP output, not a stand-in. What looks soft or banded in a thumbnail will look the same in the file you keep. That is a small but useful difference from the GIF and BMP modes of this converter, which preview a PNG and only reveal the encoded format on download.

Quality, scale and transparency

Two controls matter, and they do different jobs.

• Quality runs from 1 to 100, with 90 as the default. It drives the lossy encoder. Around 80 is usually indistinguishable from 95 on a scanned page; below 60 text begins to smear.
• Scale runs from 5 to 300 percent. It decides how many pixels the page gets before encoding. At 100 percent an A4 page is roughly 794 by 1123 pixels; at 200 percent it is about 1588 by 2246, near 300 DPI for print.

WebP keeps the alpha channel, so a page that does not paint its own background stays transparent. That is welcome for logos and stamps and can be a surprise for ordinary documents viewed on a dark background. If you need a guaranteed opaque page, use JPEG instead, or flatten the image in an editor afterwards.

There is no lossless switch here. The canvas encoder compresses lossily; if you need bit-exact pixels, PNG is the format to pick.

How it compares

The size advantage is real but not universal. On flat text pages PNG can still win because lossless compression of large white areas is efficient. On scanned paper, photos and gradient-heavy brochures, WebP usually wins comfortably.

Compatibility

All current versions of Chrome, Edge, Firefox and Safari display WebP, and so do phones. The friction appears in older desktop software: some versions of Office, older image editors, certain print workflows and a number of upload forms do not recognise the extension. If the destination is a website or a modern app, WebP is safe. If it is an institutional portal, a print shop or a colleague on old software, JPG is the lower-risk choice.

There is also a fallback worth knowing about. In a browser whose canvas cannot encode WebP, the encoder returns PNG data instead while the download still carries a .webp name. Current browsers do not do this, but if a file looks unexpectedly large or refuses to open in an image editor, check what it actually contains before assuming the converter failed.

Running a conversion

1. Add the PDF by dropping it on the panel or clicking the upload area.
2. Confirm the format selector shows WEBP; it lists other formats but starts here.
3. Set quality and scale. For screen use, 85 and 100 percent; for print, 90 and 200 percent.
4. Press Render Pages. All pages are rendered, with progress reported per page.
5. Inspect the previews, especially small print and thin rules.
6. Select pages and download them individually, or export the selection as a ZIP.

Names follow the source file, with unsafe characters replaced by hyphens, and the page number is appended. The archive is name-selected-pages.zip. Selection controls downloads only: rendering always covers the entire document, so a hundred-page PDF takes the same time whether you keep one page or all of them.

Where WebP is the right choice

• Web pages and landing pages. Smaller page previews load faster and reduce bandwidth.
• Slides and presentations. Modern deck software accepts WebP and the files stay light.
• Chat and email. Smaller attachments are less likely to hit a size cap.
• Logo and stamp pages. Transparency survives, so the image drops onto any background.
• Photo-heavy brochures. The format's compression advantage is largest here.

It is the wrong choice for archival masters, for print shops that demand TIFF or JPEG, for anything requiring exact pixel values, and for workflows where the recipient's software predates roughly 2020.

Sending the files onward

WebP travels well between modern systems and badly through old ones, so it is worth thinking about the last hop rather than the first. A file uploaded to a web platform is fine; the same file emailed to a print shop that expects JPEG may come back as "unreadable" even though the image is perfectly valid. When you are unsure about the recipient, render the pages as JPG as well — the format selector makes that a second pass rather than a separate job — and send whichever version the destination accepts.

Naming also matters more than it seems. Page numbers in the filenames mean an extracted archive sorts back into document order, and the ZIP carries the source document's name, so a recipient who receives several archives can tell them apart without opening them.

Limits

One PDF per run, all pages rendered, one still image per page, no animation, no lossless mode, no control over encoder effort or chroma settings, no embedded colour profile, no DPI metadata and no text layer. Password-protected files cannot be opened. There is no page-range render, no batch queue and no OCR. Practical size is limited by browser memory rather than a stated maximum, and very large pages at 300 percent can be slow.

Privacy

Everything stays local: PDF.js reads the file, the canvas encodes it, and the download is a local blob. The only network activity is loading the PDF.js library itself when the page opens. For confidential documents, this is one of the safer outputs in the family, alongside PNG and JPEG.

Common mistakes

• Sending WebP to an old portal. Extension checks reject it even though the file is valid.
• Pushing quality to 100. The size grows quickly for a difference nobody sees.
• Expecting lossless output. The canvas encoder is lossy; use PNG for exact pixels.
• Confusing transparency with a white background. Transparent areas take the colour of whatever is behind them.
• Rendering 200 pages for one image. Selection filters downloads, not rendering.
• Assuming the extension guarantees the codec. In rare fallback cases the bytes may be PNG.

Frequently Asked Questions