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.
ORF at a glance
ORF
ORF belongs to the long Olympus digital-camera story, especially in the Four Thirds and Micro Four Thirds eras where portability and serious editing often coexisted.
Format comparison
| Feature | Xfig | ORF |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1985 | 2003 |
| Inventor | Supoj Sutanthavibul | Olympus (now OM System) |
| Status | legacy | proprietary |
| 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 ORF.
- Xfig is commonly used in vector workflows.
When to use ORF
- Your target workflow expects ORF.
- Improve delivery compatibility with ORF.
- ORF is commonly used in image workflows.
FAQs
Why convert Xfig to ORF?
Convert to ORF when preserving Olympus camera originals or maintaining compatibility with an Olympus raw-photo workflow.
It is useful for archive masters and non-destructive photographic editing.
What changes when converting Xfig to ORF?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to ORF removes vector scaling.
What should I review after converting Xfig to ORF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.