Background
What to expect from an online photo editor
A browser photo editor is limited by three things: the memory available to the tab, the codecs the browser ships, and the absence of a colour-managed pipeline. Within those limits it is fully capable; outside them it cannot compete, regardless of what a marketing page claims.
Published Updated 5 min readEditorial policy
Memory is the first hard limit
An image must be decompressed to work on it. A 24-megapixel photo occupies roughly 96 MB in memory as raw pixels, before any copy for the preview or the output. On a phone browser, two or three such copies is enough to have the tab terminated by the operating system.
This is why well-built browser tools work on a downscaled preview and only process at full resolution on export — and why a tool that promises unlimited batch processing of huge files in the browser is overpromising.
Codecs are the second
A browser can only open what it can decode. JPG, PNG, GIF, WebP and now AVIF are safe. HEIC, TIFF and camera RAW generally are not, on most browsers. Any site offering those conversions is either uploading your file or shipping a WebAssembly decoder — both legitimate, but they are different products with different privacy implications.
Colour management is the third
Browsers assume sRGB and quietly discard embedded ICC profiles in many canvas operations. For screen use this is invisible. For print, or for images in Adobe RGB or ProPhoto, it means colour shifts you will not notice until the proof arrives.
What that leaves
Everything most people actually need: making an image the right size, the right shape, the right format and small enough to upload. Those tasks make up the overwhelming majority of image work, they are fully solvable in a browser, and they do not require an account or an installer.
Spotted something inaccurate? Send a correction — technical corrections are applied and the updated date changed.