Resize an image online
— the complete 2026 guide

How to resize an image — whether in pixels, in kilobytes, or both — without an account, without upload, without quality loss. With rules of thumb for email, WhatsApp, job applications, websites, and print.

By Jonathan Hedderich · Published: June 11, 2026 · Updated: June 21, 2026 · ~21 min read

What "resize" actually means

People who google "resize an image" rarely have a single clear goal in mind. Sometimes a photo should get "smaller" to send as an email attachment — meaning the file size. Sometimes it shouldn't appear so huge on a website — meaning the on-screen size. Sometimes a WhatsApp recipient doesn't want to pull 27 MB from their data plan — again file size is the bottleneck. Sometimes an application portal wants "max. 1024×768 pixels" — meaning the pixel dimensions exclusively.

This confusion is the source of most frustration. If you have 2400-pixel-wide hero photos and want to push the file down to 200 KB, you can achieve both — but not with a single tool you find first. Understand the problem and you pick the right tool for your case.

There are three levers that make any image smaller: the pixel dimensions (width and height in dots), the compression quality (how aggressively data is dropped), and the file format (which math sits behind the compression). Which of these levers you use depends on what you want to achieve.

Lever 1: change the pixel dimensions

The most intuitive form of resizing is scaling: the image gets fewer pixels. A 4000×3000 photo becomes a 1200×900 photo. The image information is interpolated to the new pixel density by a resampling algorithm (usually Lanczos, bicubic, or bilinear).

That's lossy, but controlled. Scaling from 4000 to 1200 pixels throws away 89% of the pixel information — but for most applications that's exactly right. Nobody views a 4000-pixel image at full resolution on an 1100-pixel browser viewport. The extra pixels are down-sampled by the browser anyway; they only cost bandwidth and storage.

Rule of thumb: always scale to double the maximum display width. Show a photo in a 600-pixel container and you need at most a 1200-pixel-wide original (retina factor 2). Anything above is wasted storage.

Which pixel dimensions for what?

You resize pixel dimensions in the JNRT Pixel resizer: drop the image, enter a new width or height, leave "lock aspect" on, download. In total that takes about twenty seconds.

Lever 2: compression quality

If the pixel dimensions already fit but the image is still too big, it's on to the quality. With lossy formats like JPG, WebP-lossy, or AVIF, the quality value determines how aggressively the encoder discards information. Lower quality value = smaller file, visibly more artifacts. Higher quality value = larger file, closer to the original.

In practice the following sweet spots crystallize:

• JPG, quality 78 — the web standard. The file gets about 60% smaller than a smartphone default JPG, the eye sees no difference.
• WebP, quality 75 — another 25–35% smaller than JPG at equal perception.
• AVIF, quality 55 — the most modern encoder, another 30–50% smaller than WebP. Browser support has been very good since 2023.

The detailed deep dive on quality sweet spots is in our post Shrinking JPG without quality loss.

Lever 3: format change

Sometimes the biggest saving lies not in the quality but in the format itself. Converting PNG to WebP saves 40–70% on a typical web graphic — without a single pixel visibly changing. Converting JPG to AVIF saves 50% on a photo — and looks identical.

There's a logical reason: PNG is specialized in graphics with few colors (logos, diagrams, pixel art). For photos it's inefficient because it stores every pixel exactly instead of using psychovisual tricks. JPG is specialized in photos. WebP and AVIF are both all-rounders with more modern algorithms that beat JPG in both disciplines.

The easiest way to find the format optimum for a specific image: load it into the multi-format comparison. It renders the same image simultaneously in JPG, PNG, WebP, and AVIF — you see the file sizes side by side and can pick the best format per image.

Use case 1: images for email / WhatsApp / job applications

Classic scenario: you want to send an attachment, but mail providers block anything over 25 MB, WhatsApp forcibly compresses photos to 1280 px, and application portals reject files over 5 MB.

Solution in three steps:

1. Scale to 1600 px width (email) or 1280 px (WhatsApp) in the resizer.
2. Compress as JPG at quality 78 in the multi-format comparison.
3. Remove EXIF in the EXIF editor, if you don't want your GPS location and camera model sent along.

Result: a 6 MB smartphone photo becomes a 250–400 KB JPG that looks sharp on any screen. Most recipients don't even notice it was resized — they only notice the email loaded faster.

Use case 2: website / blog

On a website the requirements are different. You want all at once: fast load time (Core Web Vitals), sharp images on retina displays, low data volume for mobile users, and easy maintenance in the CMS.

Optimal workflow:

