Step 1: Deliver your PDF files using the button above or by place and set.
Step 2: Click the 'Process' button to start the processing.
Step 3: Obtain your converted WebP files.
PDF to WebP Processing FAQ
How do I convert PDF pages to WebP images?
+
Upload the PDF file and the converter renders each page as a separate WebP file. By default each page becomes its own image; the result is bundled as a ZIP archive ready to download with predictable filenames (page-001.WebP, page-002.WebP, …).
What DPI does the WebP render at?
+
Default 150 DPI (good for screen viewing and casual print). Advanced options expose 72 DPI (web thumbnail), 150 (default), 300 (print quality), 600 (high-quality archival). Higher DPI means sharper WebP images but proportionally larger files and longer render time.
Can I extract just specific pages of PDF as WebP?
+
Yes — the page-range option accepts inputs like `1-5`, `1,3,5`, or `all` to pick which pages of the PDF get rendered to WebP. Useful when only a chapter, appendix, or cover-page of a long PDF is needed.
Will the WebP preserve PDF text searchability?
+
No — rasterizing PDF to WebP turns vector text into pixels. If you need searchable output, keep the PDF as a PDF and use a text-extraction tool instead. The WebP output is for visual display, slide decks, or further image processing only.
What about transparent backgrounds in the WebP?
+
PNG WebP preserves the PDF page background as transparent if the source page has no explicit fill (rare for typical documents, common for diagrams exported from Figma / Illustrator). JPG WebP cannot store transparency — pages render onto a white background. For transparent output target PNG, TIFF, or WebP.
How long does PDF to WebP take for a 100-page document?
+
About 30-90 seconds for a 100-page PDF → WebP at 150 DPI. Higher DPI multiplies the time: 300 DPI roughly doubles, 600 DPI roughly quadruples. Premium accounts get more parallel workers — 100 pages typically renders in under 30 seconds for them.
What is the file size of a typical WebP page?
+
A 150-DPI WebP render of an A4 page is 200-800 KB (PNG) or 50-150 KB (JPG at quality 85). Multiply by page count to size the bundle — a 100-page PDF → PNG ZIP is typically 30-80 MB; the same as JPG is 5-15 MB.
Can I merge all PDF pages into one tall WebP image?
+
Not in the basic flow — each page becomes its own WebP by default. To produce a single stitched image, download the ZIP, then use /image-merge/ to vertically concatenate the per-page WebP files. The two-step path keeps memory use bounded for very long documents.
Is my PDF private during WebP conversion?
+
Yes — same privacy model as every conversion: isolated workers, automatic deletion within minutes of completion, no human review. Document content (text, embedded images, form fields) is never read by a human at any stage.
Will images embedded in the PDF appear correctly in the WebP?
+
Yes — embedded JPGs, PNGs, and inline graphics inside the PDF are rendered into the WebP at the chosen page DPI. The page renderer treats them like every other page element; no separate extraction step is needed.
Can I convert just the first page of a PDF as a WebP thumbnail?
+
Yes — set the page-range option to `1` and the converter produces a single WebP file rather than a ZIP. Useful for generating cover thumbnails for a PDF library, e-commerce previews, or HTML preview cards.
Why does my WebP look pixelated when zoomed in?
+
You are rasterizing vector content into pixels — zoom amplifies the rasterization step. For infinite-zoom output, target SVG instead (when the PDF contains vectors); for sharper rasters at the same dimensions, bump DPI to 300 or 600 in the advanced options and re-render.