DDS to ORF Converter
Convert DDS 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
DDS expected · other image formats also work
How to use DDS to ORF
- 1
Add your DDS files: drop them here, choose them, or paste from the clipboard.
- 2
Pick the colour that replaces transparent areas, since DNG has none.
- 3
Click Convert. Each file is decoded and encoded in a background thread on this device.
- 4
Download the .dng files one at a time or together as a ZIP.
Why use Aback Images for dds 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 DDS
Neither format compresses much, so the DNG lands close to the DDS in size.
Written without a lossy pass
The DNG is written uncompressed, so the pixels decoded from the DDS arrive unchanged.
Processed on your device
Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.
DDS vs ORF
What changes from DDS to ORF
Encoding: the DDS uses block compression (BC1 to BC7, also called DXT) or uncompressed RGBA; 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 bits per channel for common texture formats in the DDS; ORF allows 12 bits per channel, and the DNG written here has 8 bits per channel, linearised.
Colour: RGB(A); normal maps and packed masks store data rather than colour in the DDS; ORF supports camera RGB from a Bayer mosaic, written here as 8-bit sRGB.
Transparency: the DDS stores it as alpha inside the compressed blocks (BC2, BC3, BC7) or a 1-bit cut-out (BC1); the DNG has none, so transparent areas are filled with the colour you choose.
Other images: the DDS can hold mipmaps, cubemap faces or texture arrays; only the main image is converted.
Metadata: the DDS can carry a 128-byte header (plus a DX10 header) describing the pixel format, nothing about the picture; ORF can carry EXIF and Olympus maker notes, which also contain the preview, but nothing is copied across.
About DDS
DDS is a GPU texture format used by DirectX games. It stores block-compressed textures (DXT/BC) and mipmaps that graphics cards decode directly.
A DDS file starts with 'DDS ' and a 124-byte header giving the size, mipmap count and pixel format: a FourCC such as DXT1 or DXT5, or 'DX10' followed by an extra header naming a DXGI format. The largest mipmap comes first.
DDS files usually come from DirectX games, game mods and texture tools such as NVIDIA Texture Tools and Intel's texture plugin.
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 DDS 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 DDS 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
- Only the top-level image (the largest mipmap of the first surface) is converted; smaller mipmaps and other cubemap faces are left out.
- Normal maps and packed masks hold data rather than colours, so they look purple or odd as ordinary pictures.
- The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the DDS.
More conversions
Related tools
Convert ORF to DDS in your browser, made from the full-size preview your Olympus camera stored in the file. Batch, private, no uploads.
Shrink JPG, PNG, WebP, AVIF and GIF files with MozJPEG, OxiPNG and modern codecs, with a live before/after preview.
Resize to exact pixels, a percentage or a longest side, with Lanczos3 and Magic Kernel resampling. Batch ready.
Strip EXIF, GPS, XMP, IPTC and comments losslessly. Pixels are never re-encoded for JPG, PNG and WebP.
Convert between 34 image formats in bulk: HEIC, WebP, AVIF, JPEG XL, PNG, JPG, GIF, TIFF, SVG, ICO, PSD, RAW and more.
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 DDS 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 DDS to ORF lose quality?
DNG is written uncompressed, so the pixels are stored exactly as decoded. Not carried over: any mipmaps.
What happens to transparency when converting DDS to ORF?
DDS stores transparency as alpha inside the compressed blocks (BC2, BC3, BC7) or a 1-bit cut-out (BC1). 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 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.