Resize images online
Set a max width in pixels and you're done: aspect ratio is preserved and resampling uses high quality. Perfect for web, email and social media.
Your images
Settings
Set both for an exact pixel size; set one and the other scales to keep the ratio.
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
Useful references: 1920 px covers a Full HD screen; 1080 px is the Instagram feed standard; 1200 px works well for blogs and email. Height is calculated automatically to keep the aspect ratio.
Resizing is also the most effective way to compress: a 4000 px photo reduced to 1920 px shrinks drastically before you even touch the quality slider.
How it works
Resizing here comes down to one number: the maximum width every image has to fit.
Drop your images in
One file or a hundred — JPG, PNG, WebP, iPhone HEIC, GIF, BMP and SVG all work. On desktop, Ctrl+V pastes whatever your screenshot tool just captured.
Type the max width
The Max width box opens at 1920 px. Change it to whatever your target is: 1200 for a blog, 1080 for social, 600 for an email. Height is calculated from the original ratio, so nothing gets stretched.
Generate, then download
Click Generate images and each card shows its new pixel dimensions and file size. Save them one at a time, or take the whole batch as a .zip.
Max width is a ceiling, not a target
This page has a single resize control and it only ever shrinks. Type 1200 and a 4000 × 3000 photo comes out 1200 × 900. An 800 px image that is already under the limit passes through untouched.
Height is not yours to set. It is derived from the original aspect ratio, which is why faces and product shots keep their proportions instead of going oval. If you need an exact box — a 1080 × 1080 square, a 1200 × 630 preview card — this tool will not letterbox or stretch to fill it. Crop to that shape first, then set the width here.
The cap is measured across the width only. A tall portrait shot limited to 1080 px wide can still come out 1440 px tall, and that is correct behavior, not a bug. Output tops out at 10,000 px on the longest side.
Pixels drive file size more than the quality slider does
Weight tracks pixel count, not width. Going from 4000 px wide to 2000 px throws away three quarters of the pixels, and the file usually collapses by a similar order before the encoder is even asked to do anything.
That is why resizing beats compressing whenever an image is simply oversized for where it is going. A 12-megapixel phone photo dropped into a 700 px column is carrying an order of magnitude more pixels than that column will ever display, and every one of them is paid for on load.
The flip side: if the dimensions are already right and the file is just heavy, you are on the wrong page. Compress image is the one with the quality slider as the main control. Also worth knowing — the format here stays on Auto, and PNG output is lossless, so the quality slider does nothing for a resized PNG screenshot. Fewer pixels is the entire saving.
What a resized image actually looks like
Downscaling uses the browser's high-quality resampling, so photos come out smooth rather than stair-stepped. What you will not get is sharpening. Every resize softens fine detail a little; photographers add a touch of sharpening afterwards, and this tool deliberately does not guess that for you.
Screenshots and images with small text are the hard case. Text survives a clean halving far better than an awkward ratio like 1440 → 1000 px, where letter strokes land between pixels and go gray. If a resized screenshot looks mushy, try a width that divides the original evenly.
Use the Compare button on a card before you download. The sliding lens is the fastest way to see whether the width you picked still holds the detail you care about.
Widths worth knowing
If the image will sit in a 600 px column on a high-density display, export at 1200 px and let the page scale it down. Anything beyond double is wasted bandwidth.
- 1920 px — full-width hero on a Full HD screen; the default in the box
- 1200 px — blog body images and link preview cards
- 1080 px — social feed uploads
- 800 px — documentation and help-center screenshots
- 600 px — email newsletters, where most clients cap the body width
- 400 px — forum avatars and inline thumbnails
Frequently asked questions
Which width should I choose?
Think about display size. For the web, 1200 to 1920 covers nearly everything. For forms, 600 to 1000 is usually enough.
Is the aspect ratio kept?
Yes. Height is derived from width automatically, so the image is never stretched.
Can I enlarge a small image?
Technically yes, but we advise against it. Upscaling cannot invent detail that is not there — the result looks soft.
Does resizing reduce file size?
It does, quadratically: half the width gives roughly a quarter of the weight. It beats lowering quality alone.
Can I resize several images at once?
Yes. Every image you add gets the same maximum width and you can download them all as a .zip.
Can I make a small image bigger?
No. Max width only shrinks — typing a number larger than the original does nothing and the file passes through at its native size. There is no AI upscaler here, and stretching a small image would only hand you a larger blurry one.
Can I resize by percentage instead of pixels?
There is no percentage field. Each card shows the original dimensions, so do the math once and type the result: 50% of a 3024 px photo is 1512 px.
Does resizing change my file format?
On Auto, a JPG stays JPG and a PNG stays PNG. Four inputs get converted, because browsers cannot write those formats back out: HEIC and BMP come back as JPG, SVG and GIF as PNG. Pick a format in the panel if you want something else.
Can I give each image in the batch a different width?
No — one width applies to the whole queue. If you need two sizes, run the batch twice: 1920 first, download, clear, then set 600 and add them again.