Resource ·

Local Browser Image Processing: What It Means for Your Assets

Understand the privacy advantages and practical limits of processing icons, logos, and screenshots in your own browser.

How local processing works

AppKit Studio reads selected images through browser APIs and renders exports with Canvas in the browser. The current tool has no image-upload endpoint; selected source images are not intentionally sent to this server for generation.

PNG and ZIP outputs are created and downloaded by the browser. Refreshing or closing the page clears the working image state held in page memory.

Why it matters

Unreleased captures, logos, and branding can be sensitive. Keeping routine resizing and compositing on the device reduces the number of services that receive the material.

Local processing does not replace normal device security. Use an updated browser, protect your computer account, and avoid working with sensitive files on an untrusted shared machine.

What the site can still record

Like most websites, the hosting stack can record ordinary request information such as a path, time, IP address, User-Agent, and response status for reliability and security. This is different from receiving image bytes selected in the tool. See the Privacy Policy for the current description of logs, language cookies, and advertising technologies.

Google Play requirements can change. Verify current details in the official Play Console preview-assets guidance and in your Play Console before publishing.