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
DCM at a glance
DCM
DICOM grew out of the need to exchange imaging data across scanners, archives, and clinical systems without throwing away the surrounding context that makes a medical image usable in practice.
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.
Format comparison
| Feature | DCM | Xfig |
|---|---|---|
| File type | Image | Vector |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | depends | scalable |
| File size characteristics | medium | small |
| Compatibility | broad | moderate |
| Editability | moderate | high |
| Created year | 1993 | 1985 |
| Inventor | ACR-NEMA / DICOM Standards Committee | Supoj Sutanthavibul |
| Status | active | legacy |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | moderate | good |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | delivery | design |
| Layer support | Not supported | Not supported |
| Vector scaling | Not supported | Supported |
When to use each format
When to use DCM
- capture ingest
- editing
- web or print delivery
- Carries workflow-critical metadata alongside image content.
When to use Xfig
- illustration
- diagramming
- brand asset delivery
- Preserves object-level editability for technical diagrams.
FAQs
Why convert DCM to Xfig?
Choose Xfig as target when technical diagrams and figures in Unix academic workflows, legacy Xfig drawing migration, and scientific publication figure production on Unix.
What changes when converting DCM to Xfig?
Technical diagrams and figures in Unix academic workflows, legacy Xfig drawing migration, and scientific publication figure production on Unix.
What should I review after converting DCM to Xfig?
After conversion, review these destination checks: Open converted output in xfig and verify behavior on real samples; Compare output against the expected scalable quality profile; Closely tied to the Xfig ecosystem and long-tail compatibility workflows.
How can I keep quality stable in DCM to Xfig conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Not a mainstream modern illustration exchange format; Closely tied to the Xfig ecosystem and long-tail compatibility workflows; Validate destination compatibility before large-batch conversion.