Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting PDF to WebP keeps a document page readable at a fraction of the size of a PNG, which makes it the right format for a preview or thumbnail on a website. Set the resolution to suit the size the thumbnail will be shown at, drop the file above, and the page is drawn in your browser.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
PDF to WebP
There are three sensible ways to turn a PDF page into a picture and they are not interchangeable. JPG is small and smudges text. PNG is sharp and large. WebP is the one that does both jobs adequately, which makes it the right answer for the web and a slightly odd one anywhere else.
If you are showing a document preview on a site — a thumbnail of a report, the cover of something downloadable, a page embedded in an article — the image is competing with everything else on the page for load time.
A PNG of a text page is sharp and can easily be several hundred kilobytes. The same page as a WebP is typically a fraction of that, and the text still looks clean because WebP handles hard edges far better than JPG does. That combination is what nothing else offers.
This is the setting worth getting right, and it works differently here than for a photograph. A PDF stores instructions rather than pixels, so the page is drawn at whatever resolution you ask for, at full sharpness. The control is in dots per inch, from 36 to 600, and it starts at 150.
Convert the dpi into pixels before you pick one: an A4 page is 8.27 inches wide, so it comes out 595 pixels across at 72 dpi and 1240 at 150. The useful rule is to draw at roughly twice the size the image will occupy on screen, which for a thumbnail displayed 300 pixels wide means about 72 dpi — a long way below the default, and a much smaller file. Typing 600 in there gives you a 4960-pixel page nobody asked for.
WebP is forgiving of hard edges compared to JPG, but it is still lossy, and this path writes it at a fixed quality of 82 with no control on the page. There is nothing to push down and nothing to raise, which for a document page is the setting you would have chosen anyway — the file still comes out dramatically smaller than the PNG of the same page. If a page of eight-point footnotes looks soft, the answer is more dpi rather than more quality.
Anything leaving the browser. A page going into a printed report, a slide deck, an email attachment or somebody else's document should be a PNG, because some desktop software still does not read WebP and you will not be there to explain it. WebP is a format for the web, and this conversion is for pages that are staying there.
As with the other PDF conversions, one page is one image — the Pages box chooses how many — and the words become pixels, so the result cannot be searched or selected. If the text matters to a search engine, put the text on the page as text and use the image alongside it.
Thumbnailing one PDF is a moment; thumbnailing a library of them is the actual job. Dropping many files at once converts them one after another and returns them together, and because the work happens on your own machine there is no queue and no per-file cost to ration.
The free tier takes 100 files at a time and 100 MB per file, and below those the ceiling is your device’s memory — a desktop is far more generous than a phone. If a large batch stalls, splitting it in half is usually all that is needed.
Every current browser displays WebP, which covers the case this conversion is usually for — a thumbnail on a web page. Outside the browser the picture is patchier: some desktop image viewers, some older design software and a fair amount of corporate tooling still do not open it.
So WebP for a page you control, and PNG or JPG for a file you are handing to someone else. The conversion is the same work either way; the question is only where the image is going to be opened.
| WebP | ||
|---|---|---|
| Full name | Portable Document Format | WebP Image |
| File extension | .webp | |
| Media type | application/pdf | image/webp |
| Compression | Either, depending on the setting | Either, depending on the setting |
| First published | 1993 | 2010 |
| Published by | Adobe | |
| Specification | ISO 32000-2 | RFC 9649 |
| Licensing | Open standard | Open standard |
| Standing today | Current | Current |
| Bit depth | — | 8 |
| Colour it can describe | RGB, CMYK, greyscale | RGB, YCbCr |
| Largest image | — | 16,383 px per side |
| Opens in a browser | Every browser | Every browser |
| Considered instead | DOCX, HTML | AVIF, JPG, PNG |
WebP holds one page. A multi-page PDF converts a page at a time rather than in one file.
Layers are merged. PDF keeps them separate and editable; WebP stores the composite, so anything that depended on moving a layer afterwards has to happen before the conversion.
WebP has nowhere to put the document properties, so that goes no further than the PDF. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
PDF can hold CMYK; WebP is RGB. A file prepared for a printing press converts to screen colour, and the separations have to be made again in the print workflow.
Transparency survives. Both PDF and WebP store an alpha channel, so a cut-out stays cut out and nothing is filled in behind it.
The usual programs do not overlap: PDF opens in Adobe Acrobat, Preview and LibreOffice Draw, WebP in Adobe Photoshop, GIMP and Squoosh — so whoever receives the result needs something from the second list.
PDF is Adobe's format, published in 1993. The specification is ISO 32000-2, and it is worth reading if the file has to outlive the tool that wrote it.
WebP comes from Google and dates from 2010, specified as RFC 9649. Adobe Photoshop, GIMP and Squoosh all read it.
PDF was published in 1993 and WebP in 2010. The older one is generally the safer file to hand to somebody; the newer one usually does the job in fewer bytes.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is PDF.js, Mozilla's PDF engine, the one Firefox itself uses; your browser fetches it once and caches it.
Size. WebP handles both text and photographs well and produces a much smaller file than PNG for the same page. On a website that is the whole point; for a page going into a printed document, PNG is still the safer choice.
Much better than in a JPG, which is the real comparison. WebP handles hard edges far more gracefully, so letters stay clean. This path writes at a fixed quality of 82 with no slider to change it, so the lever you have for small text is the resolution: draw the page at more dpi.
All of them if you leave the Pages box alone, since empty means the whole document. Name a page or a range — 4, or 1-3, 7, 10- — to get less than that. A WebP holds one image, so several pages come back as a ZIP, fifty at a time.
The setting is in dpi rather than pixels, and an A4 page comes out 595 pixels wide at 72 dpi. So a thumbnail shown 300 pixels wide wants 36 dpi, which is the lowest the box goes, and 72 dpi if you want the doubled version high-density screens deserve.
Not on its own — the words in the image are pixels and no crawler reads them. Put the text on the page as text and use the image alongside it.
The claims this page makes about PDF and WebP are checkable, and these are the documents that settle them.