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.
VDA at a glance
VDA
The Truevision line grew out of EPICenter-era PC graphics boards, and several board names ended up surviving as filename extensions even when the underlying raster structure stayed close to the wider TGA family.
Format comparison
| Feature | MetaPost | VDA |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 1987 |
| Inventor | John Hobby | Truevision |
| Status | active | active |
| 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 VDA.
- MetaPost is commonly used in vector workflows.
When to use VDA
- Your target workflow expects VDA.
- Improve delivery compatibility with VDA.
- VDA is commonly used in image workflows.
FAQs
Why convert MetaPost to VDA?
Convert to VDA when recovering or preserving historical Truevision-era graphics assets, or when normalizing a legacy image collection before moving it into PNG, TIFF, or another contemporary raster format.
What changes when converting MetaPost to VDA?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to VDA removes vector scaling.
What should I review after converting MetaPost to VDA?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.