Image Resizer & WebP Converter

Resize any image to exact dimensions, convert it to WebP (or JPG/PNG) and pick the quality — all on a canvas in your browser, so your photos never leave your device.

Free vs paid — when to upgrade

What this free tool is great for: a quick, one-off job with no signup — it runs entirely in your browser, so nothing leaves your device and there's nothing to manage.

Its honest limit: it's a quick one-off in your browser — it won't save, track, automate or scale what you do with it.

Where Hostinger does more: Optimised images are half the speed win; the other half is hosting that serves them fast. Hostinger bundles caching, CDN delivery and WordPress stacks that auto-serve WebP for every upload.

Try Hostinger →

Affiliate link — we may earn a commission if you sign up, at no cost to you. It never changes our honest take.

Why every image needs resizing before it goes online

Cameras and phones produce images measured in thousands of pixels and multiple megabytes — wonderful for prints, absurd for the web. A 4,000-pixel photo squeezed into a 400-pixel blog column still ships all four thousand pixels to every visitor, on every load, on every connection. Oversized images are consistently the number-one reason pages are slow, and slow pages lose visitors and rankings alike. This resizer fixes the mismatch at the source: pick the dimensions the page actually displays, choose a modern format, and download a file that's often a tenth of the original size with no visible difference. All of it happens on a canvas in your browser — the image never leaves your device, which matters more than people think for photos of documents, screenshots and anything personal.

Resize, compress, convert — three different levers

People use the words interchangeably, but they're separate operations with separate payoffs. Resizing changes the pixel dimensions — the biggest lever by far, because file size scales roughly with pixel count: halving both dimensions quarters the data. Compression keeps dimensions but encodes more efficiently at some quality cost — our image compressor specialises in that. Converting changes the container format, and modern formats simply encode smarter. This tool does all three in one pass: scale to target dimensions, encode at your chosen quality, output in the format you pick. For a typical hero photo, resize contributes most of the saving, format second, quality third.

WebP: the default answer in 2026

WebP earned its place as the web's workhorse format: at comparable visual quality it produces meaningfully smaller files than JPG for photos and supports transparency like PNG — covering both classic use cases in one format. Browser support has been effectively universal for years, so the old ritual of shipping JPG fallbacks is largely history for ordinary sites. That's why this tool defaults to WebP output. The honest footnote: even newer formats like AVIF compress further still, but encoding support in the browser's canvas API remains inconsistent — so WebP is the pragmatic sweet spot between savings and works-everywhere, and converting your existing JPGs and PNGs to WebP is the single easiest bulk win most sites haven't taken yet.

Choosing dimensions like you mean it

The right size is the largest size the image will actually display, times the device-pixel ratio of the screens you care about. In practice: a full-width blog image rarely needs more than 1,600 pixels wide; a content-column image 1,200; a card thumbnail 600; an avatar 200. Retina screens double the useful density, which those numbers already accommodate for typical layouts. When in doubt, inspect the rendered size in your browser's dev tools and double it. And keep the aspect ratio locked — this tool auto-calculates the other dimension as you type — because stretching an image to fit a slot is the one resize operation that always looks wrong.

The quality slider without superstition

Lossy quality settings confuse people into extremes: 100% "to be safe" (nearly double the bytes for invisible gains) or 40% "for speed" (visible mush). The useful range is narrow: around 80% is the everyday sweet spot where artifacts stay invisible in normal viewing; 90%+ is for photography portfolios where every gradient matters; 65% works for busy images viewed small. Two habits beat any fixed number: compare the result at the size it will actually display rather than zoomed to 300%, and let the output size be your referee — if dropping from 92 to 80 saves forty percent and you can't see the difference, the bytes were doing nothing.

JPG's white-background gotcha and other format edges

Format conversion has a few sharp edges worth knowing. JPG doesn't support transparency, so converting a transparent PNG logo to JPG fills the background — this tool fills white deliberately rather than leaving black, but the real answer is to keep transparency in WebP or PNG. PNG remains right for two niches: images that must be pixel-perfect losslessly (UI screenshots with fine text) and maximum-compatibility transparency. Upscaling deserves its own warning: a resizer can make an image's dimensions larger, but it cannot invent detail — an enlarged small image is a blurry large image. Resize down freely; resize up only when you accept the softness or genuinely need the canvas size.

Filenames, alt text and the SEO you get for free

While you're producing properly-sized images, collect the adjacent wins. Name files descriptively before uploading — team-photo-amsterdam-2026.webp beats IMG_4823.webp for image search and for your own sanity in the media library. Fill in alt text when you place the image: it's accessibility first, image-SEO second, and it takes ten seconds. And prefer dimensions consistent with your layout so the browser can reserve space and avoid layout shift — one of the Core Web Vitals your rankings quietly depend on. None of this requires tooling beyond what you're doing right now; it's the discipline that separates sites that feel fast from sites that merely have fast servers.

Screenshots deserve the same treatment

The most-shared images in business aren't photos — they're screenshots, and they're routinely enormous. A full-screen capture on a modern display is easily 3,000+ pixels wide and lands in documentation, tickets and blog posts at native size, weighing megabytes to show a dialog box that displays 600 pixels wide. The fix is the same pipeline: crop to the relevant region first (your OS screenshot tool does this), then resize here to roughly the display width, and export. One nuance: screenshots with fine text sit at the boundary between formats — WebP at high quality handles them well, but if you see smudging around small text, PNG keeps it lossless at a size penalty. Your documentation loads faster and reads sharper, and readers on mobile connections will quietly thank you.

One image at a time is fine — where Hostinger does more

This tool is perfect for the steady trickle: today's blog hero, a product shot, the occasional batch of a dozen. If you're optimising an entire existing site, the bottleneck shifts from converting images to serving them — and that's an infrastructure job. Modern hosting like Hostinger bundles the server-side half: built-in caching and CDN delivery, HTTP/2, and WordPress stacks where plugins convert and serve WebP automatically for every upload, past and future. Resize your images right with this tool; put them on hosting that serves them fast worldwide — because a perfectly optimised image on a slow host is only half the win.

Frequently asked questions

More free pdf & files

Browse all free tools →

Embed this tool on your site

Blogger, teacher or toolmaker? Put this calculator on your own page — free forever, no strings. Copy the snippet below (the credit link is appreciated and keeps the tool free):

This tool is free and runs entirely in your browser. The link above is an affiliate link: we may earn a commission if you sign up, at no extra cost to you, and it never changes our honest take.