Skip to content

PSD to ORF Converter

Convert PSD to ORF in your browser. You download a Linear DNG (.dng), not a .orf: only an Olympus camera can create a genuine ORF, and every editor that opens ORF also opens DNG. Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

PSD expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use PSD to ORF

  1. 1

    Add your PSD files: drop them here, choose them, or paste from the clipboard.

  2. 2

    Pick the colour that replaces transparent areas, since DNG has none.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .dng files one at a time or together as a ZIP.

Why use Aback Images for psd to orf

Where a ORF would go

ORF files are opened by OM Workspace, Lightroom, Photoshop Camera Raw, Capture One and RawTherapee, and every one of them opens the DNG too.

DNG next to PSD

The DNG is written uncompressed, so expect it to be several times larger than the PSD, which stores raw or RLE (PackBits) channel data, ZIP in some 16 and 32-bit files.

Written without a lossy pass

The DNG is written uncompressed, so the pixels decoded from the PSD arrive unchanged, apart from precision beyond 8 bits per channel.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

PSD vs ORF

What changes from PSD to ORF

Encoding: the PSD uses raw or RLE (PackBits) channel data, ZIP in some 16 and 32-bit files; ORF uses losslessly compressed sensor data, with a preview and thumbnail, and the download is a Linear DNG: demosaiced 8-bit RGB with the colour matrices raw editors need.

Bit depth: 8, 16 or 32 bits per channel in the PSD; ORF allows 12 bits per channel, and the DNG written here has 8 bits per channel, linearised. 16 and 32-bit documents are reduced to 8 bits per channel.

Colour: RGB, CMYK, Lab, greyscale, indexed or multichannel in the PSD; ORF supports camera RGB from a Bayer mosaic, written here as 8-bit sRGB.

Transparency: the PSD stores it as transparent layers plus extra alpha channels; the DNG has none, so transparent areas are filled with the colour you choose.

Other images: the PSD can hold layers, masks, adjustment layers and smart objects; only the main image is converted.

Metadata: the PSD can carry XMP, EXIF, IPTC and ICC in image resource blocks; ORF can carry EXIF and Olympus maker notes, which also contain the preview, but nothing is copied across.

About PSD

PSD is Adobe Photoshop's layered working format. It keeps layers, masks and effects, but almost nothing outside Photoshop can display it, so finished designs are exported to PNG or JPG.

A PSD has five sections: a header ('8BPS', channel count, size, depth, colour mode), colour mode data, image resources (thumbnail, ICC, XMP, resolution), layer and mask information, and finally the merged composite image that the Maximize Compatibility option saves.

PSD files usually come from Photoshop and apps that save Photoshop documents, such as Affinity Photo, GIMP, Photopea and Krita.

About ORF

ORF is the raw format of Olympus and OM System cameras, built around Four Thirds and Micro Four Thirds sensors. It stores 12-bit sensor data with a JPEG preview kept inside Olympus's maker notes.

ORF looks like TIFF but replaces the version number 42 with the letters 'RO', so a little-endian file starts 'IIRO' and generic TIFF readers reject it. Its JPEG preview is not in the main image directory but inside the camera-settings block of Olympus's maker notes.

ORF files come from Olympus E-series DSLRs, OM-D and PEN mirrorless cameras and OM System bodies.

When converting PSD to ORF makes sense

Forms and workflows that ask for ORF usually feed a raw editor, and each of those opens DNG as well, so the DNG can take the ORF's place. Keep the PSD if you only need to view or share the picture.

What ORF offers when it comes straight from the camera: Compact files from a smaller Four Thirds sensor; High Res Shot results stored as a single file; Supported across two decades of Olympus and OM System bodies. Its drawbacks: An 'IIRO' header that generic TIFF readers reject; 12-bit depth, less than most full-frame raw files; A preview hidden inside the maker notes.

Limitations

  • The merged composite is converted, so hidden layers stay hidden and visible ones are flattened together.
  • Files saved with Maximize Compatibility turned off may hold no full-size composite; then only the small embedded thumbnail is available.
  • The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the PSD.

Frequently asked questions

Why do I get a .dng file instead of a .orf?

A real ORF is written by Olympus cameras and holds the sensor's own readings (12 bits per channel, stored as losslessly compressed sensor data, with a preview and thumbnail) along with EXIF and Olympus maker notes, which also contain the preview. A PSD holds no sensor data, so no software outside the camera can create a genuine ORF. The Linear DNG you get instead is Adobe's open raw format, and every editor that opens ORF files opens it with the same raw controls. It holds decoded pixels, so it adds no quality or dynamic range.

Does converting PSD to ORF lose quality?

DNG is written uncompressed, so the pixels are stored exactly as decoded. 16 and 32-bit documents are reduced to 8 bits per channel. Not carried over: any layers.

What happens to transparency when converting PSD to ORF?

PSD stores transparency as transparent layers plus extra alpha channels. DNG has no alpha channel, so transparent pixels are composited onto a solid colour, white unless you pick another. To keep transparency, convert to PNG, WebP or AVIF instead.

Are PSD layers kept?

No. The flattened composite that Photoshop saves inside the file is converted, so the result looks like the PSD with all visible layers merged. Files saved without Maximize Compatibility fall back to the embedded thumbnail.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.