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
BAY at a glance
BAY
Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
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 | BAY | SRF |
|---|---|---|
| File type | Image | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2002 | 2003 |
| Inventor | Casio | Sony |
| Status | proprietary | proprietary |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Vector scaling | Not supported | Not supported |
| Camera raw data | Supported | Supported |
| HDR support | Not supported | Not supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use BAY
- Your source file is already in BAY.
- Preserve source expectations before exporting to SRF.
- BAY is commonly used in image 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 BAY 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 BAY to SRF?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting BAY to SRF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.