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.
KRA at a glance
KRA
Krita's native format reflects the rise of open-source digital painting as a serious creative workflow rather than only a hobbyist alternative.
Format comparison
| Feature | Xfig | KRA |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1985 | 2005 |
| Inventor | Supoj Sutanthavibul | Krita / KDE community |
| Status | legacy | proprietary |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | 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 KRA.
- Xfig is commonly used in vector workflows.
When to use KRA
- Your target workflow expects KRA.
- Improve delivery compatibility with KRA.
- KRA is commonly used in image workflows.
FAQs
Why convert Xfig to KRA?
Convert to KRA when the artwork needs to remain editable in Krita, especially for painting-heavy or layered illustration workflows.
It is the right target for preserving native editability during digital-art production.
What changes when converting Xfig to KRA?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to KRA adds layer support. Moving to KRA removes vector scaling.
What should I review after converting Xfig to KRA?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.