DjVu books to WebP, on your device. Nothing ever uploads.

Drop DjVu files below — get a WebP image for every page you pick, lossless or lossy at the quality you choose, at the DPI you choose, in batches of up to 20. Converted entirely on your device.

  • Batch up to 20 files
  • Page ranges + 72/150/300 DPI
  • Lossless or lossy WebP
  • No account, no limits

Convert DjVu to WebP

Add your DjVu files

Drag & drop DjVu files here

or browse your files · you can also paste from the clipboard (Ctrl + V)

Decoding runs in a background worker with DjVu.js — each page is decoded on your device and saved as a WebP. Nothing is uploaded.

WebP encoder loading…

    No files yet. Everything stays on this device. Downloads start instantly.

    What happens next

    1. Add your DjVu files — drop up to 20, 25 MB each.
    2. Pick pages, DPI and quality — or leave the defaults.
    3. Convert — each page downloads as its own WebP, or take the ZIP.

    Privacy you can verify, not just trust

    Most online DjVu-to-WebP converters upload your books to their servers first — and several cap free conversions per day. This one can't: DjVu.js decodes your DjVu pages to WebP entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the conversion itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Convert any DjVu file above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — conversion still works.

    How to convert DjVu to WebP without uploading it

    Every "free" online DjVu-to-WebP converter you've used uploads your book to a company server, converts it there, and — in several documented cases — keeps a copy or a live download link for days. For rare books, old journals, and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

    This tool does exactly that. When you drop a DjVu file here, your browser:

    1. Checks the file is really a DjVu — by its AT&TFORM magic bytes, not its name — and that DjVu.js can open it, so a corrupt or truncated file is refused with a clear message instead of producing a broken WebP. A PDF renamed to .djvu is refused the same way, and a DjVu file renamed to .txt still converts.
    2. Reads the page count and sizes and shows you a preview thumbnail of each selected page, so you can see what will convert before anything is rendered.
    3. Decodes each selected page to pixels with DjVu.js at your chosen DPI and encodes it as a WebP with libwebp — lossless if you switched Lossless on, or lossy at the quality you picked. One WebP per page: each page downloads as its own WebP, named after the book and page number — with 3-digit padding (book-p100.webp) once a book has 100 or more pages, so the files sort in page order. Your original DjVu file is never modified, and no page is ever sent anywhere.

    What makes this converter different

    The pages that top the results for this search are all server-side upload converters (FreeConvert, Quillbot, GroupDocs, Aspose) or desktop software (reaConverter) — none of them is a dedicated free fully client-side DjVu-to-WebP page. This page is the only one we found that combines a batch of 20 DjVu files with page-range selection (All, single page, or a custom range like "2, 4-6"), a DPI choice of 72/150/300, a genuine lossless toggle plus a lossy quality slider (50–95), one WebP per page with per-page download links and preview thumbnails, a per-file ZIP and a combined ZIP with one folder per book — with no daily limits, no account and no watermark — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.

    When is DjVu-to-WebP the right choice?

    Whenever the reader needs plain web images, not a DjVu: pulling a few pages out of a scanned book to share, edit, print or post; feeding pages into an OCR tool or an image editor; or opening an old journal on a phone or tablet that has no DjVu reader. A WebP opens in every current browser, and each page is its own file you can use on its own — much smaller than the PNG equivalent at the same quality. If you need the whole book as one document instead, DjVu to PDF makes a single PDF per book. And if the text layer matters, keep the DjVu — a WebP made here throws the text layer away and can never be searched.

    Honest limitations

    No text layer

    Each WebP is a rasterized render of a DjVu page — a picture, not the page itself. The text is not searchable and cannot be selected or copied from it, and the DjVu OCR text layer is not carried over. Keep the DjVu if you need the text.

    Lossless WebP is lossless; lossy WebP is lossy

    With Lossless on, every page keeps every pixel of the scan it was rendered from. With it off, quality 85 looks identical to the original for most pages and quality 95 is visually near-lossless — but neither is pixel-perfect. A WebP page can never be sharper than the scan it was rendered from.

    WebPs are bigger than the DjVu

    DjVu compresses scanned pages far more efficiently than WebP. Expect the WebPs to be several times the size of the DjVu file in total — that is the price of a web format every browser opens — but much smaller than the PNG equivalents at the same quality.

    No indirect DjVu files

    Indirect DjVu files are refused: opening one would fetch its pages over the network. Bundle the document into a single file with DjVuLibre first, then convert it here.

    No password-protected files

    Password-protected DjVu files are refused, and this tool never asks for a password. Open the file in a desktop DjVu tool first, then convert the unlocked copy.

    Memory-bound in the browser

    Very large or page-heavy books are memory-bound: 25 MB per file, 20 files per batch, 200 pages per file, 75 megapixels per page. A 62-megapixel page took about 13 seconds to decode in our test — split a bigger book into smaller files first, and use 150 DPI for big books.

    Frequently asked questions

    Do my DjVu files upload anywhere?

    No. Your DjVu files are decoded to WebP entirely in your browser with DjVu.js and libwebp — your file data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the converter.

    What is the difference between DjVu and WebP?

    DjVu is a format built for scanned books: it compresses text pages far better than WebP and can carry a text layer, but almost no reader, phone or browser opens it without a special app. WebP is the format the modern web opens — every current browser, phone and editor — and it is much smaller than PNG at the same quality, but a WebP page is bigger than the same page in DjVu, and the lossy WebP this tool makes by default throws some detail away. Convert to WebP when the reader needs a plain web image; keep the DjVu when the file size or the text layer matters.

    Will the WebP text be selectable or searchable?

    No. Each WebP is a rasterized render of a DjVu page — a picture of the page, not the page itself — so there is no text layer, the text is not searchable and you cannot select or copy words from it. The DjVu OCR text layer is not carried over either, even when the file has one. If you need the text, extract it from the DjVu file first, or keep the DjVu alongside the WebPs.

    What DPI should I choose — 72, 150 or 300?

    72 DPI is enough for quick previews and small on-screen reading; 150 DPI is the default and the right pick for reading on screen, sharing and printing at home; 300 DPI is for print and anything you will zoom into or crop later. Higher DPI makes sharper, larger WebPs — a 300 DPI page has roughly four times the pixels of the same page at 150 DPI — and very large pages decode slowly, so pick the lowest DPI that still looks sharp for your use.

    Lossless or lossy — which should I pick?

    Pick lossless when every pixel has to survive exactly — a master copy, or pages you will edit again: libwebp's true lossless mode stores every pixel, but the files are larger, sometimes bigger than the DjVu for photos. Pick lossy (the default, quality 85) when the image is going on a website or being shared: it looks identical to the original for most pages and is much smaller. Quality 50 makes the smallest files; quality 95 is visually near-lossless but not pixel-perfect. The quality slider is ignored while Lossless is on, and if your browser cannot load the WebP encoder the tool falls back to its built-in lossy encoder and says so — lossless is never claimed when it cannot be delivered.

    How do I convert only some pages of a DjVu file?

    Use the page-range setting. All pages converts the whole DjVu file; Single page converts one page you pick by number; Custom range takes a list like 2, 4-6 — pages and ranges separated by commas. Out-of-range pages are reported per file with a clear message instead of failing silently, and each file's card shows exactly which pages are selected before you convert.

    Can I convert several DjVu files at once?

    Yes. Drop up to 20 DjVu files at a time, up to 25 MB each, and convert them all in one go — each page becomes its own WebP named after the book and page number, each book gets its own ZIP, and Download all as ZIP collects the whole batch into one file with one folder per book. There is no daily limit, no account and no watermark — a 200-page cap per file applies because very page-heavy books are memory-bound in the browser.

    What is an indirect DjVu file, and why is it refused?

    An indirect DjVu document is a multi-file document: the index file references its pages as separate files in the same folder. Opening one would make the decoder fetch those page files over the network, which this tool never does — your files stay on your device. Bundle the document into a single file first with DjVuLibre (djvmcvt), then convert the single bundled file here.

    What if my file is password-protected, or not a DjVu at all?

    Password-protected or encrypted DjVu files are refused with a clear message, and this tool never asks for a password. Open the file in a desktop DjVu tool first, then convert the unlocked copy here. A CBR or CBZ comic archive is a ZIP of images — use our Extract Images from CBR or Extract Images from CBZ tool to pull the pages out as images instead. A PDF is a different document format — use our PDF to WebP Converter to turn its pages into WebPs. A file that is already a WebP needs no conversion at all.