Why Pixelify exists
Most online image tools work the same way: you hand your photo to a server, wait for someone else's GPU to process it, and hope the fine print is acceptable. That model has three costs. A privacy cost, because private photos leave your device. A latency and friction cost, because uploads are slow and queues get long. And a pricing cost, because somebody has to pay for all that compute, usually you, per credit.
The last few years removed the reason for that trade-off. Super-resolution and segmentation models got small enough, and browsers got fast enough, that the same class of network that used to need a data-center GPU now runs in a normal laptop tab. Pixelify exists to ship that: the tools, in your browser, with the server removed from the equation entirely.
What it does
Pixelify currently ships two tools and a publication:
- AI Image Upscaler: enlarge images 2×, 4× or 8× with three neural models (Vitality, Pixel-Dance, Alpha-Satoru), presets for portraits, art and landscapes, and optional denoise, sharpen, face restoration, colour and HDR passes. Export as PNG, WebP or JPEG.
- Background Remover: one-click neural cutouts using the Chopper segmentation model, with hair- and fur-level edge precision, erase/restore brushes, background replacement, and transparent PNG or WebP export.
- Blog & Guides: long-form articles on local AI, privacy, and how the models in this site actually work, published in several languages.
Both tools are free to use, with no credits, no daily caps and no watermark on the output. See the products page for full specifications.
How it works
Pixelify is a static web application. There is no Pixelify backend: no API you call, no queue your job joins, no database holding your images. When you open the page, your browser downloads the application code and the neural model files (once; they are then cached by your browser). Inference runs on your own hardware:
- WebGPU is used when your browser exposes it (Chrome, Edge, and Safari 17+ over HTTPS). Models execute directly on your GPU.
- WebAssembly (WASM SIMD) is the automatic fallback everywhere else, including Firefox and on mobile, where it keeps things slow-but-stable.
- The background remover runs inside a Web Worker, so model download and segmentation never freeze the interface.
Your image is read from disk into memory, processed as pixel tensors on your GPU or CPU, and handed back as a canvas you can preview and download. At no point does it become a network payload.
Our privacy stance
Privacy here is a property of the architecture, not a promise in a policy. We cannot leak, sell, or lose image data we never receive. There are no accounts, session replay, advertising pixels, or first-party cookies on this site. A cookieless external counter records aggregate site visits; it does not receive images or tool usage. Your theme and sound preferences stay in your own browser's local storage. The site is supported by Google AdSense ads on content pages. AdSense sets its own cookies (Google's cookies, not ours), and the ad code never touches the AI tools: your images are still never uploaded anywhere.
For completeness: your browser does make a few ordinary requests to load the site: the application itself, the model files, fonts, open-source libraries, and an aggregate site visit count. None of those requests contain your images. The full breakdown is in our Privacy Policy, written to be checkable against the code rather than taken on faith.
Being honest about AI
Super-resolution models do not recover detail that was never captured; they reconstruct plausible detail. On faces, textures and artwork this lands very close to truth. On fine text, dense patterns and small logos it can invent plausible-but-wrong shapes. Background removal can occasionally clip a stray strand of hair or misread a transparent object.
We think tools are better when they say this out loud. Every result is a reconstruction, so check the before/after at 100% before you rely on an output for print or publication, and treat restored faces and reconstructed documents accordingly. Our blog goes deeper on where each model is reliable and where it drifts.
Who it is for
Anyone who has hesitated before uploading a photo to an editing site. Photographers cleaning up client shots under NDA. Sellers who batch-process product listings. People restoring old family photos they would rather not share with a stranger's server. Developers and designers who want a fast local workflow. If your images are ordinary, Pixelify is simply the faster option; if your images are sensitive, it is the only one of the two that is safe by construction.
Contact
Pixelify is run by a small team and lives on GitHub. The most reliable way to reach us, whether for bugs, privacy questions or data requests, is to open an issue:
Get in touch
github.com/yash5800/pixelify. Open an issue for bug reports, feature requests, or anything privacy-related. We read every one.
You can also start with the products overview, read the Privacy Policy and Terms of Service, or jump straight into the blog.