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
Jira Markup at a glance
Jira Markup
Jira launched as issue-tracking software in 2002, and its wiki-style formatting became part of the broader Atlassian authoring model used across ticket fields, older Jira installations, and Confluence-adjacent workflows.
VDA at a glance
VDA
The Truevision line grew out of EPICenter-era PC graphics boards, and several board names ended up surviving as filename extensions even when the underlying raster structure stayed close to the wider TGA family.
Format comparison
| Feature | Jira Markup | VDA |
|---|---|---|
| File type | Document | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2002 | 1987 |
| Inventor | Atlassian | Truevision |
| Status | active | active |
| Primary use cases |
|
|
| Vector scaling | Not supported | Not supported |
When to use each format
When to use Jira Markup
- Your source file is already in Jira Markup.
- Preserve source expectations before exporting to VDA.
- Jira Markup is commonly used in document workflows.
When to use VDA
- Your target workflow expects VDA.
- Improve delivery compatibility with VDA.
- VDA is commonly used in image workflows.
FAQs
Why convert Jira Markup to VDA?
Convert to VDA when recovering or preserving historical Truevision-era graphics assets, or when normalizing a legacy image collection before moving it into PNG, TIFF, or another contemporary raster format.
What changes when converting Jira Markup to VDA?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting Jira Markup to VDA?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.