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
NanoMD at a glance
NanoMD
NanoMD represents the recurring tendency in documentation tooling to carve out restricted markdown subsets whenever implementers value deterministic parsing, low overhead, and minimal feature surfaces over full compatibility.
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 | NanoMD | ICB |
|---|---|---|
| File type | Document | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2020 | 1991 |
| Inventor | Community (Markdown variant) | Truevision |
| Status | active | active |
| Primary use cases |
|
|
| Vector scaling | Not supported | Not supported |
When to use each format
When to use NanoMD
- Your source file is already in NanoMD.
- Preserve source expectations before exporting to ICB.
- NanoMD is commonly used in document workflows.
When to use ICB
- Your target workflow expects ICB.
- Improve delivery compatibility with ICB.
- ICB is commonly used in image workflows.
FAQs
Why convert NanoMD 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 changes when converting NanoMD to ICB?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting NanoMD to ICB?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.