Getting AVIF images into something anyone can open
AVIF renders in every current browser and almost nothing else. That makes a PDF an unusually useful destination: it is the one document format that opens everywhere, on any device, without a codec question.
Add your images, check the order, and build. Each becomes a page sized to the image itself.
Expect a considerably larger file than the AVIFs you started with — see below for why that is arithmetic rather than a fault.
Why the images are re-encoded
PDF is older than every format on this page, and it understands only two kinds of image data: JPEG and PNG.
That means a AVIF cannot simply be dropped into a document. It has to be decoded back to pixels and re-encoded as JPEG before it can become a page.
Doing that here rather than making you convert twice is the point of this page. Nobody should need to know that PDF has never heard of AVIF.
The cost is one extra lossy step, done at a high quality setting. If you want to avoid it entirely, convert to JPG first at whatever quality you prefer, then use the JPG to PDF page.
Expect the PDF to be larger than the images
AVIF compresses more efficiently than JPEG. Storing the same pictures in the format PDF can read therefore costs more space.
That is not a failed conversion — it is the price of a document that opens on anything. If size matters more than convenience, compress the images before building.
Nothing is transmitted
The decode, the re-encode and the assembly all happen in this browser tab, using the same codecs the rest of the site uses and pdf-lib for the document itself.
The Uploaded readout beside the result measures this page’s own outbound network calls directly, and reads 0 B on a successful build. That matters here more than on most pages: images people bind into PDFs are usually documents rather than snapshots.
Questions
- Can a PDF contain AVIF images directly?
- No. PDF understands JPEG and PNG image data and nothing else of this kind, so a AVIF has to be decoded and re-encoded before it can become a page. This tool does that step for you, which is why you do not need to convert twice.
- Does that re-encoding lose quality?
- A little, since AVIF and JPEG are both lossy and the image passes through a second encoder. It is done at a high quality setting, so the difference is not visible at normal viewing sizes. Your original files are never modified.
- How do I control the page order?
- The list is the order. Use the arrows beside each file to move it up or down before building, and the cross to remove one added by mistake.
- Is there a limit on how many images I can include?
- None imposed. There is no upload and no server, so your device's memory is the only ceiling.
- Will the PDF have a watermark?
- No. Nothing is stamped onto the pages, and no feature is held back behind a paid tier.
- Are my images uploaded?
- No. The decode, the re-encode and the PDF assembly all happen in this browser tab. The Uploaded readout beside the result measures the page's own outbound traffic, so a successful build reads 0 B.
- Does each page match the image size?
- Yes. Pages are sized to their image rather than forced onto A4 or Letter, so nothing is cropped and nothing is letterboxed.
- Why is my PDF larger than the images I started with?
- Because AVIF compresses more efficiently than JPEG, and JPEG is what PDF can store. Storing the same pictures in an older format costs more space — that is the price of a document anyone can open.
- Can I mix formats in one PDF?
- Each page here handles one input format so the conversion path stays predictable. Build separate PDFs and then merge them if you need a mixed document.
- What happens to transparency?
- It is lost. JPEG has no alpha channel, and PDF pages have a white background, so transparent areas become white.