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.
MOS at a glance
MOS
Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
Format comparison
| Feature | Xfig | MOS |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | scalable | raw |
| File size characteristics | small | large |
| Compatibility | moderate | limited |
| Editability | high | high |
| Created year | 1985 | 2003 |
| Inventor | Supoj Sutanthavibul | Leaf (now Phase One) |
| Status | legacy | proprietary |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | good | strong |
| Metadata handling | moderate | rich |
| Delivery profile | strong | limited |
| Workflow fit | design | source |
| Layer support | Not supported | Not supported |
| Vector scaling | 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 MOS
- capture ingest
- editing
- web or print delivery
- Preserve capture-stage image data for later interpretation.
FAQs
Why convert Xfig to MOS?
Choose MOS as target when maintaining compatibility with Leaf-originated capture files or preserving source material from medium-format studio workflows.
What changes when converting Xfig to MOS?
Convert to MOS when maintaining compatibility with Leaf-originated capture files or preserving source material from medium-format studio workflows. It is primarily an archival and editing format.
What should I review after converting Xfig to MOS?
After conversion, review these destination checks: Open converted output in LibRaw and verify behavior on real samples; Compare output against the expected raw quality profile; Many are vendor-specific and poorly documented publicly.
How can I keep quality stable in Xfig to MOS conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software; Many are vendor-specific and poorly documented publicly; Validate destination compatibility before large-batch conversion.