Nothing is uploaded, and you can check that
Every other online image resizer sends your file to a server, does the work there, and sends it back. Most keep a copy for a few hours "for processing". If the picture is a site photo, a scanned document, a payslip or anything with a person in it, that is a decision somebody made for you.
This one does the work on the page, in your browser, using the same graphics code that draws the rest of the web. The file never goes anywhere. That is not a promise you have to take on trust: open your browser's network tab, resize an image, and watch nothing happen.
It also works with the internet off. Load the page, pull the plug, and it keeps working.
No limits, because there is nothing to limit
There is no cap on how many images you can do, no maximum file size, no daily quota, no watermark and no account. Nothing to sign up for and nothing to upgrade to.
The reason those limits exist elsewhere is that server time costs money, so somebody has to meter it. Here the work happens on your own machine, which costs us nothing, so there is nothing to meter. The only ceiling is what your browser can physically draw, and where that bites the tool tells you plainly rather than dressing it up as a plan restriction.
Photos off a phone come out the right way up
A phone almost always stores its photos in landscape and adds a rotation flag to the file's metadata. Software that reads the flag shows the picture upright; software that ignores it shows it on its side.
A great many resizers ignore it. You put a portrait photo in, and a sideways one comes out, because the rotation was stored as an instruction rather than baked into the pixels. This applies the flag before doing anything else, so what you see in the preview is what you get in the file.
Shrinking is done in steps
Going from a 4000 pixel photo to 400 in one jump runs the browser's fastest, roughest filter across a ten-to-one reduction, and it throws away most of the detail while aliasing what is left. Text goes crunchy and fine lines break up.
Halving repeatedly and finishing with the last small step is dramatically sharper and takes almost no extra time. That is what happens here, automatically, whenever the reduction is big enough to be worth it.
Formats, and the transparency trap
JPEG is right for photographs. It is lossy, so quality matters: 85 is the usual sweet spot, and above about 92 the file grows quickly for a difference you cannot see. It has no transparency.
PNG is lossless and keeps transparency, which makes it right for logos, screenshots of text, and anything with flat colour and hard edges. It is a poor choice for photographs, where it will often produce a bigger file than the original.
WebP does both. It keeps transparency, compresses better than either, and is supported by every current browser. It is the best default for anything going on a website, and the wrong choice for anything going to somebody who will open it in older software.
The trap is converting a transparent PNG to JPEG. JPEG has no alpha channel, so the transparent areas have to become something, and an unfilled canvas encodes as black. Plenty of tools hand you a logo on a black square without a word. Here you pick the colour, and it defaults to white.
Which size do you need?
For a website, 1600 pixels on the longest side covers almost everything, and 1200 is plenty for an image inside a page. For email, 1200 keeps the message under the limits most mail servers apply. For print at 300dpi you need the pixels: 2480 across for A4.
Resizing by longest side rather than by width is the one that handles a mixed batch, because it treats portrait and landscape the same way instead of making all your portraits enormous.
The images stay exactly where they already are
The images stay on your machine and are discarded when you close the tab. There is no account, no sign up, nothing uploaded and nothing logged.
Common questions
Is my photo uploaded when I resize it here?
No. The resizing happens in your browser using the same graphics code that draws the rest of the web, and the file never goes anywhere. You can check this yourself in your browser’s network tab, and it keeps working even with the internet disconnected.
Why does my phone photo come out sideways after resizing?
A phone usually stores photos in landscape and adds a rotation flag to the file’s metadata rather than rotating the actual pixels. Software that ignores that flag shows the picture on its side. This tool applies the flag before doing anything else, so what you see in the preview is what comes out in the file.
Is there a limit on how many images I can resize, or a file size cap?
No. There is no cap on the number of images, no maximum file size, no daily quota, no watermark and no account. Those limits exist elsewhere because server time costs money and has to be metered; here the work happens on your own machine, so there is nothing to meter.
Should I save my images as JPEG, PNG or WebP?
JPEG suits photographs, is lossy, and has no transparency, with 85 as the usual quality sweet spot. PNG is lossless and keeps transparency, which suits logos and screenshots of text, but often produces a bigger file for a photograph. WebP does both: it keeps transparency and compresses better than either, and is the best default for a website.
Why did my logo get a black background when I converted it to JPEG?
Because JPEG has no alpha channel, so a transparent area has to become some colour, and an unfilled canvas encodes as black. Plenty of tools hand you a logo on a black square without warning. Here you pick the fill colour yourself, and it defaults to white.
What size should I resize an image to for a website?
1600 pixels on the longest side covers almost everything, and 1200 is plenty for an image sitting inside a page. Resizing by the longest side rather than by width handles a mixed batch properly, because it treats portrait and landscape photos the same way instead of making every portrait enormous.
Why does shrinking a big photo in one go make it blurry?
Going from something like 4000 pixels down to 400 in a single jump runs the browser’s fastest, roughest filter across a ten-to-one reduction, which throws away detail and makes text crunchy. Halving the image repeatedly and finishing with the last small step is dramatically sharper and takes almost no extra time, which is what this tool does automatically.