ORF to DDS Converter
Convert ORF to DDS in your browser. The preview inside the maker notes is found by scanning the whole file, and that preview is what gets converted. No raw development happens here. You get an uncompressed 32-bit RGBA DDS texture with a single mip level, or DXT1 or DXT5 block compression if you choose it. Nothing is uploaded.
- Processed locally
- No upload, no wait
- No sign-up
- No watermark
Drop images here
or choose files · paste with Ctrl/⌘ V
RAW expected · other image formats also work
How to use ORF to DDS
- 1
Add your ORF files: drop them here, choose them, or paste from the clipboard.
- 2
Choose the DDS compression: none for an exact 32-bit texture, DXT1 or DXT5 for smaller GPU-ready files.
- 3
Click Convert. Each file is decoded and encoded in a background thread on this device.
- 4
Download the .dds files one at a time or together as a ZIP.
Why use Aback Images for orf to dds
Where the DDS goes next
DDS opens in game engines, Visual Studio, Paint.NET, GIMP, NVIDIA and Intel texture tools.
DDS next to ORF
The DDS stores the camera preview's pixels uncompressed, so it can be as large as the 12 to 30 MB raw file, or larger, depending on the preview's resolution.
No new artefacts
The preview inside the ORF is a camera JPEG; the DDS stores its decoded pixels uncompressed, so this step adds no compression damage of its own.
Processed on your device
Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.
ORF vs DDS
What changes from ORF to DDS
Encoding: the ORF uses losslessly compressed sensor data, with a preview and thumbnail; DDS uses block compression (BC1 to BC7, also called DXT) or uncompressed RGBA, and the download is an uncompressed 32-bit RGBA DDS texture with a single mip level, or DXT1 or DXT5 block compression if you choose it.
Bit depth: 12 bits per channel in the ORF; DDS allows 8 bits per channel for common texture formats, and the DDS written here has 8 bits per channel. The sensor's 12 bits are not used: the 8-bit camera preview is converted.
Colour: camera RGB from a Bayer mosaic in the ORF; DDS supports RGB(A); normal maps and packed masks store data rather than colour, written here as 8-bit sRGB.
Metadata: the ORF can carry EXIF and Olympus maker notes, which also contain the preview; DDS can carry a 128-byte header (plus a DX10 header) describing the pixel format, nothing about the picture, but nothing is copied across.
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 usually come from Olympus E-series DSLRs, OM-D and PEN mirrorless cameras and OM System bodies.
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.
When converting ORF to DDS makes sense
DDS is the better choice for game textures and mods, while ORF suits editing Olympus and OM System photos in a raw developer.
DDS strengths: Loads straight into GPU memory; Mipmaps included. Drawbacks to weigh: Not viewable outside game tools; Lossy block compression.
Limitations
- High Res Shot files combine several exposures in camera; the preview shows the combined result at its stored size.
- The DDS has a single mip level, so generate mipmaps in your engine or texture tool if it needs them.
- Uncompressed DDS textures take 4 bytes per pixel; DXT1 is an eighth of that and DXT5 a quarter, at the cost of lossy 4×4 block compression.
More conversions
Related tools
Convert DDS to ORF in your browser, saved as a Linear DNG, the raw file every ORF editor also opens. 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
Does converting ORF to DDS lose quality?
DDS is written uncompressed, so the pixels are stored exactly as decoded. Those pixels come from the camera's JPEG preview, so its compression stays, but nothing new is lost. The sensor's 12 bits are not used: the 8-bit camera preview is converted.
Which apps open DDS files?
Game engines, Visual Studio, Paint.NET, GIMP, NVIDIA and Intel texture tools. It does not open in web browsers.
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.