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.
VDA at a glance
VDA
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 | Xfig | VDA |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1985 | 1987 |
| Inventor | Supoj Sutanthavibul | Truevision |
| Status | legacy | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Vector scaling | 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 VDA.
- Xfig is commonly used in vector workflows.
When to use VDA
- Your target workflow expects VDA.
- Improve delivery compatibility with VDA.
- VDA is commonly used in image workflows.
FAQs
Why convert Xfig to VDA?
Convert to VDA when recovering or preserving historical Truevision-era graphics assets, or when normalizing a legacy image collection before moving it into PNG, TIFF, or another contemporary raster format.
What changes when converting Xfig to VDA?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to VDA removes vector scaling.
What should I review after converting Xfig to VDA?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.