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.
TOD at a glance
TOD
TOD appeared with JVC's HD-capable Everio camcorders around 2006 as the high-definition counterpart to the earlier MOD format, using MPEG-2 Transport Stream rather than Program Stream to accommodate HD bitrates.
Format comparison
| Feature | Xfig | TOD |
|---|---|---|
| File type | Vector | Video |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1985 | 2004 |
| Inventor | Supoj Sutanthavibul | JVC |
| 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 TOD.
- Xfig is commonly used in vector workflows.
When to use TOD
- Your target workflow expects TOD.
- Improve delivery compatibility with TOD.
- TOD is commonly used in video workflows.
FAQs
Why convert Xfig to TOD?
Convert to TOD when preserving an original JVC Everio recording or when a legacy ingest workflow still expects the camera-native file.
More commonly, convert from TOD into MP4, MOV, or a mezzanine format during home-video migration and archive cleanup.
What changes when converting Xfig to TOD?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting Xfig to TOD?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.