Resize Images Online

What Is This Tool?

An image resizer changes the pixel dimensions of an image — different from compression, which keeps dimensions but re-encodes more efficiently. Resizing is what you need when a form demands "max 800px", an avatar must be 256×256, or a 4000px camera photo is absurd overkill for a blog column that's 700px wide.

Downscaling (making images smaller) is visually lossless and dramatically reduces file size — halving both dimensions cuts pixel count by 75%. Upscaling (enlarging) is also supported but can't invent detail: a stretched image is always somewhat soft. This tool preserves aspect ratio automatically so nothing looks squashed.

Why Use It?

• Two intuitive modes: exact pixel width (for requirements) or percentage (for quick shrinking).
• Aspect ratio locked automatically — no accidentally distorted photos.
• Also converts format on the way out if you want (JPG/PNG/WebP).
• Batch resize dozens of images with per-file downloads.
• Local and private: nothing is uploaded, no size limits.

How to Use

1. Drop your images onto the box or click to choose them.
2. Pick a mode: enter a target width in pixels, or a percentage.
3. Optionally choose a different output format (default keeps the original).
4. Each result shows the new dimensions and file size — click Download.

Example

Input

camera.jpg — 4032×3024, 3.9 MB, resized to width 1200

Output

camera-1200x900.jpg — 1200×900, 260 KB

The output filename includes the new dimensions so versions never get mixed up.

Common use cases

• Meeting an exact pixel requirement from a form, app icon spec, or upload guideline ("avatar must be 400×400 or smaller").
• Shrinking a batch of camera photos before adding them to a webpage, where 4000px-wide originals load far slower than necessary.
• Preparing a set of thumbnails at a consistent size from a folder of differently-sized source images.
• Reducing an image's pixel dimensions before pasting it into a document with strict page-width limits.

Resize vs compress, and why order matters

Resizing and compressing both shrink file size but attack different things: resizing reduces the pixel count (an image made 50% narrower and shorter has 75% fewer pixels to store), while compression re-encodes the same pixels more efficiently. If an image is both oversized in dimensions and uncompressed, resizing first delivers the bigger win — cutting pixel count from 4000px down to 1200px removes far more data than any quality slider could, and then compressing the already-resized image squeezes out the remaining excess. Doing it in the other order (compress first, then resize) works too, but resizing first means the compression step has less data to work through, which is marginally faster.

Why percent mode is different from just typing a smaller pixel width

Percent mode and pixel-width mode produce the same math under the hood — both ultimately compute a target width and a proportional height — but they solve different problems in practice. Pixel mode is for when you know the exact number you need (a spec says 1200px, so you type 1200). Percent mode is for when you're shrinking a whole batch of images with different original sizes but want them all scaled down proportionally by the same amount — 50% consistently halves every image regardless of whether the originals were 2000px or 6000px wide, which pixel mode can't do in one pass across a mixed batch without either distorting some images or leaving others untouched.

Frequently Asked Questions