Picture Editor

If something does not work

The file would not open

The editor reads the first bytes of a file rather than trusting its name, so a picture saved with the wrong extension still opens. What it cannot open is a file that is not an image, or a format no browser here decodes; it says which of the two it met rather than failing silently. Your original file is never modified either way.

A very large picture was refused, or slowed down

Everything is rendered by this device, so a photograph of a few hundred megapixels runs into the memory a browser tab is allowed rather than into a rule we invented. Where a reduced working copy is safe the editor offers one and says so; the file on your disk is untouched.

The export did not arrive

A page cannot see whether your browser finished saving a file, so the editor never claims it did. After an export the panel shows a receipt — the name, the byte size and the dimensions decoded back out of the file that was produced — and a button that hands you the same file again without re-rendering anything.

The edit disappeared after a refresh

Recovery is off until you turn it on, and some browsers refuse local storage entirely — a private window usually does. When that happens the editor says recovery is unavailable on this device rather than leaving you to discover it, and everything else keeps working.

Transparency turned white

JPG has no transparency, so anything transparent is flattened on the way in. The export receipt says so. Choose PNG or WebP to keep an alpha channel.

A step did not carry over to the rest of the folder

Some operations are tied to one composition — a crop drawn around a particular frame, a stroke healing one blemish. Those are listed before a batch starts rather than applied blind to forty other pictures where they would do damage.