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.
VST at a glance
VST
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 | VST |
|---|---|---|
| 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 MetaPost
- illustration
- diagramming
- brand asset delivery
- Excellent fit for programmatic technical diagrams.
When to use VST
- capture ingest
- editing
- web or print delivery
- Important for long-tail compatibility with historic Truevision-era assets.
FAQs
Why convert MetaPost to VST?
Choose VST as target when only when preserving or recovering early Truevision graphics assets in their original form, or when bridging those files into a contemporary raster format for access and restoration.
What changes when converting MetaPost to VST?
Convert to VST only when preserving or recovering early Truevision graphics assets in their original form, or when bridging those files into a contemporary raster format for access and restoration.
What should I review after converting MetaPost to VST?
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; Weak modern software recognition compared with ordinary.tga files.
How can I keep quality stable in MetaPost to VST conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Public documentation is mostly historical or secondary; Weak modern software recognition compared with ordinary.tga files; Validate destination compatibility before large-batch conversion.