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.
MQV at a glance
MQV
The .mqv extension appeared on some Sony camcorders and recording devices around the mid-2000s as an internal variant of the QuickTime/MOV container carrying Sony-proprietary metadata tracks and stream wrappers.
Format comparison
| Feature | MetaPost | MQV |
|---|---|---|
| File type | Vector | Video |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 2007 |
| 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 MQV.
- MetaPost is commonly used in vector workflows.
When to use MQV
- Your target workflow expects MQV.
- Improve delivery compatibility with MQV.
- MQV is commonly used in video workflows.
FAQs
Why convert MetaPost to MQV?
Convert to or from MQV when migrating recordings off older Sony consumer devices, preserving original camera exports, or normalizing a proprietary Sony library into MP4, MOV, or another easier editing format.
It is primarily a legacy-ingest and archive-recovery format.
What changes when converting MetaPost to MQV?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting MetaPost to MQV?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.