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
PFM Raw at a glance
PFM Raw
PFM persists from the era when HDR imaging, rendering research, and tone-mapping workflows needed straightforward file carriers for floating-point image data long before mainstream consumer HDR delivery formats matured.
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.
Format comparison
| Feature | PFM Raw | BAY |
|---|---|---|
| File type | Image | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1998 | 2002 |
| Inventor | PBRT / Paul Debevec community | Casio |
| Status | active | 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 | Not supported | Supported |
| HDR support | Supported | Not supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use PFM Raw
- Your source file is already in PFM Raw.
- Preserve source expectations before exporting to BAY.
- PFM Raw is commonly used in image workflows.
When to use BAY
- Your target workflow expects BAY.
- Improve delivery compatibility with BAY.
- BAY is commonly used in image workflows.
FAQs
Why convert PFM Raw to BAY?
Convert to BAY when preserving compatibility with an older camera archive or recovering original raw captures from that ecosystem.
In most modern photo workflows, BAY is a source to normalize into DNG, TIFF, or a contemporary editing format.
What changes when converting PFM Raw to BAY?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to BAY adds camera raw data. Moving to BAY removes HDR content.
What should I review after converting PFM Raw to BAY?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.