Skip to content
GPU-assistedUpload required

Upscale an Image 2x

Double an image in width and height by running a four-times model and halving what comes back with lanczos resampling. That detour is the point: every pixel you receive is the average of four the model produced, and averaging is what removes the invented texture that makes AI upscales look artificial. Of the three upscale factors on this site, 2x is the one that lies to you least.

Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.

Add to Chrome — free

Drop an image here, or click to browse

Up to 25 MB. Uploaded temporarily, deleted after processing.

GPU-assisted — results vary slightly between runs.

What it does

  • Four times model pass reduced to two times
  • Four model pixels averaged into every output pixel
  • Artifacts suppressed rather than enlarged
  • Exactly double the source dimensions

How to use AI Upscale 2x

  1. 1

    Start here if the source is already decent

    Two times suits an image that is nearly big enough. If the source is genuinely small, the 4x page keeps more of what the model produced.

  2. 2

    Run the enlargement

    RealESRGAN enlarges four times, then a lanczos resample halves that result to land on exactly double your original dimensions.

  3. 3

    Compare against a plain resize

    Enlarge the original in any editor to the same size and put the two side by side. The difference tells you whether the model earned its time.

How it works

Two steps, and the second one is the interesting one.

RealESRGAN reads your image and enlarges it four times in each direction. This is the model's native factor — the only one it does — and the stage where new detail is reconstructed, because the network has learned what photographic texture looks like at higher resolution.

That four times result is then scaled by half using lanczos resampling, landing on exactly double your original dimensions.

Why the detour is the feature

Downscaling a generated image is called supersampling, and it is the oldest quality trick in rendering.

When four pixels become one, their differences average out. Consistent detail — a real edge, a genuine texture — survives the average because all four pixels agree about it. Inconsistent detail does not. Ringing along a hard edge, the faint checcurboard some upscalers leave behind, invented pores on skin that never had them: these are exactly the sort of high-frequency disagreement that averaging destroys.

So the model gets to be confident and the resample gets to be skeptical. What reaches you is the part both agreed on.

This is why a 2x output can look cleaner than a 4x one examined at full size, even though it came from the same model pass. It is not doing less work. It is discarding the least reliable quarter of that work.

What it costs

The whole four times enlargement is computed before anything is reduced.

That means processing time and memory are identical to the 4x page. You are not buying a cheaper job by asking for a smaller output — you are spending the same compute and using it to buy cleanliness instead of size.

Whether that is a good trade depends entirely on what happens next. For a file going into a layout at a known size, it is. For a source so small that every generated pixel matters, it is not, and the 4x page is the better page.

When double is the right number

Doubling suits images that are already close.

A photo that is slightly under a print requirement, a screenshot that needs to survive a retina display, a product shot that is fine at its current size and needs headroom for a crop — these want a modest, clean enlargement rather than the largest one available.

The failure case is the opposite: a genuinely small source, a thumbnail, a tiny avatar, an image saved at 400 pixels years ago. Doubling that gives you 800 pixels, which is usually still not enough, and you will end up running the 4x page afterwards anyway.

Judging the result

Do one comparison and it will tell you everything.

Open your original, enlarge it to the same doubled size with ordinary bicubic interpolation in any editor, and put the two files side by side at one hundred per cent. On a clean source the gap will be small. On a compressed or soft source the model's reconstruction of edges and texture will be obvious.

If you cannot see a difference, use the resize. Nothing here is worth waiting for a GPU when a filter already answered the question.

Publication gate

This page ships once the workflow has been run against a compressed phone photograph, a clean high-quality source, and a portrait with visible skin texture, with each result compared against a plain bicubic doubling at full zoom.

Examples

Phone photo for a print

holiday.jpg - 1600x1200, a compressed phone photograph
prathom-ai-upscale-2x.png - 3200x2400

The best case. Compression artifacts get enlarged four times and then averaged back down, which softens them instead of magnifying them.

Portrait with fine skin texture

portrait.jpg - 2000x3000, a close head-and-shoulders shot
portrait-2x.png - 4000x6000

Skin is where invented texture is most visible, and where halving helps most. Compare the pores against the original before accepting it.

Frequently asked questions

Why run 4x and throw half of it away?

Because the discarded half is where the model's mistakes live. RealESRGAN has one native factor and it is four, so a two times result has to come from somewhere. Downscaling the four times output means each final pixel is the average of four generated ones, and averaging suppresses invented texture, ringing, and the plasticky look that gives AI upscaling away.

Is 2x worse than 4x, then?

It is smaller, not worse. Per pixel it is arguably better, because the supersampling step cleans up artifacts that a 4x output shows at full size. The question is what you need. If a device or a layout wants double, this is the honest way to get there. If you need the largest usable file from a small source, use the 4x page.

Does it cost less than 4x since the output is smaller?

No, and it is fair to say so plainly. The model still runs at full four times before anything is reduced, so the processing time and memory are the same as the 4x page. What you save is file size and download time, not GPU work. A smaller result here does not mean a cheaper job.

Would a plain resize in my editor do the same thing?

Sometimes, and it is worth checking rather than assuming. On a clean, sharp source, ordinary bicubic doubling is close enough that the difference is hard to see. The gap opens up on compressed, soft, or noisy sources, where the model reconstructs edges that a mathematical filter can only blur. Run both and judge yours specifically.