Initializing... drag & drop files here
Supports: DOCX
APNG is PNG with animation chunks bolted on — same lossless pixels, same alpha channel, plus optional frames. This converter renders a Word .docx page by page and writes each page as its own APNG file: a 6-page document produces 6 images, each holding a single full-page frame. That surprises people who expect a flip-through animation, so it is worth saying up front — if you want one looping file that pages through the document, that is DOCX to GIF, which really does assemble the pages into a single animated file.
| Property | Value |
|---|---|
| Full name | Animated Portable Network Graphics |
| Specification | Part of the PNG Specification (Third Edition), a W3C Recommendation published 24 June 2025 |
| Origin | Long maintained as a Mozilla-led extension to PNG before being folded into the official spec |
| Animation chunks | acTL (animation control), fcTL (frame control), fdAT (frame data) |
| Compression | Lossless, identical to PNG — DEFLATE over filtered scanlines |
| Colour | Indexed, greyscale or truecolour, sample depths from 1 to 16 bits, with optional alpha |
| Fallback | Decoders that don't understand the animation chunks display the default image — a normal PNG |
| MIME type | image/apng |
| Extensions | .apng, and .png |
| APNG (this page) | DOCX to GIF | DOCX to PNG | |
|---|---|---|---|
| Output for a 6-page file | 6 still images | 1 animated file | 6 still images |
| Animation | None — one frame per file | Yes, pages play in sequence | None |
| Colour depth | Full colour, lossless | Palette, up to 256 colours | Full colour, lossless |
| Transparency | Format supports alpha; output here has a solid background | Single-colour transparency only | Yes — choose "Unchanged" |
| Best for | Lossless page images with an .apng extension |
A quick looping preview of a whole document | The default choice for page images |
.docx onto the drop zone or click "Add Files". Pagination is worked out first, so you get one image per page in document order.The document is laid out with LibreOffice on our servers and printed to an internal PDF, which fixes pagination exactly as Word would print it. Each PDF page is then rasterised at the DPI you chose and encoded as an APNG. Because each page is encoded on its own, every output file contains exactly one frame — the animation chunks that make APNG interesting are never written. There is no "Combine?" control on this page, and no frame-rate setting, for that reason.
Note also that the "Image Compression" and "Quality Preset" controls you see on the PNG or JPG pages are not shown here: APNG encoding is lossless, so there is no quality dial to turn. Only the render DPI and the "Image resolution" controls change the size of the result.
Because this conversion never builds an animation. Each page is rendered and encoded separately, so every file carries a single frame and there is nothing to play. That is a deliberate limitation of the document-to-image path, not a failed animation. For a genuine page-flip through the whole document, convert with DOCX to GIF instead, which stitches the rendered pages into one animated file.
Yes — one image per page, numbered in document order. A 6-page file gives 6 images, a 1-page file gives one. When there is more than one output image, a "Download All (Zip)" button appears next to the result so you can take the whole set as a single archive.
The still-image machinery is identical: same lossless DEFLATE compression, same colour models, same alpha channel. APNG adds three chunks — acTL, fcTL and fdAT — that describe a frame sequence, and specifies that any decoder which ignores them must show the default image. Since 2025 this is not an extension at all but part of the PNG specification's Third Edition, a W3C Recommendation.
For practical purposes, yes. Each file here holds one frame and is structurally a PNG, so anything that reads PNG reads it — that fallback behaviour is written into the specification. If a program refuses the file purely because of the .apng extension, the simplest fix is to convert with DOCX to PNG instead and get identical page images with a name the program expects.
Not from this page. The Color dropdown under "Image Transparency" always composites the page onto a solid colour — White by default — and the "Unchanged" option that preserves alpha is offered only for PNG output. If you need see-through areas behind the page, use DOCX to PNG and set Image Transparency to "Unchanged".
No pixels are lost when the image is encoded — APNG uses PNG's lossless compression, so what the renderer produced is exactly what lands in the file. What is lost is the document itself: text becomes pixels, so it is no longer selectable, searchable, or editable, and the layout can no longer reflow. Keep the original .docx, or export a PDF, if you need the text to stay live.
300 DPI, the default, renders an A4 page at roughly 2480 × 3508 pixels and keeps body text print-sharp. Drop to 96 or 150 DPI for a small on-screen preview; go to 400 or 600 DPI for tiny footnotes or archival copies. Because pixel count scales with the square of the DPI, and because the output is lossless, a long document at 600 DPI produces a large stack of files — cut the DPI first if the results are too heavy to send.
Layout is performed by LibreOffice, so any font the document calls for that is not installed on the server is swapped for a metrically similar substitute — pagination usually holds, glyph shapes can shift. Embedding fonts in the .docx, or sticking to widely available families, gives the closest match. Password-protected or damaged files cannot be opened for rendering; remove the protection in Word and upload again.
It is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public.