PRIVACY-FIRST / BROWSER-NATIVE COMPUTE
An image toolkit where the browser is the compute environment.
Product / architecture / frontend engineering
No upload. No processing server. No privacy theatre.
A conventional image SaaS sends the file to a server, pays to process it, stores temporary artifacts and asks the user to trust the privacy policy.
iHateImages removes the server from the path.
Web Workers move expensive processing away from the main UI thread. OffscreenCanvas and worker-side pipelines let the interface remain responsive while large files are being transformed.
WASM-based tooling fills browser gaps for formats and transformations that cannot be handled reliably with native APIs alone. Expensive capabilities are loaded only when the user asks for them.
Background removal runs locally with an ONNX model. The architecture makes the privacy promise technically true while also reducing per-job server cost.
PWA behavior and local processing mean the core utility does not depend on a round trip to an application server. The product can behave more like installed software than a normal website.
Privacy is not a checkbox when the file never had to leave in the first place.
BACK TO THE STUDIO
Selected systemsSee the rest of the work.