Requirements, privacy and known limitations

What Raw Photo Editor needs to run, what stays on your device and what the browser stores, the editor's known limitations, and how to fix the most common problems.

6 min read Updated Open the editor →

Raw Photo Editor needs a desktop browser with WebGL2 and enough memory for the photo you open. It decodes and edits every file on your own computer: nothing is uploaded, and the only things it keeps are your settings, in your browser’s storage. This page lists what it needs, what it stores, what it can’t do yet, and what to do when something goes wrong.

What you need

  • A browser with WebGL2 that can render to floating-point textures (the EXT_color_buffer_float extension, or the half-float version as a fallback). Current Chrome, Edge and Firefox on the desktop have both. Without them the image area shows The image view stopped with the reason, for example WebGL2 is not supported by this browser.
  • A graphics card from the last few years. Every adjustment runs on it. Integrated graphics are fine.
  • Memory. A 24-megapixel file needs a few hundred megabytes while it is open; files of 60 to 100 megapixels need a few gigabytes. Supported cameras explains why.
  • An internet connection to load the editor. There is no offline mode: parts of the editor load the first time you open them.

Browser status

The editor is built for current desktop Chrome, Edge and Firefox. On tablets, touch gestures work (see viewing and comparing). Safari on the Mac and iPad, iPhone, and Android phones have not been fully tested yet. They may work, but treat them as unverified.

Privacy: what stays on your device

When you open a file, the browser reads it into memory on your computer. LibRaw, compiled to WebAssembly, decodes it in a background worker, and your graphics card renders every adjustment. Export Image writes the result through your browser’s download. At no point is the photo, or any part of it, sent over the network. There is no account to create.

The site loads its pages, code and fonts from its own host (Cloudflare) and nothing else: there are no analytics, no advertising or tracking scripts and no tracking cookies. Like any host, Cloudflare sees technical data such as your IP address when it serves the pages. The privacy policy has the details.

What the browser stores

WhatWhereContains
Saved editsIndexedDBThe settings of each photo you edit (sliders, masks, crop, heal spots), its file name and size, and a fingerprint of the file so the edit can be matched next time. Never the photo itself.
PresetslocalStorageYour own presets.
PreferenceslocalStorageThe Settings choices: control density, hints, shortcut switches.

Saved edits keep up to 500 photos; the least recently edited are dropped first. The fingerprint is calculated from the file’s size and its first and last megabyte, so renaming a file keeps its edit.

To remove saved edits, open Settings and click Clear saved edits. To remove everything, delete this site’s data in your browser’s settings. Edits you download with Save Settings (.json) are ordinary files on your disk. History and autosave covers how saving works.

Known limitations

Opening files

  • Camera RAW files only, in 24 formats. No JPEG, PNG, TIFF or HEIC, and no Sigma .X3F.
  • A file with another extension isn’t opened: the editor says so in a message over the photo.
  • One photo at a time. There is no catalog, filmstrip, batch processing or RAW+JPEG pairing.
  • Fujifilm X-Trans files take 10 to 15 seconds to decode at 26 megapixels.
  • A camera newer than the bundled LibRaw 0.22 may not open until LibRaw adds it.

The look and the adjustments

  • The default look is flat and neutral, often about a stop darker than the camera’s JPEG. There are no camera profiles or film simulations. The only automatic adjustment is a DNG file’s BaselineExposure.
  • No lens corrections (distortion, vignetting, chromatic aberration) and no perspective correction. Crop offers straighten, 90° rotation and flips.
  • No AI subject or sky selection. Masks are linear and radial gradients, a brush, and color and luminosity ranges.
  • Retouching is the Heal / Clone tool only. The backscatter finder is experimental: it proposes spots, and false positives such as fish eyes, glints or sparkling coral have to be turned down by hand.

Viewing

  • 100% means one image pixel per physical screen pixel, so on a 2× display the photo looks half as large as on an ordinary monitor.
  • In a window narrower than 1220 pixels, History opens over the left edge of the photo instead of beside it.

Export

  • JPEG, PNG and TIFF at 8 bits per channel, in sRGB. TIFF is uncompressed 8-bit RGB. There is no 16-bit output.
  • Camera data (EXIF) is not copied into the exported file.
  • The full size is limited by your graphics card. When it can’t render or encode the full size, the editor tries 75%, 50%, 35% and 25%, saves the first that works, and tells you (an image larger than the card’s texture limit starts at that limit), for example Saved alps.jpg at 4500 × 3000, 75% of the requested size: Out of GPU memory. See export.

Saving

  • Saved edits live in this browser profile only. They don’t sync, and another browser or computer doesn’t see them. Presets are per browser too.
  • A private window keeps edits only until it is closed.
  • The latest state of an edit is saved, not its history: after a restore, the History list holds Original and Restored edit.

Troubleshooting

The image area is black or says “The image view stopped”

A graphics driver reset or a crash takes the WebGL context away. The editor shows Restoring graphics and rebuilds the view when the browser hands the context back. If that doesn’t happen within five seconds, you see The image view stopped: click Restart view. Your edit lives outside the view and is not lost.

If the message names WebGL2 or the float extensions, the browser has no usable GPU access. Turn on hardware acceleration in the browser’s settings, update the browser and the graphics driver, or try another browser.

Export is smaller than expected or fails

The status line under Export Image gives the reason. Out of GPU memory, The browser limited the image to … and The graphics card handles at most … pixels on the long edge mean the graphics card couldn’t hold the full size. Close other tabs and graphics-heavy programs and export again, or choose a smaller size with Long Edge. The browser could not encode a JPEG this large is a browser limit on the encoder: try PNG or TIFF, or a smaller size.

My edit wasn’t restored

The edit is matched to the file in this browser profile. It won’t be there if you used a private window, another browser or profile, cleared the site’s data, or edited more than 500 other photos since. A file that another program has rewritten (for example to add keywords) can also count as a new photo.

If the canvas shows Edits aren’t being saved in this browser, saving to the browser’s storage failed. Click Save settings to download the edit as a .bre.json file, and use Load settings in the toolbar to apply it later.

Keyboard shortcuts do nothing

Check that Keyboard shortcuts is on in Settings. Shortcuts are also ignored while you are typing in a slider’s number box: press Enter or Esc to leave the box, then press the key again. The keyboard shortcuts page lists every key.

A file won’t open

See when a file doesn’t open.