Resize your image

Your image is resized locally and never leaves your device.

Inputs: static JPG/JPEG/JFIF, PNG, WebP, supported 8-bit still AVIF, uncompressed BMP and restricted TIFF/TIF. Outputs: JPG, PNG and WebP only. Up to 20 MB per file and export, 16,384 px per side and 67,108,864 pixels. Images are re-encoded as raster pixels: EXIF and original metadata are not preserved; this is not a metadata sanitizer. JPG replaces transparency with white.

AVIF sequences, grids, layers, HDR, EXIF/rotation/crop features and unsupported BMP variants are refused. AVIF and BMP require compatible native browser decoding. TIFF supports one uncompressed 8-bit grayscale or RGB page (optional straight RGB alpha), up to 16,000,000 pixels. Compressed, tiled, high-bit-depth, CMYK, profiles and nested directories are refused. TIFF orientation is applied; original metadata is discarded. Untagged TIFF colors are treated as sRGB.

TIFF decoder license notices

What resizing means

Change the number of pixels in an image

Image Resizer creates a new copy at your chosen width and height. Smaller dimensions are useful for websites, email, and storage; larger dimensions add pixels but cannot restore detail missing from the original.

How to use it

Choose, size, and download

  1. Select or drop one supported image.
  2. Enter exact pixel dimensions or choose a scale percentage.
  3. Review the target size, resize, and download the new copy.
Pixels or percentage?

Pick the measurement that fits your task

Pixel dimensions are best for a precise requirement such as 1200 × 800. Percentage scaling is faster when you simply need half size, double size, or another proportional change.

Aspect ratio

Keep natural proportions

The aspect ratio lock is on by default. It keeps width and height in sync to prevent stretching. Unlock it only when a specific non-proportional size is intentional.

Output formats

JPG / JPEG

Compact output for photos. Transparent areas become white.

PNG

Lossless output that preserves supported transparency.

WebP

Efficient quality-controlled output with transparency support.

Helpful answers

Image Resizer FAQs

Can I use AVIF, BMP, JFIF or TIFF?

Yes, as input only. JFIF is JPEG. Supported AVIF files contain one 8-bit image with optional alpha; sequences, grids, layers, HDR and transformation/EXIF features are refused. BMP supports validated uncompressed core/Windows headers, palettes and standard RGB/alpha masks. Compressed, profile-bearing and ambiguous BMP variants are refused. TIFF/TIF supports a restricted single-page, uncompressed unsigned 8-bit grayscale/RGB subset with optional straight RGB alpha and orientations 1–8, up to 16,000,000 pixels. Multipage, compression, CMYK, high bit depths, profiles and nested directories are refused. AVIF/BMP need compatible native decoding. HEIC/HEIF is not supported. Output choices remain JPG, PNG and WebP.

Are animation and original metadata preserved?

No. Animated and multi-frame inputs are refused. JPEG/JFIF images are decoded with supported EXIF orientation; TIFF orientation is also applied and re-encoded as raster pixels. Original EXIF and other metadata are not preserved. Browser color handling can change profiles or colors; this is not a metadata sanitizer or a guarantee of original pixel fidelity.

Are my images uploaded?

No. Resizing happens locally in your browser, so the selected image never leaves your device.

Should I resize by pixels or percentage?

Use pixels when you need an exact width and height. Use percentage when you want a quick proportional scale, such as half size at 50%.

What does locking the aspect ratio do?

It keeps the original width-to-height relationship. Changing one dimension automatically updates the other so the image does not look stretched.

What happens to transparency?

PNG and WebP output can preserve transparent areas. JPG does not support transparency, so transparent areas are placed on a white background.

Why are very large dimensions blocked?

Extremely large canvases can exhaust browser memory or fail differently across devices. ToolNest checks source dimensions before decoding and limits source and output to 16,384 pixels per side and 67,108,864 pixels. Input and export files are limited to 20 MB. Available memory can impose a lower limit.