Convert anything, at global scale.
200+ formats and automation APIs that feels instant.
CONVERT
From
To
MD at a glance
MD
Markdown was created in 2004 by John Gruber with Aaron Swartz, but the later CommonMark effort became important because the original syntax description was too ambiguous to keep implementations aligned.
X3F at a glance
X3F
Sigma raw support is closely tied to the company's Foveon sensor story, giving X3F a reputation and workflow profile that differ from more mainstream Bayer-centric raw ecosystems.
Format comparison
| Feature | MD | X3F |
|---|---|---|
| File type | Document | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2004 | 2002 |
| Inventor | John Gruber and Aaron Swartz | Sigma (Foveon) |
| Status | active | proprietary |
| Primary use cases |
|
|
| Vector scaling | Not supported | Not supported |
When to use each format
When to use MD
- Your source file is already in MD.
- Preserve source expectations before exporting to X3F.
- MD is commonly used in document workflows.
When to use X3F
- Your target workflow expects X3F.
- Improve delivery compatibility with X3F.
- X3F is commonly used in image workflows.
FAQs
Why convert MD to X3F?
Convert to X3F when preserving Sigma camera originals or maintaining a workflow built around Foveon raw processing.
It is useful for archival retention and non-destructive editing of Sigma captures.
What changes when converting MD to X3F?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting MD to X3F?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.