Initializing... drag & drop files here
Supports: ORF
ORF is Olympus Raw Format — the undeveloped sensor file an Olympus or OM System camera writes. It is a TIFF-structured container that swaps the normal TIFF signature for MMOR, IIRO, or IIRS, which is exactly why generic photo viewers refuse to open it. HEIC is the opposite kind of file: a finished, HEVC-coded picture inside an HEIF container, designed to be small and to be looked at rather than edited. Converting ORF to HEIC is therefore a one-way render, not a repackage. The short answer to the question in the heading: choose HEIC when your photos live on Apple devices and storage is the constraint, and choose JPEG when anyone outside that ecosystem has to open the file. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.
| Property | ORF (Olympus Raw Format) | HEIC |
|---|---|---|
| What it is | Undeveloped Bayer sensor data — a digital negative | Finished, compressed delivery photo |
| Container | TIFF-structured, custom signature MMOR / IIRO / IIRS |
HEIF (ISO/IEC 23008-12) carrying HEVC-coded image data |
| Origin | Olympus; the imaging business became OM Digital Solutions on 1 January 2021 and now ships as OM System | ISO/MPEG standard; Apple made it the default iPhone camera format in iOS 11 |
| Bit depth | 12 bits per channel on current bodies — DPReview lists the OM System OM-1 as 12-bit lossless-compressed | 8 bits per channel as this page encodes it |
| Compression | None or lossless | Lossy HEVC |
| Editing latitude | Full — white balance, exposure and highlight recovery are still open | None — the render is baked in |
| Typical size, 20 MP frame | Tens of megabytes | A small fraction of the raw |
| Native browser support | None | Safari 17 and later only; Chrome, Firefox and Edge do not decode HEIC (caniuse puts global support near 15%) |
| Best for | Archiving the negative, re-editing later | Small files inside Apple's ecosystem |
.orf as your master, so the HEIC never has to serve as an archive.<img src="photo.heic"> simply fails for most visitors..orf files onto the page or click "+ Add Files". Olympus raws routinely run tens of megabytes each, so the upload is the slow part, not the encode; queue several and they all convert with the same settings..heic. No sign-up, no watermark.This page deliberately shows a small option surface, and it is worth knowing what is absent. There is no bit-depth selector, no lossless toggle, no compression-level or encoder-effort control — those belong to other output formats and do not render for a HEIC target. The encoder is driven with a quality factor and nothing else.
| Control | On this page | What it does here |
|---|---|---|
| Quality Preset | Renders, Very High selected | Seven rungs from Highest to Lowest; the main quality lever |
| Specific file size | Renders, with Auto Scale | Names a target in bytes, kilobytes, or megabytes |
| Image resolution | Renders, "Keep original" selected | Percentage, preset height, width, height, or exact width x height |
| Target file size (%) | Hidden | Suppressed for image conversion targets |
| Image Quality (%) | Hidden | The Quality Preset covers this instead |
| Colors / palette reduction | Hidden | A PNG and GIF control, not a HEIC one |
| Compression level, Compression speed | Hidden | PNG-only controls |
| Lossless toggle, bit depth | Not present at all | The encoder runs at its default 8 bits per channel |
That has one consequence people get wrong: the HEIC you get is 8 bits per channel. The HEIF specification allows more, and Apple's own camera pipeline writes 10-bit HDR files, but this converter does not request a higher depth. We checked the encoder path directly — feeding a 16-bit-per-channel source through the same quality-only save produces an 8-bit HEIC. So a 12-bit Olympus raw is narrowed twice on the way out: once to 8 bits, and again by the lossy HEVC encode. Treat the result as a delivery file and keep the .orf.
No. The HEIF container can hold more than 8 bits per sample, but this page's encoder is driven with a quality factor and no bit-depth argument, so the output lands at 8 bits per channel — the same depth as a JPEG. If the wider tonal range matters, keep the .orf or render a 16-bit-capable TIFF instead of a HEIC.
Because native HEIC decoding is essentially an Apple feature. caniuse shows Safari 17 and later as the only major browser with support; Chrome, Firefox, and Edge have none. Windows can open HEIC once Microsoft's HEIF Image Extensions and HEVC Video Extensions are installed, which many managed machines do not have, and Android support varies by device and gallery app. If in doubt, send JPEG.
Roughly, at comparable visual quality — that is the practical reason the format exists, and it comes from using HEVC intra-frame coding in place of JPEG's much older DCT scheme. The exact ratio depends entirely on the picture and the Quality Preset you choose, so treat "about half" as a rule of thumb rather than a guarantee, and compare the two outputs if the number matters.
Not exactly. Your camera applies its own colour science, sharpening, tone curve, and any Art Filter you had set when it writes an in-camera JPEG. Any third-party raw converter, including this one, develops the sensor data with its own neutral defaults instead. Expect a clean but different-looking starting point; if you need the camera look, shoot JPEG alongside raw or develop the ORF in OM Workspace first.
Yes — queue them together and they convert with one shared Quality Preset and resolution setting. The realistic constraint is upload size and time rather than the conversion itself, because Olympus raws are large; on a slow connection, smaller batches finish more predictably. For a hub covering every ORF target in one place, see the ORF converter.
They are the same underlying container. HEIF (ISO/IEC 23008-12) is the format; .heic is the conventional extension for HEIF files whose image data is HEVC-coded, which is what Apple writes and what this page produces. If a particular application insists on the other spelling, ORF to HEIF writes the same kind of file under the .heif name.
Metadata handling depends on the encoder path rather than on anything you can toggle here, so do not rely on a HEIC render as a metadata archive. If the shooting data matters to you, keep the original .orf: the raw file is the only copy guaranteed to hold the full Olympus MakerNote block along with the standard EXIF fields.
Your file is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours. There is no account to create, nothing is watermarked, and your photos are never shared or made public.