ZipTool
ZipTool

Convert RAW to JPG online

A real RAW develop — LibRaw compiled to WebAssembly — running in this tab. Drop your photos or the zip they came in, press the camera button, get the JPEGs. The photos never leave your device.

Load from cloud

Drop RAW photos (or a zip of them) anywhere on this page

The RAW develop runs entirely in your browser. Photos never leave your device.

A RAW file is not a picture yet — it is what the sensor captured, and turning it into a JPEG means someone has to develop it: demosaic the color filter array, apply white balance, convert to sRGB. Online RAW converters dodge that work one of two ways: they upload your photos to a server that runs the conversion who-knows-where, or they merely unwrap the small JPEG the camera embeds for thumbnails. This page does neither. The *developer* travels to you — LibRaw, the open-source engine behind many desktop converters, compiled to WebAssembly — and your photos never travel at all.

The distinction is checkable, not a slogan. Open DevTools, convert a photo, and watch the Network tab: the only fetch is the one-time engine download (~1.1 MB, from this site’s own domain, cached afterwards), and no request ever contains your photo. Load the page, go offline, and conversions still work. And if your shoot arrived as a zip — a client delivery, a backup — drop the zip: every RAW inside opens from the file tree, and the converter works straight out of the archive, no extraction step.

How to convert RAW to JPG

Nothing to install, nothing to sign up for:

  • Drop your RAW files anywhere on this page — one file, several, or the whole zip — or click to browse, or paste a URL.
  • Press the camera button in the toolbar (or ⌘K → *Convert RAW photos to JPG*): every RAW in the current folder converts — up to 50 per run — and downloads as one `<archive>-jpg.zip` with the folder structure kept.
  • Each photo is a full develop, so expect a second or three per file; the progress bar counts files honestly and you can cancel between them.
  • Want to *look* first? Click any RAW and it develops in the viewer at full resolution with zoom, metadata, and ← / → through the folder; the status bar’s Download .png exports that one file exactly as developed.

A real develop, not the embedded preview

RAW files carry a small JPEG the camera bakes in for thumbnailing, and “instant” converters usually just unwrap it — which is why their output never looks better than the camera’s own JPEG. Here the sensor data itself is processed: the Bayer pattern is demosaiced (AHD interpolation), the camera’s as-shot white balance is applied, and the result is converted to sRGB — the same pipeline a desktop RAW converter runs. The JPEG you download is rendered from that develop (quality 92), which is why each file takes a moment and why fine detail survives zooming.

One honest consequence of a real develop: a RAW has no single “correct” JPEG. Your camera’s own JPEGs apply the manufacturer’s rendering — Canon Picture Styles, Nikon Picture Controls, Fujifilm film simulations — while this converter applies the as-shot white balance and a neutral sRGB conversion. Two valid interpretations of the same capture; expect the tones to differ slightly from the camera’s back-of-screen look, the way two desktop converters differ from each other.

What you trade when you go RAW → JPG

The trade is headroom. A RAW keeps 12 or 14 bits per photosite and the exact white-balance and exposure the camera recorded; a JPEG is 8-bit and already rendered — convenient everywhere, recoverable nowhere. For sharing, printing, and handing files to people without a RAW editor, JPEG is the right destination; keep the RAWs as the negative.

Sizes run the expected direction: RAWs compress photosite data losslessly (or near it), so the JPEGs are usually smaller than their sources — a 25 MB full-frame RAW typically lands between 3 and 10 MB as a quality-92 JPEG, depending on the megapixel count and the scene.

Metadata does not survive the export. The JPEGs are re-encodes of the developed pixels, so EXIF — shooting date, camera, lens, and GPS location — does not travel with them. For photos you are posting or sending onward, that is a privacy plus; if you need the metadata, it stays readable in the viewer’s Info panel while you still have the RAW.

Which RAW files convert here

The whole camera-RAW family this site develops: Canon CR2 and CR3, Nikon NEF and NRW, Sony ARW, Adobe DNG, Fujifilm RAF (X-Trans included), Olympus/OM System ORF, Panasonic RW2, Pentax PEF — plus the vendor tail (RWL, SRW, IIQ, 3FR and more). Two honest exclusions: plain .tif/.tiff are TIFFs, not camera RAW, and Sigma .x3f needs a decoder this engine build does not include — both are refused rather than rendered wrong.

Converting is only half the story — if what you actually want is to *inspect* RAW photos (zoom to 100%, cull a folder, check what is inside a delivery zip), the online RAW viewer is the same engine framed for looking; each format’s reference page lives under /open/…. Shooting an iPhone? That is HEIC, not RAW — different page, same no-upload principle.

Honest limits

Real capability, real boundaries — stated up front.

  • A develop takes time — roughly one to three seconds per photo, longer for 50-megapixel medium format; the progress bar counts files and cancel stops between them (a develop already running finishes and is dropped).
  • One-time engine download (~1.1 MB) from this site’s own domain, cached by your browser; afterwards converting works offline.
  • Folder batches convert the first 50 RAWs of the current folder per run — rerun per subfolder for more, or in another folder.
  • Per-file export is PNG — the viewer’s Download .png is the byte-exact developed render; the JPEG path is the batch (quality 92, metadata stripped).
  • Size caps keep the tab alive: 128 MB per file, 512 MB of developed pixels — far above any camera file, but stated rather than discovered.
  • No editing — this is convert-and-inspect; white balance, exposure, and tone stay as the develop renders them.

Credits

The develop engine is LibRaw (LGPL-2.1), distributed via rawconvert-wasm (MIT) as WebAssembly and served from this site’s own domain as standalone, replaceable files. This page adds the viewer, the batch converter, and the archive integration; LibRaw does the developing.

Frequently asked questions

How do I convert RAW to JPG without uploading?

Drop the files on this page and press the camera button in the toolbar (or ⌘K). LibRaw compiled to WebAssembly develops each photo in your browser, and the JPEGs download as one zip. You can go offline after the page loads and it still works — no queue, no watermark, no server ever receives a photo.

Which formats does this RAW to JPG converter support?

Canon CR2/CR3, Nikon NEF/NRW, Sony ARW, Adobe DNG, Fujifilm RAF (X-Trans included), Olympus/OM System ORF, Panasonic RW2, Pentax PEF, and the longer vendor tail — the same family the online RAW viewer develops. Sigma X3F and plain TIFF are the honest exceptions: no decoder in this build, so they are refused rather than converted wrong.

Can I convert several RAW photos at once?

Yes — that is the main flow. The camera button (or ⌘K) converts every RAW in the current folder, up to 50 per run, and downloads them as one <archive>-jpg.zip that keeps the folder structure. Each JPEG is a full develop of the sensor data, which is why the run takes a second or three per photo.

Will the JPG look exactly like my camera’s JPEG?

Close, but not identical — and that is inherent to RAW, not a defect. A RAW has no single correct rendering: your camera applies its own picture profile, this converter applies the as-shot white balance and a neutral sRGB conversion. Expect the same scene with slightly different tones, the way two desktop RAW converters differ from each other.

Is this RAW to JPG converter free?

Yes, with no artificial limits — no daily caps, no watermarks, no sign-up. The limits that exist (50 photos per batch run, 128 MB per file) exist to keep your browser tab responsive, not to sell an upgrade.

Does the JPG keep my photo’s EXIF and GPS data?

No. The JPEGs are re-encodes of the developed pixels, and metadata — including where the photo was taken — does not travel with them. For sharing, that is usually a privacy plus. The metadata is not lost while you are here: the viewer’s Info panel reads camera, lens, exposure, timestamp, and GPS straight out of the RAW.

Drop here.