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.
MIFF at a glance
MIFF
MIFF reflects the older tradition of image-processing toolkits defining their own native technical formats for fidelity and internal workflow convenience.
Format comparison
| Feature | MetaPost | MIFF |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 1990 |
| Inventor | John Hobby | ImageMagick |
| 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 MIFF.
- MetaPost is commonly used in vector workflows.
When to use MIFF
- Your target workflow expects MIFF.
- Improve delivery compatibility with MIFF.
- MIFF is commonly used in image workflows.
FAQs
Why convert MetaPost to MIFF?
Convert to MIFF when ImageMagick or a related processing stack is the main consumer and you want a tool-native working format.
It is useful as an intermediate in automated imaging pipelines.
What changes when converting MetaPost to MIFF?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to MIFF removes vector scaling.
What should I review after converting MetaPost to MIFF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.