ORF to TIFF Converter

Convert ORF to TIFF: What This Page Covers

This is the Olympus and OM SYSTEM raw handoff — developing a .orf into a flat, print-ready TIFF for layout, prepress, or archival. There is a neat piece of lineage underneath it: ORF is a TIFF-structured container (with its own magic bytes, MMOR, IIRO or IIRS, in place of the standard TIFF signature), so this conversion develops a TIFF-family raw into an ordinary rendered TIFF. What follows is the one setting that quietly decides whether your TIFF is lossless, the two compression choices you must never pick, and why the quality slider does nothing most of the time.

How to Convert ORF to TIFF

1. Upload Your ORF File: Drag and drop your Olympus .orf onto the page or click "+ Add Files" to browse. Several raw frames can be queued and converted with the same settings.
2. Change the Compression Type: Open Advanced Options and set "Compression Type". It opens on JPEG, which is lossy — switch it to LZW, Deflate, PackBits or None for a mathematically lossless TIFF. Skip CCITT Fax 4 and JP2K entirely.
3. Set Extension, Resolution and Quality Preset: Pick .tiff or .tif under "File extension" to match your software (neither is preselected), use "Image resolution" only if you want to scale down from the native frame, and leave "Quality Preset" alone unless you deliberately chose JPEG compression.
4. Convert and Download: Click Convert and save the TIFF. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.

Compression Types on This Page

The Two Choices That Silently Produce a Broken File

CCITT Fax 4 and JP2K both appear in the dropdown, and both fail on photographic content — but they fail quietly. The encoder rejects the data (Bits/sample must be 1 for Group 3/4 encoding/decoding for CCITT Fax 4, Compression scheme 33004 scanline encoding is not implemented for JP2K) and leaves behind a header-only stub of roughly 250 bytes with no pixel data in it. We measured both: the resulting files open as an empty image with every pixel reading zero. If your "converted" TIFF is a few hundred bytes and displays as black or blank, this is why — re-run with LZW.

Why the Quality Preset Usually Does Nothing

"Quality Preset" is the shared image-quality dropdown, and on a TIFF it only reaches the encoder when the compression scheme is a lossy one. We tested this directly: writing the same source at quality 10, 50 and 95 with LZW compression produced three byte-identical files with the same MD5 hash. With JPEG compression the same three settings produced wildly different files — on our test image, roughly 7 KB, 23 KB and 380 KB.

• Chose LZW, Deflate, ZSTD, PackBits or None? The preset is inert. Ignore it.
• Chose JPEG (or LOSSY)? The preset is now the only thing controlling fidelity, and "Very High (Recommended)" is the selected entry.
• Want a smaller file without lossy compression? Use "Image resolution" to scale down instead — fewer pixels shrinks a lossless TIFF honestly.

There is no bit-depth control on this page, and this is the one limitation worth knowing before you build a workflow around it: the render normalises to 8-bit sRGB, so although a TIFF can hold 16-bit channels, the file written here carries 8 bits per channel. We confirmed it by pushing a 16-bit source through the same call the converter makes — the output came back 8-bit sRGB regardless of which compression scheme was selected. That is exactly what print, layout and delivery workflows expect. It is not what you want as a high-bit editing master: for 16-bit output, or for a working space such as Adobe RGB or ProPhoto, export from a raw editor instead.

ORF and TIFF at a Glance

Common Mistakes and How to Fix Them

• "My lossless TIFF still lost quality." The Compression Type was left on JPEG. Re-run with LZW, Deflate, ZSTD, PackBits or None.
• "The output is a few hundred bytes and shows nothing." CCITT Fax 4 or JP2K was selected. Neither can encode a colour photo; the writer errors out and leaves a stub. Use LZW.
• "The TIFF is far bigger than the ORF." Expected. The raw stores one value per photosite; the TIFF stores three colour planes for every pixel. Even with LZW a 20-megapixel frame lands in the tens of megabytes, and None is larger still.
• "My PackBits file is bigger than the uncompressed one." Also expected on photographic data — run-length encoding expands when neighbouring pixels rarely repeat. We measured PackBits coming out slightly larger than NONE on a noisy test image. Use LZW or Deflate instead.
• "Colours don't match my camera JPEG." The raw is developed on our servers with a neutral default rendering. Olympus Art Filters and Picture Modes are in-camera rendering instructions that third-party developers do not reproduce exactly. Apply your look in a raw editor and export from there if colour fidelity is critical.

