Resize images for websites, forms, email and everyday uploads

Image dimensions matter separately from file size. A photo can be efficiently compressed and still be far larger in width and height than a website, application form or content layout needs. SonoFiles Image Resizer changes JPG, PNG and WebP pixel dimensions directly in your browser, with controls designed for both one-off images and mixed-size batches.

You can resize by exact pixel limits or by percentage. When aspect ratio is preserved, width and height become a maximum bounding box, so each image fits inside the requested dimensions without stretching. When you genuinely need exact dimensions, you can turn aspect-ratio preservation off.

How to resize an image

Add one or more JPG, PNG or WebP images by selecting, dropping or pasting them.
Choose Pixels for width/height control or Percentage to scale each image relative to its original size.
Keep aspect ratio on for natural proportions, and leave Do not enlarge smaller images enabled unless enlargement is intentional.
Review the projected dimensions shown beside each image, then click Resize Images.
Download one resized image or download the whole batch as a ZIP.

Pixel resizing versus percentage resizing

Method	Best for	How SonoFiles handles it
Pixels + aspect ratio	Website slots, forms, email and maximum image dimensions	The width and height form a maximum box. Each image is scaled proportionally to fit inside it.
Pixels without aspect ratio	Strict exact-dimension requirements	The output uses the exact width and height you enter. Because proportions are not preserved, the image can stretch.
Percentage	Reducing or enlarging a mixed-size batch consistently	Every image is multiplied by the same percentage relative to its own original dimensions.

Maintain aspect ratio to avoid distorted images

Aspect ratio is the relationship between an image's width and height. If a 4:3 image is forced into an unrelated exact rectangle, people and objects can appear stretched or squeezed. With Maintain aspect ratio enabled, SonoFiles calculates proportional output dimensions automatically.

For example, a 4000 × 3000 image resized inside a 1200 × 1200 box becomes 1200 × 900, not 1200 × 1200. That keeps the original shape while respecting the maximum dimensions.

Prevent accidental upscaling

Making a raster image larger does not create genuine new detail. Browsers interpolate new pixels, which can make strong enlargement look softer or blurrier. Do not enlarge smaller images is enabled by default so an image that already fits your requested size stays at its original dimensions.

If enlargement is intentional, you can turn that protection off. SonoFiles still enforces output-dimension and megapixel safety limits because very large canvases can consume substantial browser memory.

JPG, PNG and WebP output behavior

Keeping the original format is the safest general choice. JPEG works well for photographs but does not support transparency. PNG preserves transparency and uses lossless encoding, which is useful for screenshots, graphics and interface assets. WebP supports modern lossy compression and transparency and can be practical for websites.

If you explicitly choose JPEG for an image with transparent pixels, SonoFiles fills those transparent areas with white. JPEG and WebP quality can be adjusted independently from image dimensions. That quality control affects encoding; it does not change the requested width and height.

What happens to quality and metadata?

Downsizing removes pixels by definition, so no image resizer can literally preserve every original pixel. SonoFiles uses browser image smoothing and enables high-quality interpolation by default to produce a practical resized result. Enlarging can look softer because interpolated pixels cannot recover detail that was not present in the source.

Re-encoding through the browser usually removes EXIF and other embedded metadata, including camera information and GPS tags. Modern browsers normally apply EXIF orientation during decoding so phone photos remain visually upright after resizing.

Local Resizing and Image Privacy

Your selected image bytes are processed on your device for this resizing workflow. SonoFiles does not need to upload them to a remote resizing server. The browser decodes each image, draws the resized result to a local canvas, encodes the output, and creates batch ZIP downloads locally.

Limits for reliable browser resizing

A task can contain up to 100 supported images. Each file can be up to 100 MB, and the selected batch can total up to 500 MB. For better reliability on phones and lower-memory computers, 300 MB or less is recommended. Processing is sequential so the browser does not intentionally decode the entire batch into memory at once.

