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
HEIF at a glance
HEIF
HEIF was developed by MPEG and built on the ISO Base Media File Format lineage, which helps explain why it feels more like a modern media container for images than a simple legacy bitmap file.
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.
Format comparison
| Feature | HEIF | MetaPost |
|---|---|---|
| File type | Not available | Not available |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | Not available | Not available |
| File size characteristics | Not available | Not available |
| Compatibility | Not available | Not available |
| Editability | Not available | Not available |
| Created year | Not available | Not available |
| Inventor | Not available | Not available |
| Status | Not available | Not available |
| Transparency | Not available | Not available |
| Animation | Not available | Not available |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | Not available | Not available |
| Metadata handling | Not available | Not available |
| Delivery profile | Not available | Not available |
| Workflow fit | Not available | Not available |
| Layer support | Not available | Not available |
| Vector scaling | Not available | Not available |
When to use each format
When to use HEIF
- capture ingest
- editing
- web or print delivery
- Can package richer image relationships and metadata than older flat image formats.
When to use MetaPost
- illustration
- diagramming
- brand asset delivery
- Excellent fit for programmatic technical diagrams.
FAQs
Why convert HEIF to MetaPost?
Choose MetaPost as target when precise technical diagram generation for academic papers and textbooks, mathematical figure production in TeX and LaTeX publishing workflows.
What changes when converting HEIF to MetaPost?
Precise technical diagram generation for academic papers and textbooks, mathematical figure production in TeX and LaTeX publishing workflows.
What should I review after converting HEIF to MetaPost?
After conversion, review these destination checks: Open converted output in MetaPost and verify behavior on real samples; Compare output against the expected scalable quality profile; Much narrower ecosystem than mainstream illustration formats.
How can I keep quality stable in HEIF to MetaPost conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Often converted onward for broader design or web delivery workflows; Much narrower ecosystem than mainstream illustration formats; Validate destination compatibility before large-batch conversion.