About
Careers
FAQs
Diplomas & Certificates
Awards
Gallery
Brand Design
Product Designs
WordPress Website
SEO
Hosting & Security
Website Care & Rescue
Launch
Scale
Transform
Case Studies
Portfolio
Client Stories
Curated Portfolio
Our Process
Insights
Free tool
Use this free image resizer to resize image files to any width, height or exact size, straight in your browser. Set a longest side, drive it from the width or the height, scale by a percentage, or pick a ready-made size for a link preview, an Instagram post or a YouTube thumbnail. Add as many images as you like and take them back as a ZIP.
Nothing is uploaded. Your images are read on your own device, redrawn there and handed straight back. The camera and location data in a photo does not survive the process either, so what you download carries no GPS coordinates. Need a different file type instead? Use the image converter.
JPG, PNG, WebP, GIF, AVIF or BMP. Nothing leaves your browser.
BatchNo sign up
Five steps, no account and nothing to install.
Built for our own work, free for yours. No sign-up on any of them.
Usually because something else will not accept the picture at the size the camera made it.
A job portal or a form that refuses anything over 2 MB usually just needs the picture at a sensible width rather than straight off the camera.
The same shot as a 1200×630 link preview, a 1080×1350 Instagram post and a 1080×1920 story, each cropped from the part you choose.
A 4000px photo displayed in a 600px column costs your visitors the whole 4000px. Resizing to what the layout actually uses is the single biggest win on most pages.
Drop the whole folder, set one size, and every image comes back matching so the grid does not go ragged.
Photos from a phone carry the coordinates they were taken at. Resizing writes a fresh image without them.
Set a 320px longest side and a batch of full-size images becomes a set of thumbnails in one pass.
What happens to your photo data, which size to pick, and why Fill crops.
No. They are read in the browser with the standard file API, redrawn on a canvas in your own tab and handed straight back. Nothing is sent to us, nothing is stored, and there is nothing on a server to delete afterwards. The page does send three counters: how many jobs were run, how many files were downloaded, and one per visit. Those are numbers only and carry nothing about your pictures.
Yes, and that is worth knowing either way. A photo from a phone normally carries EXIF data including the GPS coordinates it was taken at, the camera and the date. Resizing writes a completely fresh image, so none of that survives. It was checked on the real output bytes rather than assumed. If you WANT to keep that data, do not put the photo through here.
No. A photo taken in portrait is often stored landscape with a tag saying which way up it should be, and a tool that ignores that tag turns your photo on its side with no error anywhere. This reads the tag and draws the image the way it was taken. Tested with a file carrying a real orientation tag: a 200 by 100 stored image comes out 100 by 200, upright.
They only appear for an exact size, and they answer what to do when your image is not that shape. Fill gives you exactly the pixels you asked for and crops whatever does not fit, which is what a social platform expects; the nine-square grid chooses which part to keep, so a face near the top is not cut off. Fit keeps the whole image and shrinks it until it fits inside the box, so the result is usually smaller than the box in one direction. There is no letterbox option because that would need a background colour nobody chose.
Making an image smaller does not, and that is nearly always what people want. Making one BIGGER does, because the extra pixels have to be invented. That is why Do not enlarge is on by default: an image already smaller than your target is left at its own size rather than being blown up. Turn it off only if you genuinely want the larger file, and expect it to look soft.
The presets carry the current numbers, checked in September 2026 rather than remembered: a link preview is 1200×630, an Instagram feed post is now 1080×1350 because Meta prioritises 4:5 portrait over the square, a square is 1080×1080, a story or reel is 1080×1920, LinkedIn feed is 1200×1200 and a YouTube thumbnail is 3840×2160. Platforms move these, so check the current guidance if something looks wrong.
Keep leaves each image as whatever it arrived as, which is the safe default. WebP gives the smallest file at the same quality and every current browser reads it. JPG is the most compatible and the right answer if a system is fussy. PNG is lossless and the only one to use when the image has transparency, which is why the quality slider disappears when you choose it.
They are read fine, but a browser canvas cannot write those formats back out, so with Keep selected they come back as PNG and the row says so. Choose WebP or JPG explicitly if you would rather have one of those. An animated GIF loses its animation, because only the first frame is drawn.
Usually because a heavily compressed JPEG was re-encoded at a higher quality, or a photo was turned into a PNG, which is lossless and therefore large for photographic content. The row marks it so you can see it happened. Lower the quality slider, or choose WebP, and it will come down.
Set Percent to 100 and lower the quality, or switch the format to WebP, and you get the same dimensions at a smaller size. If that is all you need, the quality slider here is doing the same job a dedicated compressor would.
Free tools are a small part of what we do. The rest is websites and digital products for businesses serious about growth, whether you are launching, scaling or transforming.