Privacy
Your images are processed directly in your browser. They are not uploaded to our servers.
Privacy at a glance
The four facts that matter most.
No uploads
There is no upload step. Processing code runs in your browser and reads files from your device directly.
No server storage
Images exist only in your browser's memory while the page is open. Closing the tab discards everything.
No tracking
No analytics observe your images or actions. Only your theme preference is stored, in localStorage.
No accounts
No sign-up, no email, no profile. The tools work the moment the page loads.
What happens to your images?
The full lifecycle of a file, from pick to discard.
- 1
You pick files. They are read into your browser's memory — nothing is transmitted.
- 2
The tool decodes the image locally (native decoders, or a WebAssembly codec for AVIF).
- 3
Your chosen operation runs on the pixels via the Canvas API, on your device.
- 4
The result is re-encoded locally and offered as a download from your own browser.
- 5
When you close or refresh the page, all loaded images and results are discarded.
The original files on your device are never modified.
Browser processing
All image operations — converting, resizing, compressing, cropping, rotating, flipping and Base64 encoding/decoding — run as JavaScript and WebAssembly inside your browser tab. Your device's CPU and memory do the work; no processing server is involved at any point.
Storage
Pixitools keeps no image storage because no image is ever received. Files you load live in the page's memory until you download results or close the tab. Downloads are handled by your browser exactly like any file you save from a website.
Cookies and preferences
Pixitools sets no tracking cookies. The single preference saved is your light/dark theme choice, stored in your browser's localStorage under the key "theme". Clearing your browser storage removes it. No analytics scripts observe your images or actions.
Third-party services
The site is served as static files. Your image data is never sent to, or shared with, any third party — there is no server-side component that could forward it. Fonts are the only external resource; they contain no image data.
Offline behavior
Once the page has loaded — and the AVIF WebAssembly codec has been fetched once, where used — processing continues to work without a network connection. Disconnecting does not interrupt any running operation.
User control
You decide what happens to every file: remove images from the list at any time, clear results, or simply close the tab to discard everything in memory. Nothing persists beyond your browser session except the theme preference.
Frequently asked questions
No. There are no image uploads at all — the processing code runs in your browser and reads your files directly from your device.
No. Images exist only in your browser's memory while the page is open. Closing the tab discards everything; there is no storage and no sharing.
The app stores only your light/dark theme preference in localStorage. No analytics scripts observe your images or actions.
Yes — once the page has loaded (and the AVIF codec has been fetched once), processing continues to work without a network connection.
Open your browser's developer tools, switch to the Network tab, and use any tool. You will see no image traffic — no requests carrying your files.
See for yourself
Open your browser's developer tools, switch to the Network tab, and use any tool — you will see no image traffic. Start from the tools overview or read how it works.