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
Xfig at a glance
Xfig
Xfig began in 1985 and accumulated decades of maintenance and export tooling, which made the .fig format a durable bridge between interactive diagram editing on Unix systems and downstream conversion to PostScript, PDF, and other outputs.
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 | Xfig | ICNS |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1985 | 2000 |
| Inventor | Supoj Sutanthavibul | Apple |
| Status | legacy | 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 Xfig
- Your source file is already in Xfig.
- Preserve source expectations before exporting to ICNS.
- Xfig 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 Xfig 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 Xfig 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 Xfig to ICNS?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.