EnlargePicture
Enlarge a picture

Enlarge many images at once

Opens on the queue: one recipe — size, method, clean-up, detail, format, density — run one picture at a time into one ZIP.

Upscaled inside this tab. The original never travels.

Many pictures, one recipe

Upscaled inside this tab. The original never travels.

The same arithmetic as the single-picture bench, run down the list one at a time. Nothing is downloaded to do it and nothing is invented — each row prints the chain it went through and the size it actually took, because a folder of mixed sizes cannot all take the same one. The archive is made in this tab, with a records.txt that says what produced each file.

or drop them anywhere on this panel
The recipe
Size

Resolved per picture. A picture the size asked would take past 8× or past this browser's canvas takes the largest size that fits, and its row says so. A picture already bigger than the size asked is kept at its own size.

Nothing chosen yet

What this opens on

The queue, empty, with the recipe above it. Choose or drop pictures and the preflight shows what will happen before anything runs.

One recipe (2×), three pictures
PictureBecomesWhy
400 × 300800 × 6002× fits
1600 × 12003200 × 24002× fits
9000 × 600010,954 × 7,3022× would pass a desktop browser's 80 MP ceiling, so it takes the largest size that fits (×1.22), and its row says so

Where this falls down

  • No models in a batch.The batch is the arithmetic path, so nothing is downloaded and nothing invented. Models run on one picture at a time in Enhance.
  • One at a time is slower.An 8× pass holds four full-size buffers; two at once is how a tab gets killed. Steady beats crashed.

Questions people ask

Is this a batch resizer?
It is the enlarging part of one. Every picture is made bigger (never smaller) by one recipe; a picture already bigger than the size asked is kept at its own size, and its row says so.
What if one picture is too large for the factor?
Each picture takes the largest size that fits this browser's canvas, and its row says it came down. One file that cannot be done never stops the queue; Retry is on its row.
How long will it take?
After the first picture the page measures this device's speed and estimates the rest. Before anything has run it does not guess.
What is in the ZIP?
Every enlarged file, named after its original with the factor or size (holiday-4x.png, then holiday-4x (2).png if two would collide), and records.txt with one block per file: source and output size, the chain, clean-up, detail, density and the exact saved bytes.
Are my pictures uploaded?
No. They are decoded, enlarged and zipped in this tab, one at a time.

Better fit?

Photographic visual for Bulk Enlarge Images
Bulk Enlarge Images