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
AsciiDoc at a glance
AsciiDoc
AsciiDoc began with Stuart Rackham's early-2000s toolchain and later gained broader ecosystem momentum through Asciidoctor and the ongoing Eclipse-led specification effort.
ICB at a glance
ICB
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 | AsciiDoc | ICB |
|---|---|---|
| File type | Document | Image |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | depends | depends |
| File size characteristics | medium | medium |
| Compatibility | broad | broad |
| Editability | moderate | moderate |
| Created year | 2002 | 1991 |
| Inventor | Stuart Rackham | Truevision |
| Status | active | active |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | strong | moderate |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | exchange | delivery |
| Vector scaling | Not supported | Not supported |
When to use each format
When to use AsciiDoc
- authoring
- review and collaboration
- distribution
- Balances source readability with richer semantics than basic Markdown variants.
When to use ICB
- capture ingest
- editing
- web or print delivery
- Important for long-tail compatibility with historic Truevision-era assets.
FAQs
Why convert AsciiDoc to ICB?
Choose ICB as target when recovering historical raster assets from Truevision-era systems or normalizing old image archives before moving them into PNG, TIFF, or another contemporary format.
What changes when converting AsciiDoc to 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.
What should I review after converting AsciiDoc to ICB?
After conversion, review these destination checks: Open converted output in ImageMagick and verify behavior on real samples; Compare output against the expected depends quality profile; Weak modern software recognition compared with ordinary.tga files.
How can I keep quality stable in AsciiDoc to ICB conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Public documentation is mostly historical or secondary; Weak modern software recognition compared with ordinary.tga files; Validate destination compatibility before large-batch conversion.