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
CDR at a glance
CDR
CorelDRAW was developed by Corel engineers Michel Bouillan and Pat Beirne in 1987 to bundle with Corel's desktop publishing systems. The inclusion of TrueType support in Windows 3.1 transformed CorelDRAW into a serious illustration program.
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 | CDR | ICNS |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1989 | 2000 |
| Inventor | Corel Corporation | Apple |
| Status | active | proprietary |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Vector scaling | Supported | Not supported |
When to use each format
When to use CDR
- Your source file is already in CDR.
- Preserve source expectations before exporting to ICNS.
- CDR is commonly used in vector 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 CDR 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 CDR to ICNS?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to ICNS removes vector scaling.
What should I review after converting CDR to ICNS?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.