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
MetaPost at a glance
MetaPost
John Hobby developed MetaPost from MetaFont ideas, and the system later evolved into the MPlib era so TeX and LuaTeX workflows could keep high-quality vector graphics close to typeset documents.
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.
Format comparison
| Feature | MetaPost | IIQ |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 2007 |
| Inventor | John Hobby | Phase One |
| 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 MetaPost
- Your source file is already in MetaPost.
- Preserve source expectations before exporting to IIQ.
- MetaPost is commonly used in vector workflows.
When to use IIQ
- Your target workflow expects IIQ.
- Improve delivery compatibility with IIQ.
- IIQ is commonly used in image workflows.
FAQs
Why convert MetaPost to IIQ?
Convert to IIQ when preserving Phase One originals or keeping compatibility with medium-format studio workflows built around Capture One and Phase One hardware.
It is an archival and editing format for premium photographic production.
What changes when converting MetaPost to IIQ?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to IIQ removes vector scaling.
What should I review after converting MetaPost to IIQ?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.