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.
3G2 at a glance
3G2
3G2 belongs to an era when mobile ecosystems were more fragmented across standards families, carriers, and handset capabilities.
Format comparison
| Feature | Xfig | 3G2 |
|---|---|---|
| File type | Vector | Video |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | scalable | depends |
| File size characteristics | small | large |
| Compatibility | moderate | moderate |
| Editability | high | limited |
| Created year | 1985 | 2004 |
| Inventor | Supoj Sutanthavibul | 3GPP2 |
| Status | legacy | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | good | moderate |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | design | delivery |
| Layer support | Not supported | Not supported |
When to use each format
When to use Xfig
- illustration
- diagramming
- brand asset delivery
- Preserves object-level editability for technical diagrams.
When to use 3G2
- editing
- mastering
- streaming delivery
- Useful for long-tail mobile-media compatibility.
FAQs
Why convert Xfig to 3G2?
Choose 3G2 as target when preserving compatibility with legacy CDMA handset recordings, telecom media archives, or workflows that explicitly expect 3GPP2-style mobile video.
What changes when converting Xfig to 3G2?
Convert to 3G2 when preserving compatibility with legacy CDMA handset recordings, telecom media archives, or workflows that explicitly expect 3GPP2-style mobile video. It is useful for migration and recovery of old phone clips. For current playback and sharing, MP4 is almost always the better destination.
What should I review after converting Xfig to 3G2?
After conversion, review these destination checks: Open converted output in older phones and verify behavior on real samples; Compare output against the expected depends quality profile; Mostly legacy today.
How can I keep quality stable in Xfig to 3G2 conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Recipients usually prefer conversion into more current containers; Mostly legacy today; Validate destination compatibility before large-batch conversion.