PDF to WebP & WebP to PDF Converter

It converts selected PDF pages into individual WebP images and combines one or more WebP images into a new PDF. Both directions run locally in the browser.

Yes. Each selected PDF page becomes a separate WebP image. One selected page downloads directly, while multiple pages are packaged in a ZIP archive.

No. Standard WebP is a single-image format. Multiple PDF pages therefore need separate WebP files, usually delivered together in a ZIP archive.

Yes. Enter all or ranges such as 1-5,8,12-15. Duplicate page numbers are removed while the entered order is retained.

A quality around 88 to 92 is a practical balance for most pages. Higher values preserve more detail but produce larger files, while lower values are useful for lightweight web previews.

Yes when the page content permits it. Choose Transparent background. Many PDF pages already contain an opaque white page background, so transparency may not be visible.

Yes. Select Grayscale to convert the rendered page pixels before WebP encoding.

1.5\u00d7 or 2\u00d7 works well for screen use. Use 3\u00d7 for detailed output, understanding that pixel count, conversion time and memory consumption increase quickly.

No. WebP is an image format, so PDF text, vectors and layout are rasterized into pixels.

Yes. Choose up to 50 WebP images, reorder or remove them, and create one PDF containing a page for every selected image.

Yes. Use the up and down buttons in the file list. The preview and final PDF follow the resulting order.

Yes. Remove any item from the list while keeping the remaining images and settings.

Yes. Match image dimensions uses the image pixels and your selected source DPI to calculate an appropriate PDF page size.

Yes. Choose A4, Letter, Legal, A3 or A5, then select automatic, portrait or landscape orientation.

Contain shows the entire image and can leave blank space. Cover fills the page area and may crop edges. Stretch fills the area without preserving the original aspect ratio.

PDF pages themselves use a background surface. Transparent WebP pixels are flattened against the selected white or black page background before embedding.

Lossless mode embeds a PNG representation of the decoded WebP pixels. Smaller mode uses adjustable JPEG compression and normally creates a smaller PDF.

No. The PDF can preserve decoded WebP pixels, but it cannot restore detail already removed by lossy WebP compression.

No. WebP images are raster graphics. The PDF contains image pages unless the source is processed separately with OCR.

The tool treats each selected WebP as one still image. Animated frames are not expanded into multiple PDF pages, and the browser may decode only the default frame.

No guarantee is made for image metadata. Canvas decoding and re-encoding generally focuses on visible pixels rather than preserving the original metadata container.

The page accepts a PDF up to 100 MB. The practical limit can be lower when many pages are rendered at high scale.

You can choose up to 50 WebP files with a combined size of 200 MB. Very large dimensions can still exceed browser memory before those limits.

PDF file size does not equal rendered pixel size. A vector page can be compact on disk but become millions of pixels when rendered at a high scale.

Detailed text, diagrams, noise and high quality settings reduce compression efficiency. Lower the quality or render scale for smaller output.

Increase the render scale or WebP quality. The source PDF may also contain low-resolution images that cannot be improved by conversion.

No. Encrypted or password-protected PDFs are rejected. Unlock the document with authorization before conversion.

It checks for the RIFF container and WEBP signature, then asks the browser to decode the image before accepting it.

No page-specific upload endpoint receives your PDF or WebP files. Source bytes, previews and generated outputs stay in the current browser session.

No. The browser downloads pinned processing components, but the selected file bytes are not sent to those delivery services by this tool.

No. Temporary canvases, decoded images, blobs and object URLs exist only in browser memory and are released during reset or navigation.

Yes. The interface is responsive and touch-friendly, though large multi-page or high-resolution jobs are better suited to devices with more memory.

Current Chrome, Edge, Firefox and Safari releases are expected to support WebP decoding, canvas encoding, local file reading and downloads. Content blockers can prevent pinned processing components from loading.

The converter stops before processing and explains that the current browser cannot create WebP images. Updating the browser is usually the best solution.

Yes. Press Cancel during rendering or PDF creation. The tool stops at the next safe point and does not keep a partial output.

Press Reset to release source data, decoded images, canvases, generated blobs and temporary URLs, then choose another source.