Frequently Asked Questions

Does converting ORF to TIFF lose image quality?

That depends entirely on the Compression Type. LZW, Deflate, ZSTD, PackBits and None discard nothing — every rendered pixel survives the encode. The catch is that the dropdown opens on JPEG, which is lossy, so for an archival file you must change it. Separately, the render itself resolves the raw mosaic into fixed 8-bit sRGB pixels using a default white balance and tone curve. That interpretation is what you can no longer freely undo, and the raw's extra bit depth is resolved away with it — so "lossless compression" here means the encode discards nothing, not that the TIFF is a bit-for-bit carrier of everything the sensor recorded.

ORF is based on TIFF — doesn't that make this a lossless copy?

No, and this is the most common misunderstanding about the pair. ORF borrows TIFF's tagged file structure (with different magic bytes at the start), but structural kinship is not pixel kinship: the ORF holds an undeveloped Bayer mosaic, and the converter must demosaic and develop it into ordinary RGB before anything can be written. Whether that result is stored losslessly is decided by your compression choice, not by the shared heritage.

Which compression should I pick for a long-term archive?

LZW if you want the broadest guarantee that any tool will open it in ten years, Deflate if you want lossless with a modestly smaller file, ZSTD if your whole toolchain is current and you want the smallest lossless result. All three are mathematically lossless. Avoid None unless storage genuinely does not matter, avoid PackBits for photographs, and never use JPEG for an archive master.

Why is my TIFF so much larger than the original ORF file?

An ORF packs a single brightness value per photosite; a rendered TIFF carries a full red, green and blue value for every pixel. That is roughly a threefold expansion before compression, and lossless compression barely dents photographic noise. A 20-megapixel Micro Four Thirds frame therefore lands in the tens of megabytes even with LZW. If size matters more than edit headroom, export ORF to JPG instead.

What is the difference between the .tiff and .tif output?

Only the filename. Both are the identical Tagged Image File Format; the three-letter .tif survives from the era of eight-dot-three filenames on Windows. This page lets you pick either under "File extension", and neither is preselected — choose whichever your downstream software expects. The bytes written are the same.

Can I open the resulting TIFF on a web page or share it in a browser?

Not reliably. TIFF is a professional and archival format, not a web one: Safari renders TIFFs, but Chrome and Firefox generally do not, and most social and messaging platforms reject the format outright. For something that displays everywhere, render ORF to JPG, or ORF to AVIF for a much smaller modern web copy.

Should I keep the original ORF after converting?

Yes — always. Even a lossless TIFF is not a substitute for the raw. The white balance, exposure, tone curve and any in-camera Picture Mode are fixed once the frame is rendered, and the recoverable highlight and shadow headroom of the digital negative is gone with them. Treat the TIFF as a high-quality working, print or delivery copy, and archive the .orf separately.

My camera also wrote an .ori file — should I convert that instead?

Usually not. On Olympus and OM SYSTEM bodies, a High Res Shot writes the pixel-shifted composite as the .orf and additionally saves the first single frame of the shift sequence as a separate .ori. Convert the .orf when you want the full-resolution composite. The .ori is a normal-resolution frame of the same scene, and it is worth keeping because it gives you a clean version of any area the composite smeared through subject movement.

How are my uploads handled and how long are they kept?

Your ORF is uploaded over an encrypted connection, developed into a TIFF on our servers, and deleted automatically after a few hours — never shared, never made public. There is no sign-up and no watermark. Because Olympus raws routinely run tens of megabytes each and TIFF output is larger still, the practical limit on a big batch is upload size and connection speed rather than the conversion itself.