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
WMF at a glance
WMF
The original WMF specification was published in the Windows 3.1 SDK documentation in 1992. Aldus Corporation independently added a 'placeable' header for device independence, which Microsoft later incorporated in Windows 2000. The format specification was republished in 2006 under the Microsoft Open Specification Promise.
SRF at a glance
SRF
Before ARW became the better-known Sony raw family, Sony's raw ecosystem already included older variants that modern tools still need to decode correctly.
Format comparison
| Feature | WMF | SRF |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1990 | 2003 |
| Inventor | Microsoft Corporation | Sony |
| 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 WMF
- Your source file is already in WMF.
- Preserve source expectations before exporting to SRF.
- WMF is commonly used in vector workflows.
When to use SRF
- Your target workflow expects SRF.
- Improve delivery compatibility with SRF.
- SRF is commonly used in image workflows.
FAQs
Why convert WMF to SRF?
Convert to SRF when preserving older Sony originals or keeping a legacy Sony raw library intact.
It is useful for archive recovery and compatibility workflows.
What changes when converting WMF to SRF?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to SRF removes vector scaling.
What should I review after converting WMF to SRF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.