The hard image safety limit is 100 megapixels for both source and planned output, with a maximum width or height of 32,768 pixels. These are technical safeguards rather than paid limits. SonoFiles does not add an account requirement, watermark, daily quota or paid size unlock.

Common image resizing workflows

Website images: reduce camera-photo dimensions before publishing them in content areas that display at much smaller sizes.
Online forms: fit an image within a specific pixel box while preserving its natural proportions.
Email: reduce dimensions before attaching high-resolution photos.
Product photos: prepare a batch around a consistent maximum width and height without stretching differently shaped images.
Thumbnails: use exact dimensions when a system genuinely requires a fixed width and height.

Image Resize Problems and Output Checks

Why did my output not become the exact width and height I entered?

If Maintain aspect ratio is enabled, your values are maximum dimensions. The image is fitted proportionally inside that box. Turn the option off only when exact width and height are more important than preserving proportions.

Why did a smaller image stay unchanged?

Do not enlarge smaller images is enabled by default. This avoids unnecessary upscaling. Disable it if you intentionally want to enlarge the image.

Why is an extremely large output blocked?

Canvas memory grows with pixel dimensions, not just compressed file size. Outputs above 100 megapixels or 32,768 pixels on one side are blocked to reduce the chance of browser crashes or failed exports.

Why are GIF, SVG or HEIC not accepted?

This resizer currently focuses on static JPG, PNG and WebP for predictable browser-local raster resizing. Animated PNG (APNG) and animated WebP are rejected because browser canvas resizing would flatten them to one frame. GIF can also contain animation, SVG is vector-based, and HEIC decoding varies by browser. Treating those formats as ordinary static raster images could silently change the file's meaning.

Pixel Requirements and File-Size Requirements Are Separate

A portal may require 1200 × 1200 pixels and also set a 500 KB maximum. Resizing solves the first requirement; compression solves the second. Users often fail an upload because they meet only one rule. Read the complete specification, resize to the required geometry, then compress if necessary. For websites, choose dimensions based on the largest real display size rather than uploading a multi-megapixel source that CSS will shrink on screen.

Do Not Enlarge Prevents False Detail

Increasing dimensions cannot recreate photographic detail that is not present in the source. It only interpolates new pixels. The Do Not Enlarge option prevents a smaller source from being scaled beyond its original dimensions, which is especially important in mixed batches. The hardened logic also avoids partial enlargement in one dimension when exact width and height are requested. If enlargement is genuinely required, expect a larger file without a corresponding increase in true sharpness.

Aspect Ratio, Cropping and Distortion Are Different Decisions

Maintain Aspect Ratio prevents an image from being stretched when one dimension changes. If a destination requires a square image from a rectangular source, a pure resize cannot satisfy both exact dimensions and natural proportions without either cropping, padding or distortion. Decide which behaviour the destination expects. A general resizer should not silently crop faces or stretch logos simply to hit two numbers.

Check Output at 100% Before Using a Batch

After resizing, confirm exact pixel dimensions, output format and file size. View screenshots and images with text at 100% to check small details and edge quality. For transparent assets, make sure alpha survived the chosen format. In a mixed batch, inspect both the smallest and largest source because they reveal different problems. Test one result in the actual website or form before processing a large library.

Image Resizer frequently asked questions

Pixels or percentage?

Use exact pixels for published dimensions and percentage for proportional batch reduction.

What does Maintain Aspect Ratio do?

It prevents stretching by preserving width-to-height proportions.

Can resizing make an image sharper?

No. Enlargement cannot recreate missing source detail.

Does transparency survive?

PNG and WebP can preserve it; JPEG cannot.

What are the limits?

Up to 100 images, 100 MB each, 500 MB total plus pixel safety caps.

Does resizing keep the selected images on my device?

Yes. Resizing runs locally in the browser, so the selected image bytes stay on your device for this workflow.

Image Tools for the Next Preparation Step

Once dimensions are correct, use compression or exact-size preparation only if the destination has additional requirements.

Image Resizer

Resize images

Drop images here

Selected images

Your resized images are ready