( Price and access )
You can use the published tools without payment or registration. This page explains what is included, practical limits, and how the project may be funded.
The JPEG, PNG and WEBP comparison shows the same image in all three formats, with bytes and measured RGB difference; WEBP output appears only when the browser supports encoding.
Images are decoded into browser memory. Large photos and extensive batches need more memory, so the editor uses a preventive pixel budget rather than advertising a universal file count. Performance varies by browser and device.
The batch editor benchmark publishes reproducible measurements for 1, 10 and 25 images, and the help center covers memory, preview and ZIP failures.
Image processing happens in the browser without sending the photo file to the application server. The page may still make network connections for site services and dependencies.
The local processing map details the pixel path and the possible external connections.
The project may use advertising to help fund infrastructure, development, and maintenance. Ads will only be enabled after domain approval and applicable consent.
Privacy, terms, cookies, contact, author, methodology, changelog, and access-transparency pages remain blocked from ad units. The studio and download flow are not ad areas either.
If the access or funding model changes, it should be explained here and recorded in the changelog before making a different promise.
Last reviewed: 5 September 2026.