📐 Image Resize

Resize images to any width and height in pixels. Lock aspect ratio, batch process multiple images, output as PNG or JPEG. Processed in-browser via Canvas API.

100% Free No signup Browser-only 5 languages Dark mode

🔒 About Privacy

・All processing happens entirely in your browser
・Image data is never sent to any server
・No storage logs, no upload history, no database
・No signup, no login, no payment ever

📂

Drag & drop, click to select, or paste images (multiple supported)

📖 Where people get stuck

Resize an image to a given width and height, keeping the aspect ratio and handling several files at once. Everything runs in the browser. Shrinking works well; enlarging cannot invent information — scaling past the original size produces detail that was never there, so the result either blurs or shows stepped edges. Wanting to use a small image large is a problem to solve by re-shooting the source, not by resizing.

Case	What happens	What to do
Shipping images far larger than needed	Photographs from a camera or a phone are around 4,000 px across. Drop one into a 600 px slot and the browser downloads and decodes all 4,000 px before scaling it down to draw. That wastes memory and decode time as well as bandwidth, and on a mobile connection it is usually the single largest contributor to how slow a page feels.	Cap it at twice the displayed width. A 600 px slot needs 1,200 px; beyond that there is no visible difference even on a Retina display. Serving several sizes and letting `srcset` choose is ideal, but if you are shipping one file, size it at twice the largest place it appears. Converting to WebP with the image converter takes another 20–30 % off at the same apparent quality.
The shrunken image looks soft	When the reduction is large, the default interpolation in a browser or a canvas does it in one step, averaging away the fine detail and leaving the image soft. It is most obvious going from 4,000 px to 400 px, a tenth of the size. On images containing text or a logo, thin strokes can fade to the point of being unreadable.	Reduce in stages: halving three or four times preserves far more detail than going to a tenth in one step. For images containing text, the more reliable answer is not to put text in the image at all — overlay it as HTML and it stays sharp at any resolution, can be copied, can be found by search, and gets translated. For a logo, SVG scales without any loss; the SVG optimiser will shrink the file too.
Batch resizing produced inconsistent proportions	Specifying only a width of 800 px across sources with different proportions leaves the heights all over the place, so a grid of them refuses to line up. Fixing both width and height instead stretches the images and distorts them.	Cropping and resizing are separate jobs. To make proportions match, crop to a common ratio first with the image cropper, then resize. Solving it in CSS with `aspect-ratio` and `object-fit: cover` makes mismatched sources line up inside their frames — but where the subject is off centre, a face or a product can end up outside the crop, so preparing gallery images at one ratio from the start is the reliable route.

Resizing is a one-way operation. The original resolution cannot be recovered from a shrunken file, so keep the originals somewhere separate. Being asked years later for a print version, or for a larger size, genuinely happens. The workable arrangement is to keep originals in one place and generate the published files from them every time, so that changing your mind about display sizes only means rebuilding. Most CMSes and static site generators already do this at build time.

📖 How to Use

1

Load images

Drag and drop, click to select multiple files, or paste with Ctrl+V.
2

Set width and height

Enter target size in pixels. With ratio locked, changing one dimension auto-fills the other.
3

Run resize

Click Resize Now to process every loaded image with preview.
4

Download

Download each image individually, or use Download All. Files get _resized suffix.

❓ Frequently Asked Questions

Is my image uploaded to your server?

No. All processing happens in your browser via Canvas API. You can verify in DevTools Network tab.

Will upscaling look blurry?

Yes. Upscaling uses Canvas bilinear interpolation and looks soft. This is not AI super-resolution, so we recommend it mainly for downscaling.

Can I batch process many images?

Yes. Load dozens of images at once and resize them all with the same settings. Everything runs in-browser with zero server load.

🔗 Related Tools

🐛 Found a bug or issue with this tool?

Free to use, no signup. Even just the steps to reproduce are helpful. Reports go directly to the operator and help us fix issues.