Do my images leave this device?

No. Image processing and download preparation happen in your browser. No account or image upload is required.

Which files can I process together?

Choose up to 32 static PNGs, 10 MiB each and 64 MiB combined. Source/output geometry and a conservative memory budget also apply. Animated PNGs are rejected; an invalid input can fail while valid peers finish.

What happens when no input succeeds?

The result manifest explains each failure. No PNG or ZIP download is created. Keep your originals, review the messages and try a smaller valid selection.

BROWSER-LOCAL · INTEGER SCALING

Batch PNG upscaler

Choose static PNGs, set one integer factor and download the successful results together. No account or image upload.

Choose PNG files

Or drop a selection here. Images stay on this device.

Up to 32 static PNGs, 10 MiB each and 64 MiB combined. Output dimensions and browser memory limits also apply. Animated PNGs are rejected.

Integer scale

2×4×8×

0 selected · 2×

Follow the batch PNG walkthrough for original inputs, measured exports and cancellation checks.

Repeated pixels, named results

Nearest-neighbor scaling repeats each decoded pixel into a 2×2, 4×4 or 8×8 block. It adds no detail and preserves existing blur or compression artifacts. Each successful image has its own PNG download; the ZIP includes those PNGs and the same outcome manifest shown separately.

The manifest records safe output names, source and output dimensions, geometry and every input's outcome in selection order. Duplicate names receive deterministic suffixes. Original names remain visible in the result list. PNGs do not supply animation timing, tags or engine resources.

Read partial failures before importing

A corrupt, animated or oversized input can fail while valid peers finish. Read the success/failure counts and individual messages. Zero successful inputs produce a failure manifest and no PNG/ZIP. An archive failure stops the batch; cancel or choose a smaller selection and run again.

The tool accepts up to 32 files, 10 MiB per image and 64 MiB combined. Both source and output must fit 16,777,216 pixels and 16,384 pixels per edge, with an additional conservative memory budget. Some smaller selections can still exceed that budget. It requires browser worker image-decoding and PNG-encoding support.

If a valid image exceeds the estimate, compare a smaller factor with splitting the source grid before retrying.

Transparency and browser decoding

Output PNGs support transparency. Browser canvas decoding/encoding can round partially transparent colors and discard invisible RGB or ancillary metadata; byte-identical source PNG pixels, profiles and metadata are not promised. Keep your original source files. Use the transparent-edge walkthrough to distinguish existing matte colors from a display-filtering problem.

For one image with a comparison preview or existing JPEG/WebP/GIF first-frame input, use the single-image pixel-art upscaler. A sprite sheet with accompanying JSON needs matching metadata after enlargement; this tool does not rewrite that sidecar.

? QUESTIONS

Do my images leave this device?: No. Image processing and download preparation happen in your browser. No account or image upload is required.
Which files can I process together?: Choose up to 32 static PNGs, 10 MiB each and 64 MiB combined. Source/output geometry and a conservative memory budget also apply. Animated PNGs are rejected; an invalid input can fail while valid peers finish.
What happens when no input succeeds?: The result manifest explains each failure. No PNG or ZIP download is created. Keep your originals, review the messages and try a smaller valid selection.