Image Compressor

Shrink an image's file size without leaving your browser. Pick a photo, set the quality, and download a smaller version — great for faster-loading pages. Your image never leaves 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: Smaller images are one part of a fast site; the host matters too. A fast host like Hostinger serves your pages quickly with caching and a global CDN.

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 image weight is the web's silent tax

Images are, by a wide margin, the heaviest thing most pages ship — routinely more than half of a page's total bytes. Every unnecessary kilobyte is paid for on every load, by every visitor, forever: slower first paint, worse Core Web Vitals, more data burned on mobile plans, and a measurable slice of visitors who simply leave before the page finishes. The absurd part is how avoidable it is — most images online are two to ten times heavier than they need to be at identical visible quality. This compressor removes that excess in your browser: pick a file, pick a quality, and download a lighter version. Nothing uploads, which matters when the image is a contract scan, an ID or a screenshot of something internal.

What lossy compression actually throws away

Lossy formats like JPG and WebP exploit a gap between what a file stores and what an eye perceives. They discard information human vision is bad at noticing — fine colour differences in busy textures, high-frequency detail in shadows — and keep what we're sharp at, like edges and faces. That's why a photo can lose eighty percent of its bytes and look untouched: the discarded data was perceptually redundant. It's also why compression artifacts, when you push too far, look the way they do — smudged blocks and halos around edges are the visible seams of the perceptual shortcuts. The skill isn't avoiding loss; it's staying on the invisible side of it.

Finding the sweet spot per image

There is no universally correct quality number, because content decides. Busy photographs — landscapes, crowds, texture — hide compression beautifully and often survive 65-75% untouched to the eye. Portraits and product shots with smooth gradients show banding sooner; keep them around 80-85%. Screenshots with fine text are the fussiest — small type smears early, which is why pixel-lossless PNG sometimes beats a lossy format there despite bigger files. The honest procedure: compress, then judge at the size the image will actually display — not zoomed to 300%, which is a test no visitor will ever run. If you can't see the difference at display size, the bytes you removed were pure waste.

Compression, resizing and format — use all three levers

Compression alone is leaving money on the table. File size responds to three multiplicative levers: pixel dimensions (our image resizer — halving both dimensions quarters the bytes), encoding quality (this tool), and format choice (WebP typically beats JPG by a meaningful margin at equal quality, and our resizer converts). A 4,000-pixel, 92-quality JPG hero image versus a 1,600-pixel, 80-quality WebP of the same photo is routinely a 10-20× difference — with no visible change in the layout where it actually appears. Run the levers in that order: right-size first, then convert, then tune quality; each step compounds the previous one.

The screenshots-and-documents case for local compression

Most online compressors are upload services: your file travels to their server, gets processed, comes back. For holiday photos, fine. But think about what actually gets compressed at work — screenshots of dashboards and internal tools, scans of contracts and IDs, product images under embargo. Uploading those to a third party's server, under a retention policy you've never read, is a quiet data leak dressed up as a utility. This tool's canvas-based approach means the image is decoded, recompressed and downloaded entirely inside your browser — you can load the page, go offline and compress away. For anything sensitive, local-only isn't a nicety; it's the requirement.

Where the kilobytes matter most

Some destinations punish weight more than others. Email: many gateways cap attachments around 10-25MB, and a three-photo mail that bounces is a classic; compressed images sail through. CMS and marketplaces: upload limits and slow media libraries reward lean files. Mobile-first audiences: every image is paid for over a cellular plan — in markets where data is expensive, page weight is genuinely a reach question. And web performance: Google's Core Web Vitals (particularly Largest Contentful Paint) are dominated by hero-image weight on most sites, which makes compression one of the few SEO tasks with an immediate, mechanical payoff. Same picture, faster everywhere — there's no catch to it.

Building the habit into your workflow

The difference between a fast site and a slow one is rarely knowledge — it's whether optimisation happens by default or requires remembering. Make the compressed version the only version that leaves your machine: compress right after exporting from your design tool or camera roll, before anything gets uploaded anywhere. Keep originals in your archive if you like (recompressing an already-lossy file compounds artifacts, so always work from the source), but never publish them. Teams formalise this with an asset rule — nothing over ~300KB enters the CMS without a reason — which turns a good intention into a checkable standard that survives busy weeks and new hires.

Recompression: the copy-of-a-copy trap

One failure mode deserves its own warning: compressing an image that was already heavily compressed. Lossy encoding discards information permanently, and each generation of re-encoding stacks its artifacts on the last — the digital equivalent of photocopying a photocopy. A photo that's been through three social-media downloads and two WhatsApp forwards will look visibly worse after even gentle recompression, because there's no clean signal left to preserve. The rule: always compress from the best source you have — the original export, not the version that's been around the block. And when you receive an already-tiny image that still looks poor, more compression isn't the answer; going back to whoever has the original is.

Lean images are half the speed story — where Hostinger does more

A perfectly compressed image still travels from a server to your visitor, and that half of the journey is hosting. Slow hosting squanders lean assets; good hosting multiplies them — caching, CDN delivery so files come from a server near the visitor, HTTP/2, and WordPress stacks that convert and serve modern formats automatically for every future upload. That's where Hostinger does more: fast, inexpensive hosting with those pieces built in, so the discipline you apply here shows up as real loading-speed on real connections. Compress the assets with this tool; serve them from infrastructure that respects the effort — the combination is what visitors experience as a fast site.

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.