Convert anything, at global scale.
200+ formats and automation APIs that feels instant.
CONVERT
From
To
Drop files or choose a source
Upload multiple files at once, mix formats, and fine-tune every conversion with format-aware settings.
Max 2GB per file · Drag & drop ready · Mixed file types welcome
ICB at a glance
ICB
Convert to ICB when recovering historical raster assets from Truevision-era systems or normalizing old image archives before moving them into PNG, TIFF, or another contemporary format.
It is mainly a compatibility target for legacy graphics collections.
Jira Markup at a glance
Jira Markup
Convert to Jira Markup when content must round-trip through older Jira or Confluence workflows, when exporting or importing issue text through scripts, or when translating Atlassian-authored content into Markdown, HTML, or another publishing format.
It is mainly useful for migration and interoperability inside Atlassian-heavy environments.
Format comparison
| Feature | ICB | Jira Markup |
|---|---|---|
| File type | Image | Document |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | depends | depends |
| File size characteristics | medium | medium |
| Compatibility | broad | broad |
| Editability | moderate | moderate |
| Created year | 1991 | 2002 |
| Inventor | Truevision | Atlassian |
| Status | active | active |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | moderate | strong |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | delivery | exchange |
| Vector scaling | Not supported | Not supported |
When to use each format
When to use ICB
- capture ingest
- editing
- web or print delivery
- Important for long-tail compatibility with historic Truevision-era assets.
When to use Jira Markup
- authoring
- review and collaboration
- distribution
- Easy to author in plain text for issue comments and descriptions.
FAQs
Why convert ICB to Jira Markup?
Convert to Jira Markup when content must round-trip through older Jira or Confluence workflows, when exporting or importing issue text through scripts, or when translating Atlassian-authored content into Markdown, HTML, or another publishing format.
It is mainly useful for migration and interoperability inside Atlassian-heavy environments.
What changes when converting ICB to Jira Markup?
This conversion changes how the format behaves in downstream tools and delivery environments.
Archival profile changes from moderate in ICB to strong in Jira Markup. Workflow profile changes from delivery in ICB to exchange in Jira Markup.
What should I review after converting ICB to Jira Markup?
Check the exported file for It is a vendor-specific legacy syntax rather than a broadly portable documentation standard.; Modern Atlassian cloud editing increasingly emphasizes richer structured editing rather than raw wiki-style source..