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.
ERF at a glance
ERF
Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
Format comparison
| Feature | MetaPost | ERF |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 2004 |
| Inventor | John Hobby | Epson |
| 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 ERF.
- MetaPost is commonly used in vector workflows.
When to use ERF
- Your target workflow expects ERF.
- Improve delivery compatibility with ERF.
- ERF is commonly used in image workflows.
FAQs
Why convert MetaPost to ERF?
Convert to ERF when preserving or restoring Epson-origin raw captures in an archive or compatibility workflow.
In most contemporary pipelines, it is a legacy source format to retain or migrate.
What changes when converting MetaPost to ERF?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to ERF removes vector scaling.
What should I review after converting MetaPost to ERF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.