Image Resizer
Resize images to any width and height right in your browser, lock the aspect ratio, then download as PNG or JPEG.
- Free, no account
- No watermark
- No usage limit
About the Image Resizer
This resizer changes a photo's width and height right in your browser, free, with no upload and no watermark. What sets it apart is the one thing the server-based resizers don't bother with. It strips the hidden location and camera data out of the file while it resizes, so the photo you shrink to email or post doesn't quietly carry the GPS coordinates of where you took it.
Most online resizers send your photo to a server, resize it there, and hand you back a link. It works, but your private picture just took a round trip through a stranger's machine, and it usually comes back with all its metadata still baked in. This one reads the file locally and never sends it anywhere. No upload wait, no daily quota on how many you run, and nothing of yours sitting on someone else's disk.
Drop in a JPG, PNG, GIF, WebP, or even an iPhone HEIC, set the width or height you want, and download. Queue up a whole folder and pull it all back as one ZIP. It does not work offline from a cold start, because the codec for whichever format you feed it is fetched on your first resize rather than shipped with the page.
How to use
- Choose an image by clicking the drop zone or dragging a file onto it. You can also paste one straight from the clipboard, which is handy for screenshots. JPG, PNG, GIF, WebP, AVIF, and HEIC all work as input.
- Add more if you want. Drop a batch in and the tool lines them all up to resize together, not one at a time.
- Type a width or a height in pixels. With Keep ratio on (that's the default), fill in just one and the tool works out the other so nothing gets stretched.
- Leave Keep ratio on unless you specifically want to squash or stretch the picture out of proportion. Turn it off and the two fields go independent.
- Pick an output format. PNG for anything with transparency or crisp edges, JPG for photos, WebP or AVIF when you want the smallest file. For the lossy formats a quality slider appears so you can trade sharpness against size.
- Rotate or flip if the shot came in sideways. The three transform buttons turn the image ninety degrees at a time and mirror it horizontally or vertically.
- Click Resize. You'll see each file's before and after size next to a thumbnail of the result, with a download button per image. More than one? Grab them all in a single ZIP.
The location data hiding in your photos
Every photo your phone takes carries a hidden block of data called EXIF. It's genuinely useful at first, since it records the date, the camera settings, and, if location services are on, the exact latitude and longitude where you were standing. The trouble starts the moment you share the file. Post that photo, email it, or upload it to a listing, and the coordinates travel with it. Anyone who saves the image can read where it was taken, and for most people a good chunk of their photos were taken at home.
Plenty of resizers ignore this entirely. They rewrite the pixels and pass the metadata straight through, so your image that was "resized for the web" still carries the coordinates of where you live. The server-based ones are arguably worse, because now your original file, GPS and all, sat on a machine you don't control before you ever got the resized copy back.
Because this tool rebuilds the image from its raw pixels when it resizes, the old metadata simply isn't part of the new file. Location, camera model, timestamps, all of it gone. You don't flip a switch for it, it just happens. If you've ever wanted to shrink a photo for a marketplace listing or a forum without broadcasting where you live, that's the real reason to pick a local resizer over a convenient upload-based one.
A smaller file, not just a smaller picture
There's a difference between the size of the picture (its pixel dimensions) and the size of the file (the bytes it takes up), and resizing only directly controls the first. Shrinking the dimensions usually drops the file weight a lot too, since fewer pixels means less to store. But the format you save to swings it just as hard. The same 1000 pixel image can be several times heavier as a PNG than as a WebP, because PNG keeps every pixel perfectly and a photo has an awful lot of pixels to keep.
So when your actual goal is a smaller file, and it usually is (too big to email, too heavy for a page, over some upload cap), do two things. Resize the dimensions down to what you need, then save as JPG, WebP, or AVIF and nudge the quality slider. Around 75 to 85 percent is the range where photos still look clean but the file drops sharply. AVIF squeezes the hardest of the three, WebP is nearly as good and works in more places, and JPG is the one every old system on earth still opens.
One honest limit. Resizing down is where this does its best work. Resizing up does not add detail, because the detail was never captured in the first place. Double a small image and the tool fills the gaps by guessing, which comes out soft and mushy. If you need a bigger, sharper version the fix is to dig up a higher-resolution original, not to blow up the small one. A tiny logo enlarged will always look blurry, so hunt down the vector and export it at the size you want instead.
Frequently asked questions
Are my images uploaded anywhere?
No. The resizing runs entirely on your own machine, inside the browser tab. Nothing of yours goes to a server, and there is nothing to install and no account to make. The one thing that does come down is the codec, and which one depends on what you dropped in: 166,470 bytes to read a JPG, 181,088 to read a PNG, 1,458,915 for an iPhone HEIC. That happens on your first resize, so a cold start with the Wi-Fi off stops you, and every file after the first does not.
Can I resize a bunch of photos at once?
Yes. Drop in as many as you like, set the size once, and hit Resize so the whole batch runs together. Dropping a folder rather than the files is the one place a number applies, since the tool reads it down to the first 3,000 images and then says on screen that it stopped, and the rest go through on a second drop. When there's more than one result you get a single "Download all" button that packs them into a ZIP, so you're not clicking save twenty separate times. One catch: the same width and height apply to every file in the batch, so group photos that need different targets into separate runs.
It accepted my iPhone HEIC. What did it become?
HEIC is Apple's format and plenty of websites still refuse to take it. Feed one in here, pick JPG, PNG, WebP, or AVIF as the output, and you get a resized file in something that works everywhere. It's a fast way to make an iPhone photo usable on a site that rejects HEIC outright.
Why did my resized photo come out with a white background?
You saved it as JPG. That format can't hold transparency, so any see-through area gets filled with solid white on the way out. If you need the transparency to survive, save as PNG, WebP, or AVIF instead. All three keep the clear areas clear.
What size should a profile picture or a social post be?
Profile pictures are almost always shown small and square, so anywhere from 400 by 400 up to 800 by 800 is plenty, and being square matters more than the exact number since a non-square avatar gets cropped on upload. For feed posts, 1080 pixels on the short side covers most platforms cleanly. Going far bigger just adds bytes the site throws away when it displays the image.
Does DPI or a "300 DPI" setting matter here?
Not for anything on a screen. Screens go purely by pixel count and ignore the DPI tag, so a 1000 by 1000 image looks identical whether it's tagged 72 or 300. DPI only means something in print, where it decides how many pixels a given print size needs. For web and screen use, think in pixels and forget the number.
Will resizing the same photo over and over wear it down?
A little, if you save to a lossy format each time. Every JPG or WebP save discards a bit of detail, and repeating that stacks the loss up. Keep your original, resize from it in one step to whatever you need, and you skip the problem entirely. There's no benefit to walking the size down in several small passes.