What "free" means in a free image upscaler
Server GPUs cost money, so a free upscaler recovers it somewhere — in credits, a watermark, an output cap, or a sign-up.
Steps
- Find out where the cost is recovered
Look for the credit counter, the watermark, the output size cap, or the account requirement before you start. - Check the free tier at the point of download
Run one image through and go all the way to the download, since watermarks and size caps usually appear at the end. - Read what happens to the file you send
If processing happens on a server, the terms decide what may be done with the image afterwards. - Prefer tools that have no server cost to recover
Something running on your own machine has no per-image cost, which is why it can be unmetered.
A tool that runs a model on a server is paying for GPU time on every image, and it has to get that back somehow. Knowing which method it uses tells you exactly where you will hit the wall, usually at the least convenient moment — after the work is done. Open Pixmend if you would rather skip that question entirely, or read on for what to check in anything else.
The four ways "free" is paid for
| Method | Where you notice it | What to check first |
|---|---|---|
| Credits or a daily count | After a handful of images | Whether the counter is per day, per month, or once ever |
| A watermark | At the download, not on screen | Download one result before doing real work |
| An output cap | On the result, which is smaller than expected | The maximum output size, not the advertised scale |
| Your file | Nowhere visible | What the terms say about images you send |
The first three are honest business models, plainly stated by most tools that use them. The fourth is the one worth reading carefully: when processing happens on someone's server, the image is on that server, and the terms of service decide what may be done with it afterwards. For a holiday snapshot that may not matter. For unpublished artwork, a client's photo, or anything under an NDA, it is the whole question.
Check the free tier at the download, not at the preview
Most limits appear at the end of the process. The on-screen preview is clean, the watermark is applied to the file you save, and the output cap only becomes visible when you check the pixel dimensions of what you downloaded.
So before you commit an afternoon to a tool, spend two minutes on one throwaway image and go all the way through: process, download, open the file, and look at its actual dimensions. That answers more than any pricing page will.
Two more things worth checking at the same time. Whether an account is required before the download — sign-up walls are usually placed exactly there. And whether the advertised scale survives the output cap: a tool offering 8x that caps output at some maximum side is offering 8x only for small inputs.
Free without metering does exist
Some tools have no per-image cost to recover, which changes the shape of what they offer. As checked in July 2026:
| How it is free | The catch | |
|---|---|---|
| waifu2x | Free to use, illustration-focused models | Processing happens on the server, so the file has to be sent, and there is a limit on the size accepted |
| Upscayl (desktop) | Free, and processing runs locally on your own machine | It has to be installed, so it needs a machine you are allowed to install software on |
| Upscayl Cloud | 10 free credits | $24.99 a month afterwards — and if you need 8x, this is the one that has it |
| Pixmend | Runs in your browser on your own GPU, so there is no server cost to recover | Needs a WebGPU-capable browser, and the input is capped at 12.6MP |
That is a real trade-off table, not a sales pitch: if 8x is what you need, Upscayl Cloud is the answer here and nothing else in the list is. Desktop Upscayl is free and local and has been for years — installation is the only thing it asks of you.
What unlimited means here
Pixmend is 0 円: every feature, no image count, no size-based pricing, no account, and no install. That is possible for one reason only — the model runs on your own GPU inside the browser, so there is no server bill to divide up between users.
The honest limits are the ones in the table above. It needs a WebGPU-capable browser, which today means Chrome, Edge, or a recent Safari, and there is no slow fallback path for machines without it. Input is capped at 12.6MP. The first run fetches about 11.6MB of models and runtime, which is then kept on your device, after which a 1024×1024 photograph takes 7.1 seconds and an illustration of that size 3.9 seconds.
There is no watermark and nothing appears at the download stage that was not on screen — the file you save is the result you were looking at. And because the image is never sent anywhere, no terms of service apply to it: you can confirm the absence of any upload by watching the Network tab in DevTools stay silent while the work happens.
The one question that settles it
Ask where the tool's costs are, and the rest follows. A tool with server GPU bills must limit you somewhere, and the limit will be in credits, a watermark, an output cap, or the terms attached to your file. A tool with no server bill has nothing to recover, and can afford to leave the count alone.