Skip to main content

Architecture explained

How your photo is processed locally

This map separates the pixel path inside the browser from technical, measurement, or advertising connections the page may make.

Image path

The arrows below represent the functional sequence observed in the editor. Each card describes a different responsibility.

  1. 1. You choose the image

    The browser receives the file through the picker or drop area. The page validates its type and attempts to decode its pixels.

  2. 2. The browser retains the work

    Studio files and adjustments may remain in IndexedDB; preferences and temporary flow data use browser storage.

  3. 3. Workers process pixels

    Adjustments, thumbnails, and exports are calculated locally. Canvas displays the preview; it is not proof of final-output resolution.

  4. 4. The batch becomes a file

    Individual results are bundled by a ZIP library packaged with the project, without fetching ZIP code from a CDN during export.

  5. 5. The browser starts the download

    A temporary in-memory address is created for the image or ZIP. The new copy is saved through the browser download mechanism.

External page connections

Local processing does not mean the entire page works without a network. This distinction avoids an absolute privacy promise.

Storage and deletion

IndexedDB lets the studio recover files and adjustments across operational routes. localStorage holds preferences such as consent and theme; sessionStorage carries temporary export data. The browser and its storage policies determine when this data may be removed.

The complete legal description, categories, and available choices remain on the Privacy and Cookies pages.

Verify it yourself

MethodologySee how capabilities and claims are tested.Batch benchmarkReview results, ranges, and raw data.Test the batch editorRun the local workflow with your own images.