When you need a batch, not a single file
A single RAW to JPG conversion is easy. The real headache is a wedding, a product shoot or a holiday where you come home with 400 RAW files and need a folder of JPGs to deliver. Doing that one file at a time is not an option, so the question becomes: what is the least painful way to convert a whole folder at once, for free?
There are four practical answers. The browser method needs no install and handles most real-world batches; the desktop and command-line methods are better once you're doing this every week.
Method 1 — Batch convert in your browser (no install)
This is the method that surprises most people, because nothing gets installed or uploaded. The RAW decoder runs as WebAssembly on your own CPU, so files are processed locally and sequentially.
- Step 1. Open the converter above and let the page load fully.
- Step 2. In your file manager, press Ctrl+A (Windows) or ⌘A (Mac) to select every RAW file, then drag the selection onto the box. Hundreds of files queue up at once.
- Step 3. Choose JPG and set quality — 92% for deliverables, 80–85% if you're posting a large gallery online.
- Step 4. Click Download all to save every JPG in a single action, then Clear all before the next group.
Because nothing is uploaded, batch size is limited by your RAM rather than a quota. It handles Canon CR2 and CR3, Nikon NEF, Sony ARW, Fujifilm RAF and Adobe DNG in the same list. The dedicated RAW to JPG converter is the general entry point; there are also per-brand tools for CR2, NEF, ARW, DNG and RAF.
Method 2 — Lightroom, Capture One or DxO (payware, best control)
If you already pay for a RAW editor, its batch export is the most capable route because you can apply consistent develop settings first and export the whole selection:
- Lightroom Classic: develop one image, then in the Library grid select all, right-click → Export → JPEG, and set resolution, sharpening and file naming.
- Capture One: use Process Recipes with a JPEG recipe, then select the batch and output.
- DxO PhotoLab: select all, apply a preset, and export to JPEG.
The advantage is a consistent look and full metadata control; the cost is a subscription or licence, plus the time to develop before exporting.
Method 3 — Free desktop batch tools
- Darktable — open source; create a style, select the batch and export with the JPEG preset.
- RawTherapee — has a Batch Queue and a CLI mode that converts a folder unattended.
- XnConvert — free batch converter with excellent format coverage and simple output naming; ideal if you don't need deep editing.
- digiKam — batch processing integrated with a photo library.
Method 4 — Command line (fastest for archives)
Once set up, a shell loop is the fastest and most repeatable option, because you start it and walk away:
- ImageMagick:
mogrify -format jpg -quality 92 *.CR2converts every CR2 in the folder. - RawTherapee CLI:
rawtherapee-cli -o ./out -j92 -c *.nefprocesses a whole folder with a preset. - dcraw / LibRaw tools: extract to TIFF or PPM first, then convert, if you need maximum control.
Command-line tools read RAW from almost every brand and run without a GUI, which makes them perfect for backing up and converting a multi-year archive overnight.
Tips for large batches
- Work in groups of 100–200. Each decoded RAW can use several hundred MB of RAM; a smaller group keeps the machine responsive and avoids browser slowdowns.
- Keep the tab in the foreground. Browsers throttle background tabs, which slows long jobs.
- Don't convert blindly. If you shoot RAW deliberately, keep the originals — batch converting everything to JPG and deleting the RAW destroys your editing headroom.
- Mind the naming. Img_1234.CR2 becoming Img_1234.jpg is fine, but a delivery folder is easier to use with a project prefix.
- Free disk space first. 400 RAW files at 30 MB are 12 GB; the JPGs add several more.
Organising and naming the output
A batch of 400 files all called "IMG_0001.jpg" is hard to use as a delivery. Before converting, decide how the JPGs should be named and where they should land. Desktop tools such as XnConvert and Lightroom let you set a filename mask (for example, "ClientX_###") and an output folder. A browser converter keeps the original names, which is fine for personal use but worth renaming for client work.
A practical end-to-end batch workflow
- 1. Cull first. Delete the obvious rejects in your RAW browser so you don't convert images nobody wants.
- 2. Pick a quality. 92% for deliverables, 80–85% for a large web gallery where size matters.
- 3. Convert in groups. 100–200 files at a time keeps memory use sane.
- 4. Verify a sample. Open two or three JPGs at 100% to confirm exposure and colour before shipping the folder.
- 5. Back up both. Archive the RAW originals and treat the JPGs as the working copies you send out.
Does batch conversion hurt quality?
No more than a single conversion. The output is an 8-bit JPEG at your chosen quality — visually lossless at 92% for normal use. The point of batching is speed and consistency, not degradation. The one thing it can't do is apply careful per-image edits; if a shoot needs individual grading, develop first and batch-export second. For the background on why, see RAW vs JPEG.