Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting AVIF to PDF turns an image that only browsers read into a document every machine will open, without re-compressing the picture. Choose the page size, and the whole thing runs on your own machine — nothing is uploaded.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
AVIF to PDF
AVIF is a delivery format for web pages. Sites serve it because it is the smallest thing every current browser reads, and saving a picture from such a page hands you a format nobody on your computer asked for.
The consequence is familiar: the photo viewer refuses it, the email client will not preview it, the print service rejects the upload, and the colleague you sent it to asks what it is. Nothing is wrong with the file — the software outside the browser has simply not followed.
It depends on where the picture is going, and both answers are legitimate. If the destination expects an image — a photo library, an editor, an upload form asking for a picture — then JPG or PNG is the more natural conversion and this is the wrong page.
PDF is right when the destination expects a document. An email attachment somebody will open and print. A form that accepts PDFs and nothing else. A filing system. A print shop. In those cases wrapping the image in a document removes every question about what the recipient can open, because the answer is everybody.
The picture is written into the PDF without a further lossy pass, so the document holds exactly the pixels the AVIF held. No second round of compression, no resampling, no softening of edges.
What it cannot do is undo what already happened. An AVIF served by a website has been compressed to be small, sometimes aggressively, and that compression is in the picture now. Converting changes the container faithfully; it does not restore detail the site chose not to send.
Fitting the page to the image is the right default for anything that will be looked at on a screen — no white border, no letterboxing, and no decision about paper for a file nobody will print.
A4 or US Letter is right when the PDF is going to be printed or filed alongside other paper-sized documents. The image is then centred on the sheet, and it is scaled down if it does not fit but never scaled up: enlarging a small web image onto a full page would turn a sharp picture into a soft one, and a modest picture centred on a page is the honest result.
Setting a margin adds space around the picture. On the default page size it grows the page; on A4 it reduces the room the image is given.
It is worth using when the document is going to a printer, since most printers cannot put ink right to the edge of a sheet and will otherwise crop into the picture. For anything staying on a screen, leave it at zero — a margin on an attachment is white space the recipient scrolls past.
AVIF carries a full alpha channel, and the transparency is preserved in the conversion. But a PDF page is white underneath, so what you see when the document opens is the picture sitting on white.
For most images that is exactly right. The case where it bites is a light-coloured graphic designed to sit on a dark background, which disappears against the page. If that is what you have, place it on its intended colour before converting rather than afterwards.
The decoding happens in your browser rather than in the operating system, which is the useful part on a machine that cannot display the format at all. If double-clicking the file does nothing, this still works — the browser is the one piece of software that definitely reads it.
And nothing is uploaded. The conversion runs on your own processor, so there is no account, no queue and no daily allowance, and a folder of saved images converts in a single pass with the results returned as one ZIP.
| AVIF | ||
|---|---|---|
| Full name | AV1 Image File Format | Portable Document Format |
| File extension | .avif | |
| Media type | image/avif | application/pdf |
| Compression | Either, depending on the setting | Either, depending on the setting |
| First published | 2019 | 1993 |
| Published by | Alliance for Open Media | Adobe |
| Specification | AV1 Image File Format | ISO 32000-2 |
| Licensing | Open standard | Open standard |
| Standing today | Current | Current |
| Bit depth | 12 | — |
| Colour it can describe | RGB, YCbCr, wide gamut | RGB, CMYK, greyscale |
| Largest image | 65,536 px per side | — |
| Opens in a browser | Current browsers | Every browser |
| Considered instead | WebP, JXL, JPG | DOCX, HTML |
PDF has nowhere to put the EXIF block — camera, lens, shutter speed and ISO and the embedded ICC colour profile, so those go no further than the AVIF. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
Nothing is discarded. AVIF and PDF both store their content losslessly, so the conversion is a change of packaging rather than a change of quality, and it can be repeated without accumulating damage.
Transparency survives. Both AVIF and PDF store an alpha channel, so a cut-out stays cut out and nothing is filled in behind it.
PDF opens in every current browser. AVIF has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
The usual programs do not overlap: AVIF opens in GIMP, Squoosh and ImageMagick, PDF in Adobe Acrobat, Preview and LibreOffice Draw — so whoever receives the result needs something from the second list.
AVIF is Alliance for Open Media's format, published in 2019. It records 12 bits per channel.
PDF comes from Adobe and dates from 1993, specified as ISO 32000-2. Adobe Acrobat, Preview and LibreOffice Draw all read it.
PDF was published in 1993 and AVIF in 2019. The older one is generally the safer file to hand to somebody; the newer one usually does the job in fewer bytes.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is pdf-lib, a PDF writer that runs entirely in JavaScript; your browser fetches it once and caches it.
It is a web delivery format. Every current browser reads it, and image viewers, older phone galleries, chat applications, email clients and print services frequently do not. The file is fine; the software around it has not caught up.
No. The picture is written into the PDF without any further lossy step, so what you see is exactly what the AVIF held. Whatever compression the image already carried from the website comes with it, since that is part of the picture now.
If the destination is a photo library, an image editor or an upload form expecting a picture, yes — JPG is the more natural file. PDF is right when the destination is a document: an email attachment, a print job, a form upload, something to be filed.
Fit to image if the file will only be looked at on a screen, which keeps the page exactly the size of the picture. A4 or US Letter if it is going to be printed or filed with other documents, where the image is centred on a real sheet.
The transparency is carried across, and a PDF page is white underneath, so a cut-out image appears on white. That is usually what people want; if it is not, place the image on the colour you need before converting.
No. The conversion runs inside your own browser, so nothing is sent anywhere — which also means it works on a machine that cannot display the AVIF at all, because the decoding happens in the browser rather than in the operating system.
The claims this page makes about AVIF and PDF are checkable, and these are the documents that settle them.