Image Resizer
Resize images in your browser with aspect ratio control and format conversion. Files are processed locally and never uploaded.
Last reviewed by the Radiatus Cloud team
Resize Options
Need this done properly for your business?
Radiatus delivers secure cloud, DevOps & compliance engineering.
Resize to the size you actually display
The most common performance problem on a website is a 4000 pixel wide photograph displayed in a 400 pixel wide container. The browser downloads every byte and then throws most of the detail away. Resizing to roughly the displayed size, or twice it for high-density screens, routinely removes 80 to 95 percent of the file size with no visible difference.
Downscaling is safe, upscaling is not
Reducing dimensions discards information and produces a clean result. Enlarging invents pixels that were never captured, and conventional interpolation can only blur or introduce artefacts. Machine-learning upscalers hallucinate plausible detail, which is fine for a decorative image and not fine for anything where accuracy matters. Always start from the largest original you have.
Format choice
WebP is supported everywhere now and is typically 25 to 35 percent smaller than JPEG at equivalent quality, with alpha transparency. AVIF compresses better still, often half the size of JPEG, at the cost of slower encoding. JPEG remains the safe universal fallback for photographs. PNG is for images needing lossless quality or sharp-edged graphics such as screenshots and logos; using PNG for a photograph produces a file several times larger than necessary. SVG is the right answer for icons and logos, since it scales to any size from one small file.
Quality settings
JPEG and WebP quality around 80 is the usual sweet spot: the difference from 100 is invisible in normal viewing while the file is a fraction of the size. Above 90 the returns are negligible and the file grows sharply. Re-encoding an already lossy image compounds the loss, so always resize from the original rather than from a previously exported copy.
Always set width and height
Specifying intrinsic dimensions in the markup lets the browser reserve the correct space before the image loads, which prevents the layout shifting as it arrives. Cumulative Layout Shift is a Core Web Vitals metric, and unsized images are its most frequent cause.
Processed locally
Resizing uses the browser canvas. Files never leave your device, which matters for photographs containing people, documents or anything client-confidential. Note that canvas processing also strips EXIF metadata, including GPS coordinates, which is usually desirable before publishing.
Related tools
- EXIF Viewer — Extract hidden EXIF data (Camera, GPS, Settings) from images.
- Favicon Generator — Generate favicons and app icons at every required size from one source image, with the exact HTML to reference them.
- Placeholder Image Generator — Generate placeholder images at any size with custom colours and label text. Produced in your browser as downloadable files, no external hotlinking.
- Image Cropper — Crop images to any aspect ratio or exact pixel dimensions in your browser. Nothing is uploaded.
Frequently Asked Questions
Are my images uploaded to a server?
No. Resizing uses the browser canvas and files never leave your device. As a side effect, canvas processing strips EXIF metadata including GPS coordinates, which is usually what you want before publishing.
Which format should I use?
WebP for most web images, typically 25 to 35 percent smaller than JPEG with transparency support. AVIF where you can afford slower encoding. JPEG as a universal fallback for photographs, PNG only for lossless or sharp-edged graphics, SVG for icons and logos.
Can I enlarge a small image without losing quality?
Not really. Upscaling invents pixels that were never captured, so conventional methods blur and AI methods hallucinate detail. Fine for decorative use, unsuitable where accuracy matters. Always start from the largest original available.
What quality setting should I use?
Around 80 for JPEG and WebP. The difference from 100 is invisible in normal viewing while the file is far smaller. Above 90 the file grows steeply for negligible gain.
Why do my images need width and height attributes?
So the browser can reserve the correct space before the image loads. Without them the page reflows as images arrive, which is the most common cause of Cumulative Layout Shift, a Core Web Vitals metric.
Privacy & Security
Resizing happens in your browser.
About This Tool
This tool runs entirely in your browser. No data is sent to any server, ensuring complete privacy. Simply use the interface above to get started — no registration or login required.
Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.
Related Tools
EXIF Viewer
ImageExtract hidden EXIF data (Camera, GPS, Settings) from images.
Favicon Generator
ImageGenerate favicons and app icons at every required size from one source image, with the exact HTML to reference them.
Placeholder Image Generator
ImageGenerate placeholder images at any size with custom colours and label text. Produced in your browser as downloadable files, no external hotlinking.