Initializing... drag & drop files here
Supports: DOCX
Turn a Word document into a single animated GIF that flips through its pages — handy for previewing a report in a chat message, showing a document in a README or forum post where PDFs will not embed, or dropping a paging preview into a slide. Each page of the document becomes one frame of the animation, so a six-page document produces a six-frame GIF. The one setting worth changing before you convert is Framerate, because the default plays pages far faster than anyone can read them.
.docx onto the page or click "+ Add Files" to browse. Queue several documents to convert them in one batch — each document becomes its own GIF.Frame delay is simply the inverse of the framerate, so the setting decides how long each page stays on screen. This catches people out: at the default, a document is gone before you can read a heading. We converted a three-page A4 document and measured the resulting animation at both ends of the range:
| Framerate | Time each page is shown | Total length, 3-page document | Good for |
|---|---|---|---|
| 1 FPS (Slideshow) | 1 second | 3.0 seconds (measured) | Reading along; short documents |
| 2 FPS | 0.5 seconds | 1.5 seconds | A brisk but followable flip |
| 5 FPS | 0.2 seconds | 0.6 seconds | Skimming a longer document |
| 10 FPS (default) | 0.1 seconds | 0.3 seconds (measured) | A fast riffle-through effect |
| 30–50 FPS | 0.03–0.02 seconds | Under 0.1 seconds | Long documents where only motion matters |
A useful rule: pick the framerate so total length lands between three and ten seconds. For a 20-page document that means about 5 FPS; for a 3-page document, 1 FPS.
| Control | Default | What it actually changes |
|---|---|---|
| Framerate | 10 FPS (Recommended) | How long each page is displayed before the next |
| Conversion Quality | 300 DPI (High Quality / Print Recommended) | Render sharpness of each page before it becomes a frame |
| File Compression | Quality preset: High | Quality preset trades size against fidelity; Max file size caps the output; Custom reveals the two controls below |
| Image resolution (File Compression → Custom) | Keep original | The finished pixel dimensions of the animation |
| Image quality (%) (File Compression → Custom) | 80% | Encoder effort, trading file size against banding and noise |
| Colors (File Compression → Custom) | Original palette | Shown, but not read on the document route — the encoder builds its own palette per frame |
| Image Transparency → Color | White | The page background painted behind the text |
Because the framerate defaults to 10 FPS, which gives each page one tenth of a second. That default suits video sources, where 10 FPS is a reasonable animation rate, but a document page needs far longer on screen. Set Framerate to 1 FPS (Slideshow) or 2 FPS and convert again — in our testing a three-page document went from 0.3 seconds total at the default to a readable 3.0 seconds at 1 FPS.
One GIF. Unlike converting a document to JPG or PNG, where every page becomes a separate image, the GIF conversion assembles all the pages into a single animated file with one frame per page. If you want individual page images instead, use DOCX to JPG or DOCX to PNG.
You still get a valid GIF. The format needs at least two frames to be a legitimate animation, so a single page is written as a repeated frame. The result looks like a still image, which is usually what you want from a one-page document — though a genuine still in PNG or JPG will be sharper and smaller.
The GIF encoder applies its own size ceiling of roughly 800 × 600 worth of pixels unless you tell it otherwise, so raising Conversion Quality alone will not give you a bigger animation. In our testing, three A4 pages rendered at the default 300 DPI (about 2481 × 3508 pixels each) came back as a 620 × 877 GIF. To control the finished size, set Image resolution explicitly (under File Compression → Custom) rather than relying on the DPI setting.
GIF is limited to 256 colours per frame, so the smooth grey edges that make small text look crisp have to be approximated. Anti-aliased body text is the hardest case. Raise Conversion Quality so the source pages are rendered more finely, and keep the File Compression Quality preset high — palette choice itself is automatic on this route. For genuinely sharp document text, PNG is a much better fit — it is not limited to 256 colours and has no lossy block compression.
Not on this conversion. The document is painted onto a solid background before it becomes frames, and the Image Transparency control offers White by default plus 23 other named colours. Choose a colour that matches wherever you are embedding the GIF, or use DOCX to PNG if you need an alpha channel.
Three levers, in order of effect. Cap the output directly with File Compression → Max file size — pick a preset such as Forum (2 MB max) or type your own ceiling. Or reduce Image resolution (under File Compression → Custom), since pixel count dominates the file size, and drop Conversion Quality to 150 or 96 DPI. Finally lower the framerate, which trims a little overhead per frame. You can also run the finished file through GIF compression.
It loops continuously, and frames follow document page order, so the animation runs from page one to the last page and starts again. There is no reverse or ping-pong option and no per-page timing — every frame gets the same delay, set by the framerate. To show only part of a document, delete the unwanted pages in Word before uploading.
For document pages, often yes. APNG keeps full 24-bit colour and a real alpha channel, so text edges stay clean instead of being forced into 256 colours — the trade is a larger file and slightly narrower support than GIF, which every platform accepts. If your target is a chat app, forum, or older tooling, stay with GIF; if it is a modern browser and text crispness matters most, consider a still image or an APNG instead.