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.
PMD at a glance
PMD
The .pmd extension appeared in Sony's prosumer and professional recording device output alongside other Sony-proprietary formats like MQV, serving as a companion metadata or media descriptor file.
Format comparison
| Feature | MetaPost | PMD |
|---|---|---|
| File type | Vector | Video |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 2004 |
| Inventor | John Hobby | Sony |
| Status | active | legacy |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not 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 PMD.
- MetaPost is commonly used in vector workflows.
When to use PMD
- Your target workflow expects PMD.
- Improve delivery compatibility with PMD.
- PMD is commonly used in video workflows.
FAQs
Why convert MetaPost to PMD?
Convert to PMD when maintaining compatibility with a Sony-centered production workflow, preserving source media from a professional ingest system, or migrating archived broadcast assets that were originally wrapped for structured editorial exchange.
What changes when converting MetaPost to PMD?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting MetaPost to PMD?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.