Jira to ICON Converter
FileFlip converts Jira to ICON entirely inside your browser, using Pandoc, MuPDF and ImageMagick 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 Jira file to ICON?#
- Drop your Jira 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 ICON and the conversion starts on its own. FileFlip downloads 79.9 MB of WebAssembly the first time and nothing after that, then runs Pandoc, MuPDF and ImageMagick on your own machine.
- Save the ICON file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting Jira to ICON lose quality?#
Yes, in the sense that text stops being text. Each Jira page is rendered to pixels and handed to ICON, so the result looks right and can no longer be selected, searched, or reflowed.
Is it safe to convert Jira files online?#
Yes, because nothing is uploaded. FileFlip converts Jira 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 Jira to ICON actually does to the file#
Converting Jira to ICON runs on Pandoc, MuPDF and ImageMagick, downloads 79.9 MB of WebAssembly the first time and nothing after that, renders each page to pixels, keeps page layout, and drops selectable text and transparency.
| Engine | Pandoc, MuPDF and ImageMagick |
|---|---|
| Conversion path | 3 steps: Jira → HTML → PNG → ICON |
| Downloaded to your browser | 79.9 MB, once, then cached by your browser |
| Quality | Text becomes pixels |
| You get back | One image per page, zipped when the source has several |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Selectable text | Dropped | The target format has nowhere to put it. |
| Page layout | Kept | Carried through into the converted file. |
| Transparency | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- pages render at twice their point size in opaque RGB, roughly 144 DPI, with no transparency
- reflowable input is laid out on a fixed 595x842pt page at 11pt before anything else happens
- the file passes through HTML on the way, so anything HTML cannot express does not survive
What is a Jira file?#
A JIRA file holds text written in Jira wiki markup, Atlassian's plain-text syntax for bold text, tables, and code blocks that was once typed directly into issue descriptions and comments.
Reach for Jira wiki markup when scripting issues through the REST API's legacy text fields, or working in a Jira Server or Data Center instance that still edits comments and descriptions as wiki markup directly.
Convert Jira wiki markup to another format when moving issue content into documentation, a wiki, or anywhere outside Jira and Confluence.
What is an ICON file?#
ICON is ImageMagick's alternate name for the ICO format, the container Windows uses for small multi-resolution images shown as application, file and shortcut icons, so a file written as ICON is the same Windows icon container as one written as ICO.
Use ICON, or the equivalent ICO, for Windows application icons, favicons and shortcut images, where the file needs to offer several sizes in one container.
Convert to PNG when a single-resolution image is needed for general use, since most software outside Windows icon contexts doesn't expect an ICO/ICON container.
Jira to ICON questions people ask#
Is Jira wiki markup still used?
Jira wiki markup is no longer the storage format in Jira Cloud, which switched to the Atlassian Document Format, a JSON structure produced by a rich-text editor. It still shows up in Jira Server and Data Center instances, in older exports, and in some legacy REST API fields, which is why converters still need to read it.
Why doesn't my Markdown work when pasted into Jira?
Jira's comment and description fields use their own wiki markup, not Markdown, and the two syntaxes overlap just enough to cause confusion, such as asterisks meaning different things in each. Pasted Markdown symbols are usually shown as literal characters instead of being rendered as formatting.
What's the difference between Jira markup and Confluence markup?
Jira wiki markup and Confluence wiki markup come from the same Atlassian syntax family and share most of their formatting rules for bold text, lists, and tables. Confluence adds more macro and layout syntax for building full pages, since Jira's markup only ever had to fill in an issue description or a comment.
What is the difference between ICON and ICO?
There isn't one. ICON is ImageMagick's alternate name for its ICO coder, so a file written as ICON is the same Windows icon container as one written as ICO.