Initializing... drag & drop files here
Supports: PDF
This tool rasterises every page of your PDF and writes each one as a separate .apng file — one image per page, numbered in page order. Two things about that are worth stating plainly before you start, because most PDF-to-APNG pages gloss over them: a document source never produces an animation on this path, and each output file is a still PNG that simply carries the .apng name. If you want the pages to play as a looping flip-through in a single file, PDF to GIF is the converter that does that.
APNG is an animation format, so the expectation is reasonable — but nothing on this path ever assembles frames. A PDF is treated as a document source, and the pipeline's rule for documents is one rendered image per page: a ten-page PDF becomes ten separate files, not ten frames of one file. The frame-merging control that exists for multi-image uploads is hidden for document sources, and only the GIF target has a special branch that stitches rendered pages into an animation.
The consequence is easy to verify with any PNG inspector: a single still written out as .apng has no acTL animation-control chunk in it, which is the chunk that makes an APNG an APNG. What you get is an ordinary PNG under a different extension. That is genuinely useful for some workflows — it opens everywhere PNG does, and viewers that know APNG treat it as a one-frame animation — but if you were expecting motion, this is not the page for it.
One more detail worth knowing if you care about pixel fidelity: for alpha-capable targets the renderer hands off a PNG intermediate, but .apng is not on that list, so pages are rendered to an intermediate JPEG before the final encode. The .apng you download is losslessly compressed PNG data, but the pixels inside it passed through one JPEG generation. Choose PDF to PNG if you need the page render to stay untouched end to end.
Page dimensions are pure arithmetic: page size in inches times the DPI you pick. For US Letter (8.5 × 11 in) and A4 (8.27 × 11.69 in):
| Conversion Quality | US Letter page | A4 page | Typical use |
|---|---|---|---|
| 72 DPI | 612 × 792 px | 595 × 842 px | Thumbnail, contact sheet |
| 96 DPI | 816 × 1056 px | 794 × 1123 px | Screen preview |
| 150 DPI | 1275 × 1650 px | 1240 × 1754 px | Readable on-screen page |
| 300 DPI | 2550 × 3300 px | 2480 × 3508 px | Print-grade text and line art |
| 600 DPI | 5100 × 6600 px | 4961 × 7016 px | OCR of small type, archival scans |
| 1200 DPI | 10200 × 13200 px | 9921 × 14032 px | Fine-art detail; very large files |
| Property | APNG (this page) | PNG (PDF to PNG) | GIF (PDF to GIF) |
|---|---|---|---|
| What you get | One still per page | One still per page | One animated flip-through file |
| Animation | None on a document source | None | Yes — one page per frame |
| Render path | Intermediate JPEG, then truecolour PNG data | Straight to truecolour PNG, no lossy step | Intermediate JPEG, then a 256-colour palette |
| Alpha channel | Not offered here; pages are composited onto your chosen colour | Available — "Unchanged" keeps page transparency | 1-bit on/off only |
| Standardisation | Folded into the PNG specification, W3C Recommendation of 24 June 2025 | PNG, W3C Recommendation | GIF89a, 1989 |
| Browser support | 95.94% globally per caniuse | Universal | Universal |
| Best for | PNG-quality page images where a .apng name is required |
The default choice for page images | Showing a whole short document as one looping preview |
Because a PDF is a document source, and this converter renders documents one image per page rather than assembling frames. The frame-merge control is hidden for document input, and the animated branch exists only for the GIF target. Convert with PDF to GIF if you want a single looping file that flips through the pages.
Twenty separate image files, numbered in page order, each a full render of one page at the DPI you chose. They come back individually and as a single "Download All (Zip)" bundle, so you can keep just the pages you need. A one-page PDF returns one file.
No. The alpha-preserving "Unchanged" entry in the Image Transparency dropdown is not offered for this output, so every page is composited onto a solid colour — White unless you change it. If page transparency matters, use PDF to PNG, where "Unchanged" is available and the alpha channel survives.
No, and the label misleads a lot of people. It is the render DPI — the resolution at which each page is drawn — so raising it multiplies the pixel dimensions of every output image rather than trading quality against artefacts. Doubling the DPI roughly quadruples the pixel count. Pick it from the intended use: 150 DPI for reading on screen, 300 DPI for print-grade text, 600 DPI only if you plan to OCR small type.
No. Rasterising a page turns its text into pixels, so nothing can be selected, searched, copied or clicked afterwards, and links and form fields are gone. If you need the text to remain live, keep the PDF — or, if you only need a smaller PDF, compress the PDF instead of converting it to images.
Because a PDF stores text as glyph instructions and vectors, which is enormously more compact than a bitmap of the same page. Every output file is a full raster of one page at your chosen DPI, written with lossless PNG compression, and there is one of them per page. Dropping the Conversion Quality to 96 or 150 DPI is by far the most effective way to shrink the total.
.apng file open in normal image viewers and browsers?Yes. Each file is valid PNG data, so anything that reads PNG will display it — and because the output carries no animation chunk, even software that has never heard of APNG shows it correctly. For reference, APNG itself was folded into the official PNG specification when the Third Edition became a W3C Recommendation on 24 June 2025, and caniuse puts browser support at 95.94% of global traffic.
Your PDF is uploaded over an encrypted connection, rendered on our servers, and deleted automatically after a few hours — never shared, never made public. There is no sign-up and no watermark. On a long document rendered at high DPI, the practical constraint is upload and download size rather than the conversion itself, since each page becomes its own full-resolution image.