How to convert PDF to AVIF without uploading it
Every "free" online PDF-to-AVIF converter you've used uploads your document to a company server, converts it there, and — in several documented cases — keeps a copy or a live download link for days. For contracts, payslips, medical letters, 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 PDF here, your browser:
- Checks the file is really a PDF — by its %PDF magic bytes, not its
name — and that pdf.js can open it, so a corrupt or truncated file is refused with a
clear message instead of producing broken images. A JPEG renamed to
.pdfis refused the same way, and a PDF renamed to.txtstill converts. - 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.
- Renders each selected page to canvas with pdf.js at your chosen DPI and encodes it as AVIF with libavif — lossy at the quality you pick (there is no lossless mode: this encoder build's lossless option produces monochrome files) — with the transparent-background toggle on, the AVIF keeps the page's transparency; with it off, transparent areas are flattened onto your chosen background colour. Your original PDF is never modified, and no page is ever sent anywhere. AVIF encoding is slow — about 5–10 seconds for a large photo page — so big batches take a while, but the files come out far smaller than JPGs.
What makes this converter different
The pages that top the results for this search mostly convert on a server, cap free conversions per day, or ask for an account — the big names (Convertio and the other server-side converters) all upload your file and limit free use. The dedicated client-side pages we found each cover only part of the job: Convertlo converts a single file with no DPI or page-range choice; PureConverter is client-side with batch, 72/150/300 DPI and page ranges, but no transparency toggle and no per-page previews; HandyWebUtils relies on the browser's built-in canvas AVIF encoder, which fails in most browsers — it has no encoder of its own; and reaConverter is a desktop program, not a web page at all. None of them combines all of it — batch conversion, page ranges, DPI choice, a real AVIF encoder that works in every browser, a quality slider, a transparency toggle, per-page previews and a ZIP — with no daily limits, no account and no watermark. This page is the only dedicated client-side PDF-to-AVIF page we found that combines a batch of 20 PDFs with page-range selection (All, single page, or a custom range like "1-5, 8"), a DPI choice of 72/150/300, a vendored AVIF encoder (libavif via WebAssembly — the same one that powers the JPG, PNG and AVIF converters on this site — so it works in Safari as well as Chrome, Edge and Firefox), a quality slider, a transparent-background toggle, per-page preview thumbnails, per-page downloads and a ZIP of the whole batch — 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 PDF-to-AVIF the right choice?
Whenever the destination wants a small modern picture, not a document — a page from a report on a website, a diagram or logo from a PDF laid over a coloured slide, a certificate or ticket posted to social media, a form page attached to an email, a scanned page uploaded to a form that only accepts images, or a single page printed at high quality. AVIF is the right pick when file size matters and transparency might matter too: it beats JPG on size and keeps an alpha channel that JPG cannot have. If the destination accepts PDFs, keep the PDF — an AVIF throws away the text layer and can never be searched or re-flowed. And if every pixel must survive exactly and size does not matter, a PNG is the safer pick — lossy AVIF always re-encodes, so there is no pixel-perfect option here.
Honest limitations
No text layer
Each AVIF is a rasterized render of a page — a picture, not the page itself. The text is not searchable and cannot be selected or copied from it. Copy the text from the PDF first if you need it.
Lossy re-encodes
The output always discards some detail — there is no lossless mode. Quality 85 is visually identical to the original for most pages, but quality 100 is near-lossless, not pixel-perfect. Keep your PDF as the master copy.
No lossless mode — on purpose
This encoder build's lossless option produces monochrome files (solid red comes back grey), so a lossless toggle would silently destroy colour. Lossy AVIF at quality 85 is the honest option — and it is far smaller than a PNG of the same page. An AVIF can never be sharper than the PDF page it was rendered from, so pick the lowest DPI that still looks sharp for your use.
AVIF encoding is slow
Expect about 5–10 seconds for a large photo page, and longer for a 300 DPI batch — the encoder trades speed for small files. The page converts one page at a time and shows its progress, so you can watch it work.
Transparency is your choice
With the transparent-background toggle on, transparent areas stay transparent in the AVIF. With it off, they are flattened onto your chosen background colour (white by default). Pages with a solid background are unaffected either way.
No password-protected PDFs
Password-protected PDFs are refused, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then convert the unlocked copy.
AVIF size limit and memory
AVIF caps at 16383 px per side — a very tall page at 300 DPI is refused, so convert it at 150 DPI instead. Very large or page-heavy PDFs are memory-bound: 25 MB per file, 20 files per batch, 200 pages per PDF. Fonts render via pdf.js — rare exotic fonts may substitute. Metadata is dropped, and embedded images are not extracted — each AVIF is a render of a whole page. AVIF encoding is slow (about 5–10 seconds for a large photo page).