Output format
90%
Resize
Convert PDF to WEBP Online Free — Fast Batch Conversion
How to Convert Images Online
1Upload PDF
Drag and drop your PDF file. Multi-page PDFs supported.
2Choose settings
Select DPI (72/150/300), encoding mode (lossy or lossless), and quality level.
3Download WebP
Click Convert. Download individual files or ZIP. Files deleted immediately.
Supported Image Formats
WebP
Modern image format by Google. Up to 30% smaller than JPG with the same quality.
PDF
Portable Document Format. Convert PDF pages to JPG, PNG or WebP images.
HEIC
Apple photo format used by iPhone and iPad. High quality with small file size.
HEIF
High Efficiency Image Format — same as HEIC, used on Apple devices.
PNG
Lossless format that preserves every pixel. Best for screenshots and logos.
JPG
Universal format for photos. Supported everywhere, great balance between quality and file size.
GIF
Classic format for simple animations. Supports transparency and up to 256 colors.
BMP
Uncompressed bitmap format. Maximum quality but very large file size.
TIFF
Professional lossless format used in printing and photography.
AVIF
Next-gen format with excellent compression. Up to 50% smaller than JPG.
PPM
Portable Pixmap format used in Unix/Linux environments.
HDR
High Dynamic Range format storing extended brightness data.
FITS
Flexible Image Transport System used in astronomy and science.
AVIF vs WebP vs HEIC vs JPG
Quick comparison to help you choose the right format
AVIF
- Size: Up to 50% smaller than JPG
- Browsers: Chrome, Firefox, Safari
- Transparency: ✓
- Best for: Web performance
WebP
- Size: 25-35% smaller than JPG
- Browsers: All modern browsers
- Transparency: ✓
- Best for: Web compatibility
HEIC
- Size: ~50% smaller than JPG
- Browsers: Safari only
- Transparency: ✓
- Best for: iPhone storage
JPG
- Size: Baseline
- Browsers: All browsers & apps
- Transparency: ✗
- Best for: Universal sharing
Frequently Asked Questions
- How do I convert PDF to WebP?
- Upload your PDF, choose DPI (150 for web, 300 for Retina), select lossy or lossless encoding, click Convert. Each page becomes a separate WebP image delivered as a ZIP.
- Is WebP smaller than JPG for PDF page images?
- Yes. At equivalent visual quality, WebP lossy is 25–34% smaller than JPEG. A 300 DPI A4 page is roughly 280 KB as WebP versus 450 KB as JPG.
- What DPI should I use?
- 72 for thumbnails, 150 for web hero images (sweet spot), 300 for print or Retina 2× displays. Higher than 300 rarely adds visible detail.
- Does WebP support transparency?
- Yes — full 8-bit alpha in both lossy and lossless modes. JPEG cannot do this.
- Why do my colors look different after conversion?
- Print PDFs use CMYK color space. WebP only supports sRGB. Without color management the conversion produces a greenish shift. Convertify converts automatically.
- Can I convert all pages at once?
- Yes. All pages are rendered and packaged as a ZIP file.
- Does WebP work in Safari?
- Yes, since Safari 14 (September 2020). Over 97% of browsers support WebP globally.
- Should I choose lossy or lossless?
- Lossy for photographs and brochures — smaller files. Lossless for text-heavy documents and diagrams — pixel-perfect.
- Why is my WebP file larger than expected?
- Likely using lossless at high DPI. Switch to lossy at 150 DPI for web use.
- Does Convertify delete my files?
- Yes. Files are deleted immediately after download. Nothing is stored.
Render pages vs extract embedded images — two different operations
When you convert PDF to WebP, there are two fundamentally different things you might want. Rendering means rasterizing the entire page — text, vector graphics, embedded photos, backgrounds — into one flat image at a chosen resolution. This is what most people need: turning a brochure page into a hero image, a slide into a social media post, or a spec sheet into a product page asset. Extracting means pulling out the original images that were embedded inside the PDF — the photographs, logos, and charts that the PDF author placed during layout. Extraction preserves the original resolution and compression of each embedded image but ignores text, vector graphics, and page layout. Convertify performs full-page rendering at your chosen DPI.
How DPI controls your output — the decision tree
DPI (dots per inch) determines how many pixels the renderer generates for each inch of the PDF page. An A4 page is 8.27 × 11.69 inches. At 72 DPI that produces a 595 × 842 pixel image — fine for a thumbnail. At 150 DPI you get 1240 × 1754 pixels — the sweet spot for web hero images and blog posts. At 300 DPI the output is 2480 × 3508 pixels — print quality, suitable for Retina displays or physical printing. Going higher than 300 DPI rarely adds visible detail for text-and-vector PDFs because the renderer already captures every curve at 300; it just multiplies file size. A 600 DPI A4 page produces a roughly 139 MB raw RGBA buffer that compresses to about 1 MB as lossy WebP — large and slow to encode with minimal visual benefit over 300 DPI. For most web use cases 150 DPI is the right choice.
File size comparison: same A4 PDF page at different DPIs and formats
| DPI | Pixels (A4) | JPG Q80 | PNG | WebP Lossy Q80 | WebP Lossless |
|---|---|---|---|---|---|
| 72 | 595 × 842 | ~45 KB | ~150 KB | ~30 KB | ~110 KB |
| 150 | 1240 × 1754 | ~190 KB | ~750 KB | ~120 KB | ~500 KB |
| 300 | 2480 × 3508 | ~450 KB | ~1.8 MB | ~280 KB | ~1.1 MB |
| 600 | 4960 × 7016 | ~1.8 MB | ~7 MB | ~1 MB | ~4.5 MB |
WebP lossy vs lossless — which mode to choose
WebP has two independent compression engines. Lossy mode uses VP8 — a DCT-based codec similar to JPEG but with better entropy coding and in-loop deblocking. At quality 75–85 it produces files 25–34% smaller than JPEG at equivalent SSIM scores. This is the right choice for photographic content, brochure pages with photographs, and any case where file size matters more than pixel-perfect accuracy. Lossless mode uses VP8L — a completely different codec based on predictive coding, LZ77 back-references, Huffman coding, and a color cache. It produces files roughly 26% smaller than equivalent PNG. This is the right choice for text-heavy pages, line art, diagrams, and screenshots where you need every pixel exactly preserved. Both modes support 8-bit alpha transparency.
Why PDF to WebP instead of PDF to JPG?
Three reasons. First, file size: WebP lossy at quality 80 is consistently 25–34% smaller than JPEG at the same visual quality. For a 10-page PDF converted at 150 DPI, that means roughly 1.2 MB total as WebP versus 1.9 MB as JPG — a meaningful difference for page load times. Second, transparency: JPEG cannot represent transparency at all. If you need a transparent-background render for overlaying on a colored page or compositing in CSS, WebP supports full 8-bit alpha while JPEG does not. Third, modern web compatibility: every major browser supports WebP — Chrome since version 23, Firefox since 65, Edge since 18, Safari since 14. The only holdouts are IE11 and Safari 13 or earlier, both effectively dead in 2026.
CMYK color profiles — the color shift problem
Print-prepared PDFs often use CMYK color space. WebP only supports sRGB. When the renderer converts CMYK to sRGB without proper color management, colors shift — typically appearing greenish or desaturated. This is especially visible in brochure PDFs designed for offset printing. The fix is explicit color conversion during rasterization: PDFium and Ghostscript both support sRGB conversion flags that apply ICC profile transforms before encoding. Convertify applies sRGB conversion automatically, so your WebP output matches what the PDF looks like on screen — not what it would look like on an offset press.
Core Web Vitals — how PDF-to-WebP improves LCP scores
Largest Contentful Paint (LCP) measures how quickly the largest visible element loads. For landing pages that use a PDF-sourced hero image, switching from a 450 KB JPG to a 280 KB WebP at the same 300 DPI saves 170 KB — which translates to 400–800 ms on a typical 4G connection. Google documented real-world results from companies that migrated to WebP: significant improvements in new-user sessions and page engagement. If your site serves PDF-sourced graphics — infographics, brochure excerpts, report figures — converting to WebP is one of the cheapest LCP wins available. Use the HTML picture element with a JPG fallback for the remaining 3% of browsers that do not support WebP.
Multi-page PDFs: one WebP per page, batching, and memory limits
Most converters default to rendering only the first page of a multi-page PDF. libvips, for example, reads page 1 unless explicitly told to load all pages via the n=-1 parameter. When all pages share the same dimensions, it is technically possible to output them as a single animated WebP — but in practice, converters produce one WebP file per page with appended page numbers (page-001.webp, page-002.webp).
For large PDFs — 50 pages or more — memory consumption and processing time become real constraints. A 100-page PDF at 150 DPI produces roughly 100 individual rasterization and encoding passes. Workflows that process these documents typically batch pages in groups of 10–20 to avoid timeout or out-of-memory failures. Pages with different dimensions cannot be combined into a single strip and must be rasterized individually. If your PDF is a scanned book or report destined for web display, PDF to JPG may be simpler for platforms that do not yet accept WebP, while PDF to PNG preserves text sharpness at the cost of larger files.
Text sharpness, accessibility, and SEO after converting PDF to WebP
PDF rasterizers differ significantly in text rendering quality. MuPDF produces high-quality anti-aliased text by default. Ghostscript requires explicit anti-aliasing flags (GraphicsAlphaBits=4, TextAlphaBits=4) — without them, text appears blocky. Once rasterized, the compression mode determines whether text stays sharp: lossless WebP produces pixel-identical output to PNG, preserving every edge. Lossy WebP at quality below 85 softens fine details, particularly small font sizes and thin strokes. For documents with text, use lossless mode or lossy quality 90+.
Converting a text PDF to images removes the text from Google's index and from screen readers entirely. Google can index live text inside PDFs directly, but once pages become WebP images, that content is invisible to crawlers. To mitigate this, every converted image should carry meaningful alt text describing the page content. For SEO-critical documents, keep the original PDF available alongside the WebP previews — link the downloadable PDF and use the WebP images as visual previews only.
Troubleshooting common PDF to WebP problems
Output WebP larger than expected: you are likely using lossless mode at high DPI — switch to lossy at 150 DPI for web use. Blurry or pixelated text: DPI too low — raise to 150 or 300 and enable text anti-aliasing. Colors look greenish or faded: the PDF uses CMYK and color conversion was not applied — Convertify handles this automatically. Transparency disappeared: most PDF pages have an implicit white background that the renderer paints before drawing content — this is standard behavior. Only the first page converted: some tools default to page 1 only — Convertify converts all pages. Photoshop cannot open the WebP: upgrade to Photoshop 23.2 or later, or install the WebPShop plugin. Safari does not display the image: update to Safari 14 or later.