MRW to TIFF Converter

Convert MRW to TIFF: What This Guide Covers

MRW is Minolta's raw format — the undeveloped sensor readout from DiMAGE bridge cameras and the Dynax/Maxxum digital SLRs. Konica Minolta announced on 19 January 2006 that it was leaving the camera business and began transferring its SLR operations to Sony on 31 March 2006, so no camera has written a new MRW file since, and support for reading them has been quietly draining out of consumer photo software ever since. This guide is for people holding an orphaned MRW archive who want a flat, viewable, genuinely lossless TIFF preservation copy, and most of its length goes to a single dropdown — because the setting this page opens with is the wrong one for archival work.

How to Convert MRW to TIFF

1. Upload Your MRW File: Drag your .mrw files onto the page or click "Add Files" to browse. You can queue a batch of frames from a DiMAGE or Dynax/Maxxum body in one go.
2. Change Compression Type from JPEG to LZW: Open the options and find the "Compression Type" group. It is set to JPEG, which is lossy — switch it to LZW (or Deflate, PackBits, ZSTD or None) before you convert anything you care about.
3. Set Image Resolution and File Extension (Optional): "Image resolution" starts on "Keep original", which is what you want for a master; the same group also offers Resolution Percentage, Preset Resolutions and Width x Height if you need a smaller derivative. The "File extension" group switches the output name between .tiff and .tif.
4. Convert and Download: Click Convert and download the TIFF. Files upload over an encrypted connection, are processed on our servers and are deleted automatically after a few hours. No sign-up, no watermark.

Walk-through: The Compression Type Dropdown

Everything about whether this conversion is archival or not lives in one control. TIFF is a container that can hold pixels compressed several different ways, and our TIFF writer passes your choice straight through to the encoder — including the fallback, which is JPEG. That is a reasonable default for someone making a quick preview and a bad one for someone rescuing a raw archive, so it is worth two seconds of attention.

Two interactions are worth knowing. First, the "Quality Preset" dropdown ("Very High (Recommended)" and six other steps) becomes a JPEG quality factor — our writer converts "Very High" to Q95 — and a quality factor only means something when the compression is lossy. Pick LZW and the preset has nothing to act on. Second, "Specific file size" works by searching for a quality value that lands on your target; with a lossless compression selected there is no quality to search, so the only lever left is the Auto Scale checkbox shrinking the pixel dimensions. If you are producing an archival master, leave both alone.

What the Raw Development Step Actually Does

A TIFF is not a repackaged MRW, and this is the part people underestimate. The MRW holds one brightness value per photosite sitting behind a colour filter array — no full-colour pixels exist in the file yet. Producing a TIFF means demosaicing that mosaic into three channels per pixel, applying a white balance, and running a tone curve to get from linear sensor readings to something that looks right on a screen. Those decisions get baked into the output permanently.

That is why a lossless TIFF is still not a raw file. The compression is lossless in the sense that the TIFF encoder discards nothing you hand it; the interpretation that produced those pixels is what you can no longer freely revisit. It is also why the TIFF is dramatically larger than the MRW despite starting from the same photograph: one value per photosite becomes three full channels per pixel. Note that our server-side decoder makes its own development choices and will not reproduce Minolta's in-camera processing exactly. It is not doing any HDR tone-mapping — just a standard raw development.

MRW and TIFF Side by Side

Common Errors and How to Fix Them

• "My archival TIFF came out suspiciously small and looks soft at 100%" — Compression Type was still JPEG (or LOSSY, which is the same thing). Re-convert with LZW.
• "The TIFF is many times bigger than the MRW" — Expected, and not a fault. Three RGB channels per pixel is simply more data than one filtered value per photosite, and lossless compression cannot close that gap.
• "CCITT Fax 4 or JP2K failed" — Both expect input those coders can handle; Group 4 in particular is bilevel-only. Neither is appropriate for a colour photograph. Use LZW.
• "My MRW no longer opens in current photo software" — Some applications have dropped the legacy Minolta decoder. That is exactly the reason to render TIFFs now, while a decoder that reads your files still exists somewhere.
• "The TIFF will not display in my browser or upload to a website" — TIFF is a print and archival format. Export a MRW to JPG copy for anything web-facing, or MRW to AVIF if you want a modern, efficient one.
• "Colours and exposure look different from what I remember" — The render applies its own white balance and tone curve. If a specific look matters, develop the raw in a desktop editor first and archive that export.

