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
PAGES at a glance
PAGES
Pages emerged as part of iWork, offering an alternative to Microsoft Office shaped by Apple's design and document-authoring philosophy.
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 | PAGES | ICB |
|---|---|---|
| File type | Document | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2005 | 1991 |
| Inventor | Apple | Truevision |
| Status | active | active |
| Primary use cases |
|
|
| Vector scaling | Not supported | Not supported |
When to use each format
When to use PAGES
- Your source file is already in PAGES.
- Preserve source expectations before exporting to ICB.
- PAGES 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 PAGES 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 PAGES to ICB?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting PAGES to ICB?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.