1. Confirm the capability
Code and the factual matrix record formats, controls, observable results, and limitations. Published copy must not expand that scope.
Transparency
Editorial and testing methodology
The process used to keep published claims aligned with what the tool actually does.
Verification workflow
2. Test with controlled images
JPEG and PNG, WEBP input, invalid-file, and controlled batch fixtures check dimensions, signatures, transparency, cancellation, and export. WEBP output appears only when the browser supports it.
3. Exercise browsers and screens
Essential flows are tested in desktop and mobile profiles. Emulated results are identified as such, and the pending physical-device matrix remains disclosed.
4. Review content and publication
Landing pages, articles, metadata, FAQs, and structured data must describe the same behavior with visible dates and limits.
Editorial rules
- Separate general photography concepts from features actually available in the editor.
- Use reproducible product tests and primary sources for external concepts when needed.
- Produce real tool screenshots with project-owned images without simulating unavailable controls.
- Review EN and PT-BR for meaning and natural phrasing while preserving the same facts and limits.
- Record limitations and correct content when product behavior changes.
Code and fixtures
Automated checks use controlled images and observable results.
Browser
Flows, accessibility, and responsive dimensions are exercised in a browser.
Real screenshots
Visual comparisons come from the running interface and are reviewed before publication.
Last reviewed: 5 September 2026.