When This Doesn't Work

This path expects a genuine Minolta .mrw. A truncated file from a failed card copy, or some other raw format renamed to .mrw, will either fail to decode or come out flat — re-copy the original from the camera or card if you still can. This page also exposes no bit-depth control and no DPI control, so if your workflow specifically requires a 16-bit TIFF or an embedded ICC profile and print resolution, do that development in a desktop raw editor that reads Minolta files and export the TIFF from there. Whatever you do, keep the .mrw. It is the only copy that still holds the recoverable highlight, shadow and white-balance latitude, and nothing will ever produce another one.

Frequently Asked Questions

Will my MRW to TIFF conversion actually be lossless?

Only if you change one setting. The "Compression Type" control on this page starts on JPEG, and JPEG inside a TIFF wrapper is still lossy DCT compression — the container being TIFF does not make it archival. Switch it to LZW, Deflate, PackBits, ZSTD or None and the TIFF encoder writes back exactly the pixels it was handed. That is the encode side. The development side — turning the sensor mosaic into RGB — is a one-way interpretation regardless of which compression you pick, which is the reason you keep the MRW as well.

Why is JPEG the default compression for a TIFF?

It is the fallback in our TIFF writer, and it optimises for file size rather than fidelity, which suits the common case of someone making a shareable copy. It is genuinely the wrong default for a raw archival user, so we would rather say so plainly than let you discover it later. There is also a second entry in that list labelled LOSSY that maps to the identical JPEG encoder value, so choosing it changes nothing — treat LZW as your starting point on this page and ignore both.

Which lossless compression should I pick — LZW or Deflate?

LZW if you care about compatibility, Deflate if you care about size. LZW is the lossless TIFF compression that essentially every imaging tool and print RIP has read for decades. Deflate is the zlib/ZIP algorithm and usually squeezes photographic detail a bit harder, at the cost of being less universally understood by very old software. PackBits is a simple run-length scheme that ancient applications can open but that barely compresses photographs; ZSTD is fast and efficient but recent enough that older readers will not recognise it; None writes uncompressed pixel bytes and is the most defensively simple option of all.

Does the Quality Preset do anything when I choose LZW?

No, and that is expected rather than a fault. That dropdown is a quality factor — our writer turns "Very High (Recommended)" into Q95 — and a quality factor is only meaningful to a lossy encoder. With LZW, Deflate, PackBits, ZSTD or None selected there is nothing for it to trade away, so the output is the same whichever preset is showing. It does matter if you deliberately choose JPEG or WebP compression.

Can I get a 16-bit TIFF or set the DPI here?

Not on this path. This page renders a standard TIFF and exposes no bit-depth selector and no DPI field — the visible controls are Compression Type, Quality Preset, Specific file size, Image resolution and the .tiff/.tif extension. If your requirement is specifically 16 bits per channel or a particular print resolution tagged into the header, develop the MRW in a desktop raw application and export from there. For a viewable, lossless, correctly-sized copy of an orphaned archive, what this page produces is sufficient.

Does the TIFF keep my Minolta EXIF data?

Treat it as unreliable and do not build a workflow on it. TIFF can carry EXIF, but raw metadata written by a discontinued camera line passes through a decoder that was reverse-engineered rather than documented, and maker-note blocks in particular are the first thing to get dropped. If capture dates and camera settings matter to your archive, read them off the original MRW with an EXIF tool and record them alongside — and keep the MRW, which is the authoritative copy of that metadata.

Is there any difference between the .tiff and .tif output?

None in the bytes. .tif is a three-letter holdover from the old eight-character filename limit and .tiff is the same Tagged Image File Format; the "File extension" group simply names the output to match whatever your software expects. Pick whichever your cataloguing or print workflow wants and the file itself is identical either way.

How are my files handled while they convert?

Your MRW is uploaded to our servers over an encrypted connection, decoded and written out as a TIFF there, and deleted automatically after a few hours. There is no sign-up, no watermark, and your photographs are never shared or made public. The practical constraint on a large batch is upload size and time rather than anything on the conversion side, so if you are digitising a whole archive it is usually faster to work in modest batches. And keep the originals: the TIFF is a copy, not a replacement.