1. Scale all images to double the maximum display width (typically 2200–2400 px for hero images, 1200 px for content images).
2. Convert to WebP or AVIF in the multi-format comparison.
3. Serve with srcset variants (480w, 800w, 1200w, 1800w) so the browser pulls the right variant per device.
4. Enable loading="lazy" for images below the fold, fetchpriority="high" for the hero.

Detailed best practices in the comprehensive post Compressing images for web — the 2026 guide.

Use case 3: print (A4, A3, poster)

Here the rules work in reverse. Instead of small, the image should be big enough. Rule of thumb: 300 dpi times the print size in inches. An A4 full image (21 × 29.7 cm) needs 2480 × 3508 pixels at print quality. Come with less and you risk pixelated-looking print.

Resizing in print preparation means either "crop to the target size" (see the cropper) or "embed in a PDF and reduce the compression settings on PDF export". More on the resolution math in the DPI/PPI post.

Use case 4: hit a specific file size

Sometimes a platform demands an exact maximum size: "max. 200 KB", "max. 2 MB". Here you need an iterative approach. Recommended path:

1. In the multi-format comparison, watch what the current file size looks like (shown directly under each format card).
2. If too big: first reduce quality (in steps of 5).
3. If still too big: reduce pixel dimensions.
4. If still too big: change format (JPG → WebP → AVIF).

Do this often and over time you learn to estimate the approximate file sizes. A 1200×800 JPG at quality 78 is about 80–150 KB. An 800×600 WebP at quality 75 about 40–80 KB. A 400×400 AVIF thumbnail often under 20 KB.

Common mistakes when resizing

Five typical mistakes I see from thousands of image audits:

1. Resizing twice instead of once. Scale an image first and then compress it hard again, and you stack two loss operations on top of each other. Better to set pixel dimensions AND quality at the same time in the multi-format comparison — that's just one loss operation.
2. Wrong aspect ratios. Forcing a 4:3 photo to 1920×1080 (16:9) without lock-aspect distorts the image. Always leave lock-aspect on — for a different target format, crop first, then scale.
3. Upscaling. "Resizing down" is lossy but controlled. "Enlarging" beyond the original pixels is always a bad idea — the resampling algorithm invents pixels that don't exist. If you need a bigger original: go back to the source, not to an upscaler.
4. Compressing already-compressed JPGs. Every JPG generation throws away information. Re-save the same image three times as JPG and you get visible artifacts. Better: keep the original, generate every variant from the original.
5. Forgetting EXIF metadata. A modern smartphone camera packs 100–500 KB of metadata into every image (GPS, camera model, lens, ICC profile). When resizing for web/mail, don't take any of it along — the EXIF editor deletes it in one click.

Frequently asked questions

How do I resize an image without quality loss?

Pixel scaling always involves some loss — information is interpolated. But that's no problem as long as the new pixel dimensions are still large enough for the target display. Real "quality loss" only occurs when you scale below the display resolution. Detailed discussion in the post Shrinking JPG without quality loss.

Which tools are free?

Browser-local tools like the JNRT Pixel resizer and the multi-format comparison are permanently free, no account, no file limit, and no server upload. Another free tool is Squoosh (Google), but often slower for more complex workflows.

Does it work on a smartphone?

Yes. All JNRT Pixel tools are responsive and work on iOS and Android. Performance depends on the device — a newer smartphone handles images up to about 20 megapixels without trouble. If you regularly resize large batches, you'll be faster on a desktop or laptop.

How many images can I resize at once?

The multi-format comparison processes any number of images in sequence — the only limit is your browser's memory. A batch of 50–100 images typically runs smoothly. At the end you can download them all in a ZIP.

Is my image stored?

No. All processing happens in the browser, on your device. There's no upload — you can verify it live in the browser DevTools network tab. More on this architecture in the post Optimize images online for free.

Practical summary

If you want to compress this article into four keywords:

• Pixel dimensions change → resizer, leave lock-aspect on, down to 2× display size.
• File size down → multi-format comparison, quality to 78, pick the best format per image.
• EXIF/metadata remove → EXIF editor, 100–500 KB saved per smartphone photo.
• Hit a specific file size → iteratively: quality, then pixels, then format change.

Conclusion

Resizing images in 2026 is neither complicated nor time-consuming nor expensive. A modern browser tool like JNRT Pixel does in a minute what a decade ago would have cost a dedicated image-editing workflow. Understand the three levers — pixel dimensions, quality, format — and you're well prepared for any practical situation: from the application photo through website optimization to WhatsApp sending.

Further reading: Compressing images for web — the 2026 guide, Optimize images online for free, Scaling images — a guide, Reducing image size.