INLINE Converter
FileFlip converts INLINE files into 62 other formats entirely inside your browser, using ImageMagick, MuPDF and Pandoc compiled to WebAssembly. The INLINE file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. There is no file-size limit and no account to create.
How do I convert an INLINE file?#
- Drop your INLINE file onto the converter at the top of this page, or click it to pick one from your computer.
- Choose the format you want out of it. FileFlip downloads the engine that conversion needs, once, and your browser caches it.
- Conversion starts the moment you pick the format, and the result is yours to download. The work happens in this tab, so nothing is uploaded and nothing is queued.
Is it safe to convert INLINE files online?#
Yes, because nothing is uploaded. FileFlip converts INLINE 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 happens to a INLINE file#
FileFlip converts INLINE into 62 formats with ImageMagick, MuPDF and Pandoc, all of it inside the browser tab. Each conversion below names the engine it uses, what it downloads, and exactly what that conversion keeps or drops.
| Category | Image Files |
|---|---|
| File extension | .inline |
| FileFlip support | Read only, so it is a source rather than a target |
| Conversions available | 62 |
| Engines | ImageMagick, MuPDF and Pandoc |
| Downloaded to your browser | 14.1 MB on the first conversion, then cached |
What is an INLINE file?#
An INLINE reference is not a file at all but ImageMagick's own syntax, inline:, for handing it an image that already exists as base64 text, such as a data: URI copied out of an HTML page or an API response.
Use the inline: syntax when an image already exists as base64 text, such as a data: URI pulled from HTML or JSON, and it needs to be read without writing a temporary file first.
There is nothing to convert away from: inline: is a way of pointing ImageMagick at an image, not a format a finished file is ever saved in.
The INLINE file format reference covers the specification, the programs that open one, and what each conversion keeps or drops.
INLINE questions people ask#
What is an INLINE file?
INLINE isn't a file format, it's ImageMagick's inline: syntax for reading an image supplied as base64 text, most often a data: URI. The base64 data can come from a text file or be typed directly after inline: on the command line.
Can I save or write a file as INLINE?
No. The inline: mechanism in ImageMagick only reads base64-encoded images; there is no corresponding way to write one back out, so a converter that reads INLINE decodes the base64 into whichever image format was actually encoded inside it.
Why does my base64 image fail when pasted as inline:?
Typing a base64 string directly after inline: on a command line is limited to 5000 characters in ImageMagick, so a photo-sized data URI will fail there even though it works from a text file. The comma after the MIME type is also required to mark where the base64 data starts, even though ImageMagick otherwise ignores the MIME type itself.