Short answer: Add an image below, type the width or height you need (the other follows automatically with aspect lock on), and download the resized copy. The preview and new file size update live — and the resizing happens on your device, not a server.

Drop an image here

or click to browse — JPG, PNG or WebP, up to 30 MB

Resizing vs compressing — two different jobs

Resizing changes how many pixels an image has; compressing changes how efficiently those pixels are stored. They solve different problems. Resize when the destination has a fixed slot: a profile picture at 400 × 400, a marketplace image at 2000 px on the longest side, a website hero that displays at 1200 px wide while your phone produced 4032. Serving a 4032-pixel photo into a 1200-pixel slot wastes bandwidth and load time no matter how well it is compressed afterwards.

This tool resizes with the aspect ratio locked by default, so people do not end up stretched or squashed: type one dimension and the other is calculated from the original proportions. Unlock it only when a destination demands exact dimensions and slight distortion is acceptable — or better, resize locked and crop elsewhere. Preset percentages (25%, 50%, 75%…) handle the common “make it half the size” case in one click. After resizing, the Compress Image tool is the natural second step: resize cuts the pixels, compression cuts the bytes per pixel. For marketplace sellers, our product photo guide lists the dimensions the big marketplaces actually ask for.

How to use the Resize Image tool

Resizing takes four quick steps:

  1. Add your image. Drag it onto the box or click to browse. The tool shows the original dimensions in pixels and the file size.
  2. Set the new size. Type a width or height — with “Keep aspect ratio” ticked, the other dimension fills itself in. Or pick a percentage from the Scale menu.
  3. Check the preview. The resized preview, its exact dimensions and its file size update as you type. If anything looks stretched, the aspect lock was off — tick it and re-enter one dimension.
  4. Download the resized image. The copy keeps your image's format (JPG, PNG or WebP) and is named searchpoint-resized. Your original is never modified.

The sizes people actually need

Most resize jobs come from a requirement someone else set: an application portal demanding a passport-style photo at exact pixels, a marketplace wanting images at least 1000 px on the longest side for zoom, a CMS or theme that displays a fixed width, an email or forum with dimension caps. The second big family is performance: a page showing a photo at 800 px wide should not ship the 4000 px original, a point Google's own web.dev guidance on serving correctly sized images makes in detail (linked below).

What resizing cannot do is enlarge small images into sharp big ones. Doubling the pixels interpolates — the result is bigger, not more detailed — which is why this tool's presets stop at 200% and why a tiny logo will never become a crisp banner. Start from the largest original you have, resize down for each use, and keep the untouched original as your master.

Resized in your browser, never uploaded

The resize happens on a canvas inside your browser tab. Your image is read locally, redrawn at the new dimensions by your own browser, and handed back as a download. No copy is uploaded to SearchPoint or any other server, there is no account, and the tool keeps working if you go offline after the page loads.

That matters most for the images people resize for official purposes — ID photos, certificates, personal pictures for applications. An upload-based resizer holds a copy of exactly the images you least want on a stranger's server. Here, nothing leaves the device, and closing the tab erases the working copy from memory.

Common problems and fixes

  • The image looks stretched or squashed. The aspect ratio lock was off and both dimensions were forced. Tick “Keep aspect ratio”, enter just one dimension, and let the tool calculate the other.
  • The resized image is blurry. You enlarged it, or shrank it far below the size it will be displayed at. Browsers and editors cannot invent detail — start from a larger original, and never resize below the display size.
  • The file size barely changed. Resizing cuts pixels, but a small resize (say 10%) changes little, and PNG files stay heavy at any size. Combine resizing with the Compress Image tool, or convert to JPG/WebP.
  • The destination still rejects the image. Check whether it wants exact dimensions (unlock the ratio and enter both), a minimum size (your original may be too small), or a specific format — the Image Converter handles format changes.
  • Text in the image became unreadable. Fine detail goes first when shrinking. Resize only as small as the destination truly requires, and keep screenshots as PNG so the remaining pixels stay exact.

Key takeaways

  • Resize changes pixel count; compression changes bytes per pixel. Size problems often need both, resize first.
  • Keep the aspect ratio locked unless a destination demands exact dimensions.
  • Enlarging cannot create detail — always work down from the largest original.
  • Judge the result at the size it will actually be displayed.
  • Fully local processing: no upload, no account, no stored copy.

Quick questions

What size should I resize my image to?

Match the slot it will fill: the display width of the website, the marketplace's required dimensions, or the exact pixels a form demands. If you only know one dimension, enter that with the aspect ratio locked and the tool calculates the other. When in doubt, keep the longest side at 1000-2000 px for web use — sharp on most screens without excessive weight.

Will resizing make my image blurry?

Shrinking a large image down is safe and usually looks identical at its display size. Enlarging is the risky direction: the tool can add pixels but not detail, so an enlarged image looks soft. The presets cap at 200%, and for best results always resize down from the biggest original you have.

What is the difference between resizing and compressing?

Resizing changes the number of pixels (the dimensions); compressing keeps the dimensions and stores the pixels more efficiently. A 4000-pixel photo in an 800-pixel slot needs resizing; a correctly sized photo that is still 3 MB needs compressing. Many images need both, in that order.

Is my image uploaded to a server?

No. Your browser redraws the image at the new size on a local canvas and generates the download on your device. Nothing is transmitted or stored — the tool works offline once the page has loaded.

Further reading: Serve images with correct dimensions — web.dev (Google).