How to convert RAW to JPG, every way

A RAW file is not a picture yet. It is sensor data plus a recipe, and something has to cook it before anyone else can look at it. There are six ways to do that, and they are not interchangeable: one is instant and neutral, one gives you the camera's look, one is an edit. This is the whole list, what each one costs you, and which one to reach for depending on whether you need one frame tonight or a card by Friday.

What a conversion actually does

A RAW holds what the sensor recorded: one brightness value per photosite, behind a color filter, before white balance, before a color space, before any tone curve. Converting it to a JPG means demosaicing that grid into full color pixels, applying white balance and the camera's color matrix, mapping the linear data to a curve your screen can show, then compressing the result. Every route on this page does those same steps. What differs is who chose the recipe, how much of the sensor data survives, and how long you wait.

Two things follow. First, there is no such thing as a conversion with no look; neutral is also a choice. Second, because the JPG is a render, you can make as many as you like from the same RAW without touching it. The RAW stays the negative.

The fastest way: a converter in your browser

The route most people do not know exists: a converter that runs inside the browser tab, with no upload. Kepla's RAW to JPG converter ships LibRaw, the same open source decoder behind a long list of desktop RAW tools, compiled to WebAssembly. You drop CR2, CR3, NEF, ARW, RAF, ORF, RW2 or DNG files on the page, every one shows its embedded preview in under a second, and a full develop from the sensor data takes a few seconds per file on a recent laptop. Batch of forty, one ZIP, and the files never leave your machine. Turn the wifi off after the page loads and it keeps working.

What you get is an honest neutral render: camera white balance and the maker's color matrix, no profile, no preset. There are exposure, white balance and contrast sliders for the frame that came out flat, a histogram, and the camera settings beside it. What you do not get is an edit. It is the right tool when you need a clean JPG now, not when you need your look.

The privacy point matters more than it sounds. Most "online" converters upload the file to a server, render it there, and hand back a link. That is a 40 megabyte round trip per frame, a copy of your client's wedding on someone else's disk, and terms of service you did not read. Whether that is safe is a separate question; a converter that never uploads makes it moot.

The camera already did it once

Every RAW from a modern body carries a JPEG the camera rendered at capture, at or near full size on most Canon, Nikon and Fujifilm bodies, smaller on many Sony, Olympus and Panasonic ones. It is the picture you saw on the back of the camera, Picture Style or Film Simulation included. Pulling that JPEG out of the file is not a conversion at all; it is a copy, and it takes milliseconds.

That is the "camera preview" mode in the browser tool above, and it is also what any culling app is showing you when it feels instant. It is the right answer for a sneak peek, for checking a card, and for anyone who likes the camera's look and just needs the file. It is the wrong answer when the preview is 1616 by 1080 and the client wants a print. What is inside your RAW file covers the sizes brand by brand.

Built into macOS and Windows

macOS Preview and Photos open most RAW formats through the system RAW decoder, and Export gives you a JPG. Windows reads RAW in Photos once the Raw Image Extension is installed from the Store. Both work, both are free, and both have the same two limits. The decoder ships with the operating system, so a body released after your last OS update is not supported until the next one; CR3 famously took a while to arrive. And there is no batch worth the name: export is one file or one folder at a time, with a quality slider and little else.

For one file, the built in route is fine. For a card, you will want something with a queue.

Lightroom, Capture One, and the makers' apps

Lightroom Classic, Lightroom, Capture One, DxO, ON1 and darktable all convert RAW to JPG as the last step of an edit. That is the point: you import, you develop, you export. The conversion is excellent, the color management is real, and the export dialog does resize, sharpen, watermark and rename in one pass. The cost is the import. A 4,000 frame wedding is a catalog, previews, and an evening, before a single JPG exists.

The makers' own apps are the other end. Canon Digital Photo Professional, Nikon NX Studio, Sony Imaging Edge, Fujifilm X RAW Studio and OM Workspace render your files with the exact Picture Style, Picture Control or Film Simulation the camera used, lens corrections included, for free. They are slow, the interfaces are what they are, and each one reads only its own brand. But if the brief is "make it look like the camera JPEG, at full quality", nothing else is closer.

Which one, when

One frame, tonight, for a client or a post: the browser converter, camera preview mode if you like the camera's look, full develop if the frame needs an exposure nudge. Under a minute door to door. The whole routine is here.

A card you need to check or share before you leave the venue: the browser converter again, because it is the only route that does forty files without an import and without a signal.

The delivery: your editor. The conversion is the last step of your edit, and nothing on this page replaces the edit. The export settings that matter are shorter than the dialog makes them look.

The archive, or a client who asked for the RAWs: do not convert. Hand over the RAW, or decide whether to. A JPG is a print of the negative, and the negative is the thing worth keeping.

And the card as a whole, the four thousand frames before any of this? That is culling, not converting, and it is the job Kepla does on your Mac: it clears the obvious misses, names the reason on every frame it sets aside, and leaves the choosing to you. Request Founding Access.

FAQ