Olympus ORF MIME Type

What does image/x-olympus-orf mean?

image/x-olympus-orf identifies an Olympus Raw Format photograph. The usual extension is .orf. Olympus and its successor camera brand, OM System, use ORF to preserve sensor data and capture settings for development after the photograph is taken. An editor can then choose white balance, exposure, color rendering, noise reduction, and sharpening instead of being limited to the camera's finished image.¹

The media type is a widely used convention, not an IANA registration. IANA's current image registry has no entry for image/x-olympus-orf, while libopenraw documents that identifier for ORF files.²³ The historical x- prefix signals an unregistered subtype.

How to identify an ORF file

ORF is based on the directory structure used by TIFF and TIFF/EP, but it replaces the ordinary TIFF identifier with an Olympus-specific four-byte value. Depending on the generation and byte order, an ORF can start with one of these signatures:³

4D 4D 4F 52    MMOR
49 49 52 4F    IIRO
49 49 52 53    IIRS

The file can contain raw sensor samples, image-file directories, capture metadata, Olympus MakerNotes, and one or more JPEG previews. Some applications show the embedded preview immediately, while a raw processor interprets the sensor data and camera profile to make a new rendering. Those two pictures can differ in crop, brightness, white balance, color, and sharpening.

A signature and extension are only the start of validation. Software must still check directory offsets, lengths, image dimensions, and model-specific data before trusting a file. Renaming a TIFF, JPEG, or DNG file to .orf does not create an Olympus raw photo.

When did Olympus introduce ORF?

ORF dates to Olympus's early professional digital-camera era. The CAMEDIA E-10, released in 2000, offered raw recording, and libopenraw documents E-10-specific organization within the ORF family.³⁴ Olympus continued the format through Four Thirds and Micro Four Thirds cameras. Current OM System cameras still record raw photographs as ORF.⁵

The format has evolved while retaining its familiar extension. That continuity is convenient for photographers, but it means an older decoder may open one ORF and reject a newer camera's file. Adobe therefore publishes ORF compatibility by camera model and minimum Camera Raw or Lightroom version.⁶

What is an .ori file?

.ori is a related raw file created by some Olympus and OM System high-resolution shooting modes. In the PEN-F workflow, for example, the camera saves a pre-combination raw exposure as .ori before merging multiple sensor-shift captures into the High Res Shot.⁷

An ORI should not be treated as a generic alternate filename for every ORF. Its role depends on the camera and capture mode. Current Adobe compatibility tables list ORF and ORI separately for models that produce both, which is a good reminder to verify model-specific application support.⁶

How to open an ORF or ORI file

Use a raw editor that supports the exact camera:

• OM Workspace is the first-party Olympus and OM System application for viewing, editing, and converting supported raw photographs.⁸
• Adobe Camera Raw, Photoshop, and Lightroom support a long list of Olympus and OM System cameras. Adobe's table gives the minimum version for each model and includes ORI where supported.⁶
• Apple Photos and Preview-based workflows can use the operating system's raw decoder for camera models listed by Apple.⁹

Chrome, Edge, Firefox, Opera, and Safari do not natively develop ORF files as web images. ORF is absent from MDN's list of browser image formats.¹⁰ A website should display a rendered JPEG, WebP, AVIF, or PNG, with the ORF offered separately when visitors need the raw original.

Support in Poly

Poly recognizes .orf and .ori photos and makes them easy to work with:

• Browse them with thumbnails and an in-app image preview.
• Find them by filename, available camera metadata, color, and visual similarity.
• Let the Poly agent inspect and reason about the visible photograph.

The preview represents the camera-rendered image stored with the raw capture. Poly does not develop the sensor mosaic, so exposure recovery, demosaicing, lens correction, and precise color work still belong in a dedicated raw editor. Preview resolution and appearance depend on the usable image stored by the camera. Words photographed in an ORF are not searchable as text.

Converting ORF to DNG, TIFF, or JPEG

Choose the output for the next stage of the workflow:

Adobe DNG Converter can translate supported camera-specific raw files into DNG. Adobe notes that proprietary metadata can be omitted unless the original raw file is embedded in the DNG.¹¹ Keeping the untouched ORF or ORI alongside a converted copy is the cautious archival choice.

Exporting to TIFF, JPEG, or PNG is different from raw-to-raw conversion. The editor must interpret the sensor samples using a camera profile, white balance, tone curve, and other development settings. The resulting pixels are convenient to view and share, but they cannot recreate the original measurements.

Metadata and privacy

ORF files can carry detailed Exif and maker-specific metadata. Exif fields can include capture date and time, location, camera and lens names, owner or photographer information, and software history.¹² A derivative may copy some of those fields, while a DNG can retain or embed much more.

Review metadata before sharing an original raw file. For public delivery, a fresh JPEG export with an explicit metadata policy is usually easier to inspect than an ORF containing raw data, previews, and proprietary tags.

Is ORF the same as JPEG or DNG?

No. They serve different purposes.

An ORF may contain an embedded JPEG preview, but that preview is only one component. Extracting it gives you the camera's quick rendering, not a complete development of the raw sensor data.