Skip to main content
PhotoEditor

( Editorial responsibility )

Bruno Dissenha

Developer responsible for maintaining PhotoEditor.sbs and for factual review of content published on this domain.

Declared responsibilities

  • Maintain the editor implementation and review changes that affect image processing.
  • Check copy, metadata, FAQs, and structured data against verified product capabilities.
  • Review technical articles, examples, limitations, dates, and sources where applicable.
  • Correct or remove statements that cannot be reproduced in the current tool version.

Review scope

Review covers observable editor behavior, instruction clarity, and consistency between the product and published content. This page does not claim certifications or present articles as specialist advice.

The scope of the project itself — which operations exist, which were left out and why — is described on the About PhotoEditor.sbs page.

Project background

What the editor sets out to solve
Cropping, brightening, fixing color and preparing photos for publishing without sign-up, without a watermark on the result and without sending the photo to an editing server. The guides are written for people with exactly that problem, and say where the editor does not fit.
The central technical decision
Processing happens in the browser tab, with Canvas and Web Workers. That settles image privacy by architecture rather than by promise: a photo opened in the editor is not sent to an editing server. The trade is a real limit — very large photos and long batches depend on the device's memory.

Editorial record

Guides in Portuguese and English
Each version is written to read naturally in its language, with control names as they appear in the editor in that language.
Real, reproducible screenshots
Guide images are captures of the running editor, generated by a versioned script from the demo photo. When the editor changes, the captures are redone.
Facts checked in the code
Value ranges, control names and limits quoted in the guides are checked against the editor's code and a capability registry. An automated auditor blocks unsupported claims such as AI or offline operation.

Signed guides

Last reviewed: 7 November 2026.