Every tool below counts the bytes it sends

AI photo tools that run on your device

Remove a background, erase an object, enlarge a small picture. Each tool runs its model in your browser, measures how many bytes left the page while it worked, and prints the number, which is zero. No account, no credits, no watermark, no expiry, because there is no server to pay for.

Remove the background

On device
Any photo
Background Remover
BRIA RMBG-1.4 runs in your browser. Cut-out on a transparent PNG, with brush erase and restore for hair and edges.
Remove background →
On device
Product shots, scans
Remove White Background
Same model, tuned for subjects on a white or near-white sweep.
Remove white →
On device
Logos
Logo Background Remover
Keeps crisp edges on flat graphics where a photo model would soften them.
Clean up a logo →
On device
Signatures
Signature Background Remover
Lifts an ink signature off paper to a transparent PNG you can place on a document.
Lift a signature →

Erase something

On device
Watermarks, stamps, labels on flat backgrounds
Magic Eraser
No model, and it says so. Tap to select by colour, fill with the background sampled around it, and read a measured verdict on whether the patch will show before you commit.
Erase something →

Make it bigger

On device
Small or soft photos, thumbnails, logos
Upscale Image 4x
Real-ESRGAN general x4 v3, 4.9 MB, tiled. Times the first tile and tells you how long the rest will take before it continues. Instant resample as the always-available fallback.
Upscale 4x →

Change the scene (the one that leaves your device)

Your key → Google
Prompt edits, new backgrounds, generated scenes
Edit a Photo with a Prompt
A model that invents a new scene cannot fit in a browser, so this page sends your photo and prompt straight to Google's Nano Banana with an API key you hold. Nothing passes through ThumbCrafted. The byte counter shows exactly what was sent.
Get a draft →

What runs where

The word "AI" on a photo site usually hides where the work happens. This table does not.

ToolWhat does the workWhere it runsLeaves your deviceDownload once
Background Remover (all four)BRIA RMBG-1.4 segmentation modelYour browser, WebAssembly or WebGPU0 bytes, measured~44 MB model, cached
Magic EraserFlood fill + median of the surrounding ringYour browser, canvas0 bytes, measuredNothing
Upscale 4xReal-ESRGAN general x4 v3 (compact SRVGG)Your browser, WebGPU where available, else CPU threads0 bytes, measured4.9 MB model, cached
Edit with a PromptGoogle Nano Banana (gemini-*-image)Google's serversPhoto + prompt + your key, to Google only, measuredNothing

Why "on your device" is the whole point

Every credit-metered AI photo site works the same way: the page is a form, the upload is the product, and the model runs on a rented GPU that the credits pay for. That is not a criticism of the model. It is a description of why those tools need accounts, quotas, expiring libraries and a reason to keep you coming back. A model that runs in your browser has none of those costs, so a tool built on one has no honest reason to add any of those frictions. It also cannot lose your photo, because it never had it.

How each page proves it

A claim on a homepage is a sentence. A number the browser keeps is evidence. When you pick a file on any on-device tool here, a small script starts counting the bytes of every outbound request the page makes, and stops when your result is ready. It prints the total next to the tool, along with what was downloaded (the model weights, once, from this site). Open your browser's developer tools on the Network tab while it runs and you will see the same thing. The one page that does send your photo somewhere, Edit with a Prompt, runs the same counter, and its number is not zero, which is the point of running it there too.

What is honest about the limits

Small models have small limits. The background remover is very good on a clear subject and struggles with wire fences. The upscaler rebuilds plausible texture and cannot make illegible text legible. The magic eraser is not a model at all, and tells you before you commit whether a flat fill will show. None of these pages calls itself something it is not; the upscaler even times its first tile and tells you how long the rest will take on your hardware before it continues.

Common questions

Is my photo uploaded when I use these AI tools?
Not by the on-device tools. The background remover, magic eraser and upscaler run a model in your browser, and each page counts the bytes it sends to any server while it works and shows the total, which is zero. The one exception, Edit with a Prompt, sends your photo to Google with an API key you supply, and is labelled in amber on every surface.
Is ThumbCrafted an AI image generator?
No. The on-device tools edit the photo you give them; they do not invent new scenes. Prompt-based generation needs a model far larger than a browser can hold, which is why that one tool uses your own Google key instead of pretending to run locally.
Why is there no signup, credits or watermark?
Because processing on your device costs ThumbCrafted nothing per use, there is nothing to meter. Credit systems exist to pay for server GPUs; a tool that does not use one has no honest reason to charge for it.
Which model does each tool use?
Background removal uses BRIA RMBG-1.4 (about 44 MB, downloaded once). Upscaling uses Real-ESRGAN general x4 v3 (4.9 MB). The magic eraser uses no model at all, a flood fill and a median, and says so. Edit with a Prompt uses Google's Nano Banana models through your key.