Skip to content
Toolyconvert Image Resize
Menu

01Browser image resizer · v2.4

Resize an image
with exact
measurements.

Toolyconvert Image Resize is a free browser-based image resizer. Resize, crop-free scale, convert between JPEG, PNG and WebP, and compress pictures without uploading a single byte. Every pixel is resampled on your own device — no queue, no sign-up, no file size games.

0KB

bytes uploaded

20,000px

pixel max width

4

export formats

Photographic prints, a steel ruler and dividers laid out on a drafting table
Fig. 01 — resampling platesRGB · 8-bit

Resize plate

local batch processing
Awaiting files

Drop images here

Select multiple JPEG, PNG, WebP or AVIF files up to 25 MB each.

01 — Dimensions & Units
02 — Fit Mode
Scales to fit entirely within the bounds. No cropping.
Fills the bounds completely. Excess areas are cropped.
Forces the image into exact dimensions, distorting it.
03 — Output format
Retains the original image format.
Great for photos. Smaller files with some compression.
Preserves 100% quality. Best for graphics with transparency.
Modern format with excellent compression and quality.

02Introduction

What “resize an image” actually means

Resizing changes the pixel dimensions of a picture. Doing it well is a small technical decision that quietly affects page speed, print quality and how professional a product looks online.

Every digital image is a grid of pixels. A photo from a modern phone might be 4032 × 3024 pixels — roughly twelve million of them — while the space it occupies on a website is often closer to 1200 pixels wide. Sending the full-size original means transferring ten times more data than the visitor will ever see, which is why resizing is one of the highest-value optimisations in any publishing workflow.

The catch is that not all resizing is equal. Scaling an image down is a process of discarding information intelligently: the software samples neighbouring pixels and blends them into each new pixel. Done with a decent resampling filter, the result is indistinguishable from the original at its new size. Done carelessly — with a low-quality filter, an unnecessary format conversion, or an odd dimension that the display has to round off again — the result looks soft, aliased or banded.

Toolyconvert Image Resize is built around that one job. It gives you exact numeric control over width and height, an aspect-ratio lock so proportions never drift, and a choice of export formats with a quality control that maps to real encoder settings rather than an arbitrary “low / medium / high”. The processing happens in your browser, which means the tool is fast, works offline after the page loads, and never asks you to hand a personal photo to a remote server.

A resized image should look like it was always meant to be that size — not like a smaller version of something else.

03How it works

Four steps, from original to download

The interface follows the order the work happens in. Nothing is hidden behind a wizard, and every value stays editable until you press resize.

  1. 01

    Drop an image into the plate

    Drag a file onto the drop area, choose one with the file picker, or load the sample photograph to try the controls first. JPEG, PNG, WebP, GIF (first frame) and AVIF are recognised.

    Max 25 MB per file
  2. 02

    Set the target dimensions

    Type an exact width or height in pixels, drag a preset, or switch to percentage scaling. The aspect-ratio lock keeps the proportions intact whenever you change one side.

    1 – 20,000 px per side
  3. 03

    Pick the output format and quality

    Keep the original format, or convert to JPEG for photographs, PNG for graphics with transparency, and WebP when you want the smallest possible file at comparable quality.

    Quality 1 – 100
  4. 04

    Resize and download

    The canvas pipeline resamples the image with high-quality smoothing, shows you the resulting dimensions and file size, and hands the result straight to your downloads folder.

    Nothing is uploaded

Processing specification

Decoding
Canvas / createImageBitmap with colour-managed sRGB output
Resampling
High-quality bilinear with progressive half-step downscaling above 2× reductions
Encoding
Browser-native JPEG, PNG, WebP and AVIF encoders
Colour depth
8-bit per channel, sRGB
Metadata
Stripped on export (EXIF, GPS, ICC profile is re-applied as sRGB)
Network
No upload endpoint exists in the application

04Benefits

Why teams resize before they publish

Three outcomes matter more than any other: pages that load quickly, images that stay sharp, and files that fit the constraints of the platform they are headed for.

Speed you can measure

Images are consistently the largest part of an average web page. Reducing a 3.5 MB hero photograph to a 220 KB WebP at the same displayed size typically saves more load time than any script optimisation on the same page. Because Core Web Vitals — especially Largest Contentful Paint — are directly derived from how quickly the biggest visible element renders, this is one of the few optimisations that improves both user experience and search performance at the same time.

Sharpness where it counts

Counter-intuitively, making an image slightly larger than its rendered size is often worse than matching it exactly. Browsers must rescale again, and fine detail turns to mush on high-density displays. The right target is the exact pixel width of the container, with a 2× variant only for genuinely high-DPI contexts such as product galleries.

Files that fit the destination

Application stores, print bureaux, email clients and advertising platforms all impose their own dimension and file-size rules. A CV photo that must be under 200 KB, a marketplace listing that rejects images below 1000 px, an email banner that needs to stay under 60 KB — resizing with exact numeric inputs turns these constraints from a guess into a repeatable step.

