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.
XPM at a glance
XPM
Before today's relatively small set of mainstream consumer image formats dominated everyday use, desktop software, workstations, GUI systems, and early graphics tools produced many specialized raster formats with local importance.
Format comparison
| Feature | MetaPost | XPM |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | scalable | depends |
| File size characteristics | small | medium |
| Compatibility | moderate | broad |
| Editability | high | moderate |
| Created year | 1994 | 1989 |
| Inventor | John Hobby | Daniel Dardailler, Colas Nahaboo (Groupe Bull) |
| Status | active | legacy |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | good | moderate |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | design | delivery |
| Layer support | Not supported | Not supported |
| Vector scaling | Supported | Not supported |
When to use each format
When to use MetaPost
- illustration
- diagramming
- brand asset delivery
- Excellent fit for programmatic technical diagrams.
When to use XPM
- capture ingest
- editing
- web or print delivery
- Important for long-tail compatibility and archival conversion.
FAQs
Why convert MetaPost to XPM?
Choose XPM as target when maintaining or restoring X11-era icon assets or other historical Unix interface graphics.
What changes when converting MetaPost to XPM?
Convert to XPM when maintaining or restoring X11-era icon assets or other historical Unix interface graphics. It is useful where text-based icon compatibility matters more than modern compression.
What should I review after converting MetaPost to XPM?
After conversion, review these destination checks: Open converted output in ImageMagick and verify behavior on real samples; Compare output against the expected depends quality profile; Poor fit for modern mainstream publishing.
How can I keep quality stable in MetaPost to XPM conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Tool support can be uneven and workflow-specific; Poor fit for modern mainstream publishing; Validate destination compatibility before large-batch conversion.