Guide
Developing camera RAW files into JPGs in the browser
A RAW file is not really an image yet. It is the data your camera’s sensor recorded, before the camera decided on colors, contrast and sharpening. That is why photographers love it for editing, and why almost nothing outside photo software can open it: phones, browsers, office suites and upload forms see an unknown file. This tool develops RAW files into ordinary JPGs, PNGs or TIFFs on your own device.
What is inside a RAW file
Behind the colored filters of a camera sensor, each pixel measures only one color, red, green or blue, in a mosaic pattern. A RAW file stores those single values at 12 or 14 bits each, plus metadata such as the white balance the camera chose and a preview JPEG for the camera’s screen. Developing means estimating the two missing colors for every pixel (demosaicing), applying white balance and a color matrix, and converting the result into a standard color space such as sRGB.
Two ways to get a JPG
“Develop sensor data” runs that whole process with LibRaw, the open-source library behind many RAW tools. You get the full sensor resolution and a neutral rendering. “Embedded camera JPEG” instead extracts the preview JPEG the camera stored inside the file. It is ready in a moment and looks exactly like the picture on the camera’s screen, with the camera’s own picture style, but some cameras store only a reduced-size preview.
White balance and half size
With “As shot”, the developer uses the white balance the camera recorded, so colors match what you saw. “Auto” lets LibRaw estimate it from the image, which can rescue shots taken with the wrong preset, such as daylight under tungsten light. “Half size” skips full demosaicing and produces an image half as wide and tall, about four times faster. That is plenty for sharing on social media and ideal for a quick look through a card full of images.
Why the result looks flatter than on the camera
Cameras add contrast, saturation, sharpening, noise reduction and lens corrections to their own JPEGs. A neutral development does not, so it can look softer and paler at first sight; it simply has more room for editing. When you want the camera’s look without editing, switch to the embedded JPEG. When you want to edit, a TIFF output keeps the developed image without JPEG compression.
Speed and memory
Developing runs in a background worker. Typical 20 to 30 megapixel files take a few seconds each on a laptop; Fujifilm X-Trans files take longer because their sensor pattern needs a more complex algorithm, and 50 to 100 megapixel files need plenty of memory. Phones can manage single files but are slow with batches; Half size helps a lot there.
When a file cannot be developed
Very new cameras sometimes use a compression the decoder does not know yet, and a few licensed formats cannot be developed by open-source software at all. If the developed data comes out corrupted, which shows up as one flat color across most of the picture, the tool notices and falls back to the embedded camera JPEG, telling you what happened. If no preview exists either, you get a clear error instead of a broken image.
Brand-specific pages
The same engine powers the pages for CR2 and CR3, NEF, ARW, DNG and RAF, each with notes on its own quirks. After converting, Compress Image can shrink JPGs further for email, and EXIF Data Remover shows what metadata your original files carry.
Checked against the current version of the RAW to JPG on .