Use cases we see most often

  • E-commerce catalogues — normalising supplier imagery to consistent square or 4:5 frames so the product grid never jumps.
  • Content teams — preparing hero images at 1200 × 630 for Open Graph and social cards, where the platform crops unpredictably if the ratio is wrong.
  • Real estate and travel — reducing 24 MP camera originals to web-friendly sizes without visible loss on a large display.
  • Students and researchers — fitting figures into word-processor documents or submission portals with strict size limits.
  • Support and documentation — resizing screenshots so annotation text stays legible while the file stays small enough to attach to a ticket.

05Supported formats

Choosing the right output format

Toolyconvert Image Resize reads JPEG, PNG, WebP, AVIF and the first frame of animated GIFs, and can export to JPEG, PNG, WebP or AVIF.

Format comparison

JPEG / JPG
Photographs, screenshots with no transparency — Smallest files for continuous-tone imagery. Use quality 80–92.
PNG
Logos, UI graphics, images needing transparency — Lossless — larger files, but edges stay crisp and alpha is preserved on export.
WebP
Web delivery, product imagery, hero images — Typically 25–35% smaller than JPEG at equivalent visual quality.
AVIF
Modern web projects prioritising file size — Highest compression ratio; support is strong in current browsers.

If you are unsure, start with WebP for anything destined for a website and PNG for anything containing text, flat colour or transparency that must survive further editing. JPEG remains the safest universal choice for photographs sent by email or loaded into older software.

06Privacy & security

Your images never leave the tab

“Runs in your browser” is a specific technical claim, not a slogan. Here is exactly what it means.

When you drop a file into Toolyconvert Image Resize, the browser reads it into memory using the File API. The image is decoded onto an HTML canvas, resampled, and re-encoded into a Blob. That Blob becomes a temporary object URL which your browser turns into a download. At no point in that chain is the file serialised into a network request.

The practical consequences are worth spelling out:

  • Confidential contracts, medical images, unpublished product photography and client work can be resized without creating a copy on someone else's disk.
  • There is no account, so there is no profile, no upload history and no retention policy to trust.
  • Closing or refreshing the tab permanently discards the working data — object URLs are revoked after each download.
  • The tool keeps working on an aeroplane, on a locked-down corporate network, or behind a VPN.

We still run privacy-respecting, aggregate page analytics to understand which sections are useful. Those requests contain no image data. You can read the full detail in our privacy policy and the terms of service.

07Pro tips & mistakes

Small habits, noticeably better results

Most resizing problems come from one of five avoidable decisions.

Tip

Resize after editing, not before

Sharpening, colour correction and cropping should happen at full resolution. Scaling down first and editing afterwards compounds the loss of detail.

Tip

Match the container, not the screen

Target the width the image is actually rendered at in the layout. A 2400 px image in a 640 px column wastes bandwidth and rendering time.

Tip

Keep a master copy

Resizing is destructive — the original pixels cannot be recovered from the output file. Keep the full-resolution original in your archive.

Tip

Watch the quality sweet spot

For JPEG and WebP, quality 80–92 is visually near-transparent for most photographs while being dramatically smaller than quality 100.

Tip

Beware double compression

Re-saving an already-compressed JPEG adds a second round of artefacts. Export from the original source whenever you can.

Common mistakes

  • Stretching instead of resizing. Setting width and height to unrelated values with the aspect lock off distorts the subject. Unlock the ratio only when you genuinely need a different crop shape.
  • Using dimensions the display has to round. If the layout renders at 720 CSS pixels, an 812 px source makes the browser rescale and blur the image on every paint.
  • Uploading full-size originals to a CMS. Many platforms create their own derivatives from whatever you upload; feeding them a 12 MB file slows the whole editorial pipeline down.
  • Ignoring file format when size matters. Converting a screenshot from PNG to WebP often cuts the file by 70 % with no visible difference at all.

08Troubleshooting

When something looks off

Four issues cover almost every support question we receive about browser-based resizing.

The download button does nothing

Check that the browser is not blocking downloads for the page, and that a file was actually processed — the result panel appears only after the resize completes. Private/incognito windows with strict tracking protection can block object URLs.

The resized image looks blurry

You have probably upscaled beyond the original pixel dimensions, or set a low export quality. Compare the target size with the original dimensions shown in the readout, and raise quality to 85 or above.

Transparent background turned black or white

Transparency only survives a round trip through PNG or WebP. If you convert a transparent image to JPEG, the transparent area is filled — export as PNG or WebP to keep it.

The page feels slow with very large photos

Images above roughly 40 megapixels need a lot of memory to decode. Resize such files in a desktop browser, close other memory-heavy tabs, or downscale the source first in your photo application.

09Frequently asked questions

Answers before you ask

Everything below is specific to how this tool actually behaves — not generic filler.

No. Decoding, resampling and encoding all happen inside your browser with the Canvas and Blob APIs. The page has no upload endpoint, so your images never leave the device — closing the tab discards everything.

Ready

Resize your first image in seconds.

Drop a file into the plate above, set the exact dimensions you need, and download the result. Nothing to install, nothing to sign up for.