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
Xfig at a glance
Xfig
Xfig began in 1985 and accumulated decades of maintenance and export tooling, which made the .fig format a durable bridge between interactive diagram editing on Unix systems and downstream conversion to PostScript, PDF, and other outputs.
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 | Xfig | MQV |
|---|---|---|
| File type | Vector | Video |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1985 | 2007 |
| Inventor | Supoj Sutanthavibul | Sony |
| Status | legacy | 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 Xfig
- Your source file is already in Xfig.
- Preserve source expectations before exporting to MQV.
- Xfig 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 Xfig 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 Xfig to MQV?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting Xfig to MQV?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.