Skip to main content

Verifiable support

Photo editor help

Practical troubleshooting for uploads, memory, previews, formats, and batch export, aligned with the tool's current behavior.

Preserve the original

Work with a copy and inspect the exported file before deleting or replacing the original photo.

Reduce the load

For memory or ZIP errors, the most useful action is to split the batch and reduce very large images.

Include context

When reporting a problem, include browser, system, count, dimensions, format, and the displayed message—without sending private photos.

Common problems and how to resolve them

An image was skipped during upload

Symptom: The summary says one or more files were skipped, or no image was added.

  1. 1Confirm that the file is a JPEG, PNG, or WEBP image with browser support; changing its extension does not convert its contents.
  2. 2Open the image in your device's photo application and export a new JPEG or PNG copy if it is damaged or uses an unrecognized encoding.
  3. 3Add fewer photos at a time when part of the batch exceeds the preventive pixel budget.

Why this happens: The editor inspects the type and attempts to decode every file. Invalid files and items over the preventive budget are counted as skipped.

The browser reports high memory use or rejects part of the batch

Symptom: Upload shows a temporary-memory estimate or says that images exceeded the preventive pixel budget.

  1. 1Remove images you will not edit and load the batch in smaller groups.
  2. 2Reduce very large photo dimensions beforehand when you do not need the original size.
  3. 3Close other demanding tabs and retry. Available memory varies across devices and browsers.

Why this happens: There is no universal maximum photo count. Cost depends on the total decoded pixels, not only the files' disk size.

The preview looks different from the thumbnail

Symptom: The central photo does not appear to reflect the expected item or adjustment yet.

  1. 1Select the correct thumbnail and wait for any active processing to finish.
  2. 2Check whether the adjustment was applied to the current image, selected images, or the full batch.
  3. 3If the preview remains stale, reload the page and import the original files again; do not replace your originals until you verify the export.

Why this happens: Thumbnail and preview are separate renders. Product tests verify that Automatic Adjustment updates both, but devices under memory pressure may render late.

The ZIP was not created or some photos failed

Symptom: The download screen reports an export failure or says that some files could not be exported.

  1. 1Use “Retry failed files only” when the button appears; the ready archive retains completed items.
  2. 2Return to the editor and export a smaller batch if ZIP creation fails completely.
  3. 3Keep the tab open until the browser finishes generating and offering the file.

Why this happens: ZIP creation runs in the browser. Cancelling export discards download progress but preserves edits so you can return to the editor.

WEBP output is missing when the browser lacks support

Symptom: The export window offers JPEG and PNG but not WEBP.

  1. 1Use JPEG for photographs without transparency or PNG when transparency must remain.
  2. 2Update your browser and retry if WEBP is required.
  3. 3Do not infer export support only because the browser opened a WEBP file; decoding and encoding are different capabilities.

Why this happens: WEBP appears only when an in-browser check confirms that the canvas can generate that format.

Transparency became a solid background

Symptom: Transparent areas appear filled after export.

  1. 1Choose PNG to preserve transparent pixels.
  2. 2Avoid JPEG when the result needs an alpha channel because JPEG does not preserve transparency.
  3. 3Inspect the downloaded file in a viewer that displays transparency; some applications use white only as the viewing background.

Why this happens: JPEG export composites transparent areas against a background; PNG is the validated option for retaining transparency.

Before retrying

Record the displayed message, keep the originals, reduce the batch, and test one image. If that image fails alone, create a new JPEG or PNG copy. If every image fails, check the browser and available download storage.

Last reviewed: 12 September 2026. This page describes the validated public flow and will be reviewed when product messages, formats, or limits change.