Initializing... drag & drop files here
Supports: MRW
MRW is Minolta RAW, the unprocessed sensor data from DiMAGE and Dynax/Maxxum cameras. The brand is gone — Konica Minolta left the camera business in 2006 — so no new MRW files are being made and the ones you have are orphaned archives. AVIF is a current, AV1-based still image that stays small and opens in today's browsers. The honest move is not to replace your MRW but to render a modern, viewable copy while software can still read the old format, and keep the original as your master. The table below lays out what you gain and what you give up.
| Property | MRW (source) | AVIF (output) |
|---|---|---|
| Full name | Minolta Raw | AV1 Image File Format |
| Type | Camera raw — sensor data, not a finished picture | Finished, displayable image |
| Origin | Minolta, later Konica Minolta; DiMAGE 7 (2001) | Alliance for Open Media; spec v1.0.0, Feb 19, 2019 |
| Codec / container | Proprietary; ~12-bit Bayer CCD readout | AV1-coded image in a HEIF container |
| Compression | Effectively lossless raw — large files | Lossy or lossless; typically far smaller than JPEG |
| Editing latitude | Wide — white balance, exposure, highlights recoverable until rendered | None left — render is baked in |
| Opens in a browser | No | Yes — about 93% of browsers (Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+) |
| Brand status | Orphaned; no new files, decoder support shrinking | Actively developed and adopted (Google, Apple, Mozilla, Microsoft) |
| Best treated as | Irreplaceable master — keep it | Working copy for viewing and sharing |
.mrw file onto the page or click "+ Add Files" to browse. You can queue several frames from a DiMAGE or Dynax/Maxxum body at once.AVIF is the efficient modern answer, but it is not the only sensible destination for a file you may be preserving for decades. The right pick depends on whether you are optimizing for file size, for guaranteed openability, or for a lossless archival copy of the render.
| Target | Compression | Bit depth | Transparency | Opens on old software | Best for |
|---|---|---|---|---|---|
| AVIF (this page) | Lossy (very efficient) or lossless | 8, 10, 12-bit | Yes | No — needs a recent browser or viewer | Small, high-quality web and gallery copies |
| JPG | Lossy | 8-bit | No | Yes, essentially everywhere | The universal copy, print shops, sharing with anyone |
| PNG | Lossless | 8 or 16-bit | Yes | Yes | Lossless render with transparency, screenshots of the frame |
| TIFF | Lossless (or uncompressed) | 8 or 16-bit | Optional | Yes, in editors and print workflows | Archival master of the render, further editing |
| WEBP | Lossy or lossless | 8-bit | Yes | Broad, but narrower than JPG | Web images where AVIF support is uncertain |
A common, sane pattern for an orphaned format: keep the .mrw as the untouchable master, make one lossless TIFF or PNG of your preferred render, and generate AVIF or JPG copies from that whenever you need to share something. That way you never have to re-open the MRW again.
For viewing and sharing, yes — with one rule. AVIF gives you a small, high-quality, modern file that opens in current browsers, which is exactly what an orphaned MRW lacks. The catch is that converting renders the raw permanently, so treat AVIF as a working copy and keep the original .mrw as your master. If you need the photo to open in older or unusual software too, JPG is the safer universal copy and AVIF the efficient modern one — many people keep both.
Yes, and this is the one thing to understand before converting. An MRW stores unprocessed ~12-bit CCD sensor data, which is why you can still recover blown highlights, lift shadows, and reset white balance long after the shot. To make an AVIF, the converter has to demosaic that data into ordinary pixels and bake in the current white balance, exposure, and tone. Once it is an AVIF, that latitude is gone — exactly as it would be in a JPEG. The original MRW is irreplaceable because no new ones are being made, so keep it as your editable master and treat the AVIF as a copy.
Because the brand that made it no longer exists. Konica Minolta announced on January 19, 2006 that it was leaving the camera business, withdrawing by that March 31 and transferring its digital-SLR assets to Sony — whose Alpha line and ARW raw format descend from that Minolta technology. No camera has written a new MRW since. Development stopped, so some current photo software has quietly dropped the old Minolta decoder. That is the real reason to convert: render a viewable copy now, while a working decoder still reads your files, rather than discover years from now that nothing opens them.
Usually close, not always identical. The AVIF is built from a fresh render of the raw, and a server-side raw decoder will not always interpret white balance and tone exactly the way Minolta's original in-camera processing or a specific desktop raw editor did. If precise color matters, open the MRW in a raw editor that reads Minolta files, set white balance and exposure there, export a rendered image, and convert that — the conversion will faithfully carry whatever render you feed it.
It depends on what you value. AVIF generally produces a noticeably smaller file than JPEG at the same visual quality and supports higher bit depth and HDR, which suits a space-conscious web gallery or archive. The trade-off is reach: AVIF is supported in roughly 93% of browsers (Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+), so a few older or niche environments cannot open it, whereas a MRW to JPG copy opens everywhere. Pick AVIF for efficiency on modern targets; pick JPG when universal compatibility wins.
MRW came out of Minolta's prosumer and DSLR lines in the early 2000s. The DiMAGE 5 and DiMAGE 7 series introduced it, the DiMAGE A1, A2, and A200 continued it, and it carried through to the Konica Minolta Dynax/Maxxum 7D (2004) and 5D (2005) digital SLRs — the last cameras to write the format before the brand exited. The Dynax and Maxxum names refer to the same bodies sold in different regions. If your files came off any of those, this page reads them directly; if they came off a later Sony Alpha, they are .arw instead, which descends from the same lineage.
Partly, and you should not rely on it for anything important. AVIF sits in a HEIF container that has proper boxes for Exif and XMP, so ordinary capture metadata like date, exposure, and camera model has somewhere to go. What does not survive reliably is anything vendor-specific: Minolta's proprietary MakerNote fields have no equivalent in a rendered image and are typically dropped, as are the raw-processing parameters that only mean something inside the MRW. If the shot's provenance matters — for a family archive or any kind of record — keep the original .mrw, which holds all of it, and treat the AVIF strictly as a viewing copy.
Your MRW is uploaded over an encrypted connection, rendered and encoded to AVIF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. In our testing, a full-resolution MRW from a DiMAGE or Dynax body rendered at the "Very High" preset produced an AVIF a small fraction of the original raw's size, since AVIF compresses photographic detail far more efficiently than the uncompressed sensor data in an MRW. The main practical limit is upload size and time, since MRW files often run to several megabytes each, not your device.