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
IIQ at a glance
IIQ
Phase One positioned IIQ around its medium-format and digital-back workflows, which is why IIQ appears in a very different professional context from ordinary consumer camera raws.
CRW at a glance
CRW
Early Canon digital-camera workflows used raw formats like CRW before the later EOS raw families stabilized around CR2 and then CR3.
Format comparison
| Feature | IIQ | CRW |
|---|---|---|
| File type | Image | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2007 | 2000 |
| Inventor | Phase One | Canon |
| Status | proprietary | proprietary |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Vector scaling | Not supported | Not supported |
| Camera raw data | Supported | Supported |
| HDR support | Not supported | Not supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use IIQ
- Your source file is already in IIQ.
- Preserve source expectations before exporting to CRW.
- IIQ is commonly used in image workflows.
When to use CRW
- Your target workflow expects CRW.
- Improve delivery compatibility with CRW.
- CRW is commonly used in image workflows.
FAQs
Why convert IIQ to CRW?
Convert to CRW when maintaining compatibility with older Canon raw libraries or recovering historical camera originals.
In most current workflows it is a source to preserve or migrate, not a preferred new output format.
What changes when converting IIQ to CRW?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting IIQ to CRW?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.