GIF87 to RST Converter
FileFlip converts GIF87 to RST entirely inside your browser, using ImageMagick, MuPDF and Pandoc compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert a GIF87 file to RST?#
- Drop your GIF87 file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to RST and the conversion starts on its own. FileFlip downloads 79.9 MB of WebAssembly the first time and nothing after that, then runs ImageMagick, MuPDF and Pandoc on your own machine.
- Save the RST file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting GIF87 to RST lose quality?#
No. The GIF87 picture is placed into the RST document at its full resolution, so every pixel reaches it intact. What you give up is that it becomes a picture inside a document rather than text.
Is it safe to convert GIF87 files online?#
Yes, because nothing is uploaded. FileFlip converts GIF87 files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What GIF87 to RST actually does to the file#
Converting GIF87 to RST runs on ImageMagick, MuPDF and Pandoc, downloads 79.9 MB of WebAssembly the first time and nothing after that, places the picture into the document at full resolution, and drops extra images.
| Engine | ImageMagick, MuPDF and Pandoc |
|---|---|
| Conversion path | 3 steps: GIF87 → PNG → HTML → RST |
| Downloaded to your browser | 79.9 MB, once, then cached by your browser |
| Quality | Pixels preserved |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Extra images | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- ImageMagick is asked for a single image, so only the first frame, page, or icon size is read
- the picture is placed in the document as a picture; no text is recognised out of it
- the file passes through HTML on the way, so anything HTML cannot express does not survive
What is a GIF87 file?#
A GIF87 file follows the original 1987 Graphics Interchange Format specification that CompuServe published two years before GIF89a added transparency and animation, so it stores a single, fully opaque image using the same LZW compression and 256-color palette as any other GIF.
There's essentially no reason to target GIF87 today; write a plain GIF, which is GIF89a, instead unless a specific tool or test needs the older header.
Convert to GIF89a or PNG when the image needs transparency or animation, since GIF87 supports neither.
What is an RST file?#
An RST file holds reStructuredText, the markup David Goodger designed in 2001 for Python documentation, where directives and interpreted text roles extend the syntax with cross-references, footnotes and generated content that Markdown has no built-in equivalent for.
Write in reStructuredText for Python documentation or any Sphinx-built site that needs directives, cross-references and generated indexes.
Convert reStructuredText to Markdown when the destination lives outside the Sphinx or Python ecosystem, since most directives don't have a Markdown equivalent.
GIF87 to RST questions people ask#
What is a GIF87 file?
A GIF87 file follows the original 1987 Graphics Interchange Format specification that CompuServe published before adding transparency and animation in 1989's GIF89a. It stores a single, fully opaque static image.
What's the difference between GIF87 and GIF89a?
GIF89a, released in 1989, added the features people now associate with GIF: transparent backgrounds, multi-frame animation, and comment or application metadata blocks. GIF87, the original 1987 version, has none of those and can only hold one static, opaque image.
Do modern browsers still support GIF87 files?
Yes. GIF89a was designed as a backward-compatible extension of GIF87, so every GIF reader that handles modern animated GIFs also reads a plain GIF87 file without any issue.
What is reStructuredText used for?
reStructuredText is the markup behind Python's own documentation and most Sphinx-built documentation sites, chosen because PEP 287 made it the standard format for Python docstrings. Its directive system lets a project define custom content types, which is why documentation with heavy cross-referencing tends to land on it over Markdown.