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.
FFF at a glance
FFF
Hasselblad's workflow tooling treated raw capture and high-end processing as parts of one integrated medium-format imaging environment, which is why formats like FFF survive in specialist archives.
Format comparison
| Feature | MetaPost | FFF |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 2002 |
| Inventor | John Hobby | Hasselblad |
| Status | active | proprietary |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | 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 FFF.
- MetaPost is commonly used in vector workflows.
When to use FFF
- Your target workflow expects FFF.
- Improve delivery compatibility with FFF.
- FFF is commonly used in image workflows.
FAQs
Why convert MetaPost to FFF?
Convert to FFF when maintaining compatibility with a specialized high-end imaging archive or recovering source material from that ecosystem.
It is mainly an archival and specialist workflow format.
What changes when converting MetaPost to FFF?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to FFF adds layer support. Moving to FFF removes vector scaling.
What should I review after converting MetaPost to FFF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.