Unuploaded

Converter · No upload

WEBP to PDF, privately

Drop in WEBP images and download a PDF of each one, with transparency kept. The conversion runs entirely inside your browser — nothing is uploaded, the network meter below proves it live, and it keeps working with your wifi switched off.

Statusidle Files— OutputPDF Network since file read—

One PDF per image, sized to the image at a point per pixel — a converter, not a page layout tool. The picture is decoded by your browser and written back as pixels: an animated WEBP keeps its first frame only, an EXIF orientation tag is not applied (your browser does not apply it either), transparency is kept as a soft mask and semi-transparent pixels lose some colour precision, and EXIF or XMP metadata never enters the PDF. An embedded colour profile is carried on still images. An image over 14,400 pixels on a side is placed on a 200-inch page at a smaller scale, and the row says so. Takes .webp.

How this converter works

Every modern browser decodes WEBP natively — it is a web format, after all — so this page has no decoder of its own to ship. What it has instead is a reader for the container: before anything is decoded it walks the file's RIFF chunks for the two things that change what happens next — the animation flag, because a browser flattens an animation to its first frame without a word, and an embedded colour profile, which decides how the pixels are asked for. Then it asks your browser for the pixels, splits the colour from the alpha, compresses each with flate — the reversible compression PNG uses — and writes them into a PDF image object with a soft mask for the alpha when any pixel needs one. Colour is handled as a pair, never a mix: a still image that carries a profile is decoded raw and the profile becomes the PDF's colour space, while an image without one is decoded the ordinary way and written as plain RGB, so no profile is ever applied twice. The result is wrapped in a Blob and offered back as a download link. No step involves a network transfer, because the file is already on your machine and this site has no server to send it to.

The best evidence for that is not our instrument but your browser's. Press F12, open the Network tab, leave it visible, and run a conversion. Nothing gets added to the list. That panel is written by the people who make your browser, it records what a page actually does rather than what a page claims, and no code of ours can quiet it. This converter has an especially easy time of it: the decoder is the one your browser already uses to show WEBP images on every other site, the PDF is a few hundred lines of first-party code, and there is no library to fetch and no traffic to explain away. Compare notes with the methodology page, which sets out two further ways to catch us.

The honest limits: the page is the size of your image at one point per pixel, so this is a converter and not a layout tool, and each file becomes its own one-page PDF. An animated WEBP keeps only its first frame, because a PDF page is a still, and the row says so. A WEBP's EXIF orientation tag is not applied — your browser ignores it when it shows you the file, and a PDF that rotated would differ from every preview you have seen. The metadata itself never enters the PDF: EXIF and XMP blocks stay in the original, which for a document you share is usually the right default, but note anything you need out of them first. Semi-transparent pixels lose a little colour precision on the way through the canvas your browser decodes into, which is why nothing on this page calls the conversion exact for a translucent image. And a very large image is placed on a smaller page rather than a rejected one, because the format caps a page at 200 inches while the picture keeps every pixel — the row says when that happened.

Frequently asked questions

Is my image uploaded anywhere?
No. Your browser decodes the WEBP itself, and this page writes the pixels into a PDF in this tab, from bytes read off your own disk. The network meter above counts requests made after your file is read and it stays at zero — disconnect entirely and convert again if you want to see that for yourself.
Does the image lose any quality?
Not in the way a re-save would. The WEBP is decoded once by your browser and the pixels go into the PDF under flate, the same reversible compression PNG uses, so an opaque image arrives with the numbers the decoder produced — a lossy WEBP's own encoding loss is already in the file before this page sees it. The one place precision goes is semi-transparent pixels: your browser premultiplies colour by alpha while decoding, so a nearly transparent pixel comes back with coarser colour than it went in with. An embedded colour profile is carried on still images, and EXIF or XMP metadata is not — only pixels leave the decoder.
What happens to an animated WEBP?
Only its first frame goes into the PDF — a PDF page is a still — and the result row says so. The page reads the container's animation flag before decoding, because a browser decodes an animation to its first frame without any error and would otherwise let the conversion report plain success on a clip it had flattened.
What happens to transparency?
It is kept. PDF has no interleaved alpha channel, so the transparency is separated out and attached as a soft mask, which is the standard way a PDF carries it — transparent areas stay transparent over whatever the page is placed on, and the row says the mask was made. A fully opaque WEBP skips this entirely and carries no mask at all.
Can I put several WEBPs into one PDF?
Not yet — each WEBP becomes its own single-page PDF, and dropping several files gives you several PDFs. Combining them into one document is a different job with its own decisions about page order and sizing.

Related tools