PixelEditor
Fourteen single-purpose tools for resizing, cropping, compressing and converting
About
Privacy-First Image Tools Fourteen single-purpose tools for resizing, cropping, compressing, converting and cleaning images — each one doing its work inside your browser, with no upload step before you can use it. What happens when you pick a file A normal image tool asks you to upload a file, does the work on a server, and sends a result back. PixelEditor skips the middle part. The browser already contains a complete image decoder and encoder, so the file can be read from your disk, worked on in memory, and handed back as a download without ever being put on the network. 1 You choose a file. Drag it onto the drop area or use the file button. The browser gives the page a reference to the file on your disk — not a copy on a server. 2 The browser decodes it. createImageBitmap turns the compressed bytes into pixels in memory. The first bytes are also sniffed, so the real format is known even when the extension lies. 3 A Web Worker does the work. Resizing, cropping, rotating and encoding run on a background thread, which is why the page keeps responding while a large photo is processed. 4 You see the real numbers. Output dimensions and byte size come from the finished file, not from an estimate, so the before-and-after figures are the ones you will actually download. 5 You download the result. The finished bytes are handed to the browser as a normal download. Batch runs are packed into a ZIP in the tab first. Closing the tab discards everything.
Data Handling
What “in your browser” actually means here It means the image processing happens on your device. When you pick a file, it is read into the tab’s memory and handled there; no upload request is made in order to resize, crop, compress, convert or clean it. There is no processing server to receive it, no storage bucket, and no job queue. The site itself sets no cookies, loads no analytics, and requests nothing from a third party — the fonts are served from this domain rather than from a font CDN. Your images are never written to local storage or to a cache; they exist in memory while the tab is open and are gone when you close it. What we will not claim: that this is “100% private” or “zero data collection”. Loading any web page means your browser contacts the server that hosts it, and that server — like every web host — can log the request, which normally includes an IP address, a timestamp and a user-agent string. That log is about the page request, not about your pictures. The Privacy Policy sets out exactly what that covers.