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
CR3 at a glance
CR3
CR3 marks Canon's move into a newer raw-file generation as mirrorless and later-camera workflows evolved beyond the long CR2 era.
ICNS at a glance
ICNS
ICNS reflects the Mac graphics-resource tradition where a single icon asset is really a packaged set of representations for one application or object identity.
Format comparison
| Feature | CR3 | ICNS |
|---|---|---|
| File type | Image | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2018 | 2000 |
| Inventor | Canon | Apple |
| 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 | Not supported |
| HDR support | Not supported | Not supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use CR3
- Your source file is already in CR3.
- Preserve source expectations before exporting to ICNS.
- CR3 is commonly used in image workflows.
When to use ICNS
- Your target workflow expects ICNS.
- Improve delivery compatibility with ICNS.
- ICNS is commonly used in image workflows.
FAQs
Why convert CR3 to ICNS?
Convert to ICNS when creating or updating macOS application icons or preserving Apple-specific icon assets.
It is the correct target when a Mac application bundle or desktop asset workflow expects native icon resources.
What changes when converting CR3 to ICNS?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to ICNS removes camera raw data.
What should I review after converting CR3 to ICNS?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.