Resize an image to exact pixels on your computer, not in an upload box

Forms mix two jobs and write them as one sentence: “photo, 600×600, under 1 MB.” Pixels and kilobytes are different tools. Stretching a picture does not always make it smaller on disk. Compressing does not make it 600 pixels wide.

Resize image on Tool Hub changes width and height in your browser. You pick the file on your computer. We do not receive it.

When resize is the right tool

Use this page when the destination names pixel dimensions (or a max width). Typical jobs: an avatar box; a listing thumbnail; a print template that wants 1200 px on the long edge.

This is not compress. After you have the pixels right, use Compress JPEG if the file is still too heavy. Do them in that order: resize, then compress, then look at the preview. This is not a format converter. HEIC still needs HEIC to JPG first on many Windows machines.

I resize when the crop is already right and I only need the box to match. I crop in an editor I already have if the subject is a face in the corner — stretching a 100 px icon to 2000 px does not add detail. It adds mush.

What “in the browser” means

Code runs in the tab. The File API reads the image. The tab draws a new bitmap. Download is local. Airplane mode after load is a fair test.

How I resize here

1. Open https://tools.sw-commercial.com/resize-image.
2. Pick the file (JPG, PNG, or WebP the hub accepts).
3. Set width, height, or a lock-aspect control if you have one. Read the form twice. “Max 600 px” is not “exactly 600×600.”
4. Check the preview. Faces and type show interpolation first.
5. Download. If the portal also caps megabytes, compress next. If it wants JPG and you have PNG, convert as a separate step.

No account. No watermark.

Failure cases

Locking the wrong side: you set width 600 and the height becomes 4000 because the source is a panorama. The form then rejects height. Crop first.

Upscaling a screenshot of a QR code until the modules blur. Generate a new QR at the size you need instead.

A Live Photo HEIC. Convert the still first.

When not to use this page

Do not resize as a substitute for EXIF stripping. Changing pixels may or may not drop GPS depending on the encoder path. If location is the worry, run EXIF remover on the file you attach.

Do not use an upload “social size” site that stores every crop you try. The size chart is not consent.

Do not print a heavily upscaled still and expect a sharp poster. Start from a larger original.

Related jobs

JPG to PDF if the portal wants a page, not a photo. PNG to JPG if it names JPEG. SW Toolbox resizes from a right-click, still on the device.

The live URL is tools.sw-commercial.com/resize-image. This page is the how-to for that path.

A worked example

An avatar form wants 400×400. My photo is 4032×3024. I crop the face in an editor I already have, then resize. A naive 400×400 on a landscape shot squashes heads. The hub is a scaler, not a portrait photographer.

If the form also wants under 200 KB, I resize first, then compress JPEG. If I compress first, I throw away detail and then interpolate mush. Order matters. I keep the original 4032 px file in a folder named originals.

“Max 600 px” usually means the longest side, not both sides 600. I read the help text twice. When it is ambiguous I output 600 on the long edge and mention the pixel size in the email so a clerk can reject it once, clearly.

FAQ

Does resize make the file smaller on disk? Not always. That is compress. Should I upscale a 100 px icon to print size? No. You get mush. Does changing size strip GPS? Do not assume it. Run EXIF remover on the file you attach if location is the worry. HEIC on Windows: convert the still first.

How I test that the bytes stayed local

I load the Tool Hub page, wait until it is usable, then disconnect the network (airplane mode, or unplug after the JavaScript is cached). I repeat the job with a throwaway file or a throwaway paste. If the result still appears, that step did not need SW Commercial’s servers. The first visit still has to download the page itself. That is HTML, CSS, JavaScript, and sometimes a codec. It is not the document I care about.

Browser developer tools also show it. A converter that posts a multipart file to /api/upload is an upload converter. These Tool Hub jobs are not built that way. Ads, if shown, are labeled and do not receive the file. The SW Toolbox extension has 0 ads if you prefer that surface for the same engines.

I would rather keep one extra paragraph in a how-to than send a reviewer to a tool that 404s. The resize-image URL returned HTTP 200 when this guide was written.