Photo Compressor: a Free Picture and Image Compressor Built Into Chrome
Photo Compressor is a free Chrome extension that makes photos and pictures — JPEG, PNG, WEBP and GIF image files, not air tanks — weigh less, right inside the browser tab you already have open. You can install it from the Chrome Web Store in one click, and files typically come out 50-70% smaller than the originals.
The difference from a regular online image compressor is where the work happens. The panel lives inside Chrome itself, handles a whole batch at once, and does something almost nobody else offers: it can squeeze a picture down to a file size you name in kilobytes.
Install from the Chrome Web Store →
What a photo compressor actually does
A picture compressor rewrites how the pixels of an image are stored so the file takes up fewer bytes. Nothing about the picture’s dimensions changes — a 4000×3000 photo stays 4000×3000, it just stops weighing eight megabytes. That single distinction clears up most of the confusion people bring to the subject.
Compression is not the same thing as resizing
Resizing throws pixels away: a 4000-pixel-wide photo becomes 1200 pixels wide and can never come back. Compression keeps every pixel position and changes only the encoding, which is why a compressed image still prints and crops the way the original did.
In practice you often want both. Shrink a camera photo to the width your page actually displays, then compress what is left — that combination beats either step on its own, and it is the reason most “my image is still huge” problems have two causes rather than one.
Lossy and lossless, in plain words
JPEG is lossy. It leans on the discrete cosine transform that Nasir Ahmed proposed in 1972 and published with his co-authors in 1974, and it permanently discards detail your eye is unlikely to miss. The JPEG committee still maintains the standard that was formally adopted in 1992 and remains the default format for photographs almost everywhere.
PNG is lossless. The PNG specification published by the W3C uses DEFLATE, so every pixel survives byte for byte, which is exactly why PNG files shrink far less than JPEG ones. GIF sits in a third camp: LZW encoding plus a palette capped at 256 colours. WebP, described in the MDN guide to image file types, usually lands 25-35% below JPEG at the same visual quality.
Why people compress pictures at all
There are three honest reasons, and they explain nearly every visit to a tool like this one:
- an upload form, an email attachment or a marketplace listing rejects anything over a stated limit;
- a website loads slowly because its pictures were never optimised, something Google’s own image guidance treats as a ranking-relevant problem;
- a phone or a drive is simply running out of room.
Everything Photo Compressor can do
Compress to an exact file size in kilobytes. Say “fit this under 200 KB” and the extension works toward that number instead of leaving you to drag a quality slider and re-export until something sticks. Be aware of the honest limit: the algorithm lands on the closest value at or below your target, so exactly 200.0 KB is not something any compressor can promise.
A side panel instead of a popup. The interface opens in Chrome’s side panel, so it stays put while you move between tabs and collect images. A popup closes the moment you click away, which is fine for one file and painful for twelve.
Right-click any picture on the web. A “Compress Image” entry sits in the context menu on any image you see online. No download, no hunting through the Downloads folder, no drag into a second app.
Batch work that ends in one ZIP. Load a pile of pictures, watch each tile show its own percentage and a before-and-after line, then press DOWNLOAD ALL and get a single archive. You can also set your own output file name, which is a paid feature over at Compressor.io.
Dark and light themes, and 52 interface languages. Small things, but this is a tool people open several times a day. The current release is version 1.2, published by pixelpioneer, and a full feature-by-feature walkthrough lives on the features page, while the workspace page breaks the interface down screen by screen.
How to compress photos in Chrome, step by step
Nothing here needs an account, and the whole sequence takes under a minute the first time:
- Install the extension from the Chrome Web Store and pin its icon to the toolbar.
- Open the side panel from that icon.
- Add pictures one of three ways: the ADD IMAGES button, drag-and-drop from a folder, or a right-click on any image already on a web page.
- Pick a compression level, or type the target size in kilobytes you need to hit.
- Download the results one by one, or take the whole batch as a single ZIP.
The how-to-use page walks through the same five steps with a screenshot at each one, and the access page covers installation, permissions and how to remove the extension cleanly.
Formats, quality and what you actually lose
Photo Compressor handles JPEG, PNG, WEBP and GIF. Each of those behaves differently under pressure, and knowing which is which saves a lot of disappointed re-exports:
| Format | Compression type | Typical use | What to expect |
|---|---|---|---|
| JPEG | Lossy | Photographs | Largest savings, detail loss grows with strength |
| PNG | Lossless | Screenshots, flat graphics, transparency | Modest savings, pixels untouched |
| WEBP | Lossy or lossless | Web images | 25-35% smaller than JPEG at matching quality |
| GIF | Lossless, palette-based | Short animations | Limited to 256 colours, savings depend on the palette |
Being straight about it: on flat-colour PNG graphics a dedicated tool like TinyPNG will usually squeeze out more than we do. That is what it specialises in, and pretending otherwise would not help anyone.
What happens to metadata and transparency
Compression strips the housekeeping data that cameras attach to a file — EXIF fields and GPS coordinates among them. For anything you are about to publish that is a bonus rather than a loss, though it is worth knowing before you compress the only copy of a photo you wanted the shooting date on.
Transparency behaves differently depending on where the picture ends up:
- in PNG and WEBP it survives compression untouched;
- in JPEG it cannot survive at all, because the format has no transparency channel;
- a transparent background converted to JPEG therefore comes out solid white.
The technical documentation goes through this and the rest of the quality mechanics in more depth.
Free, with no limits and no account
The extension costs nothing. No subscription, no monthly quota, no sign-up, no watermark. There is a plain reason for that rather than a marketing one: the compression runs on your own processor, so there are no server costs to recover.
What that looks like next to the paid tiers of the web services is the clearest way to see it:
| Tool | Free-tier ceiling | Where files are processed |
|---|---|---|
| Photo Compressor | No quota and no cap on how many files | Locally, in Chrome |
| Adobe Express | 40 MB per file, JPEG and PNG only | Uploaded to Adobe |
| Compressor.io | 10 MB per file, some modes marked PRO ONLY | Uploaded to the service |
| FreeConvert | Queue and ads on the free tier, paid upgrade removes both | Uploaded, deleted a few hours later |
One thing we do not have: an API. If you need image optimisation wired into a build pipeline or a WordPress plugin, TinyPNG is genuinely the better answer, and the pricing page says so in more detail alongside the full cost breakdown.
Photo Compressor versus online compressors
The real difference is location, not compression strength. A web service needs your file before it can do anything with it. An extension does not, because it is already inside the browser — nothing is uploaded, nothing is queued, and nothing is stored on someone else’s disk waiting to be deleted on a schedule.
Google’s Chrome Web Store publishes what each developer declares about data handling, and ours reads plainly:
The developer has disclosed that it will not collect or use your data.
Photo Compressor listing, Chrome Web Store
The competition is genuinely good, and some of it beats us. TinyPNG is stronger on PNG specifically and ships an API, a CDN and an official WordPress plugin. Squoosh, built by Google Chrome Labs, supports AVIF and JPEG XL and is open source under Apache-2.0 — but it works on one image at a time. iLoveIMG, made by the iLovePDF team, comes bundled with two dozen neighbouring tools we simply do not have. All three have audiences orders of magnitude larger than ours.
Where we win is narrow and real. Target size in kilobytes, a side panel, right-click compression on any image on the web, batch plus ZIP, and a custom output name — that combination is not sitting in any of the tools above. The full comparison puts every limit, price and retention policy side by side, including the parts where we come off worse.
Official sources
- Photo Compressor on the Chrome Web Store — the listing, version history and data-handling declaration
- Chrome side panel API — official documentation for the panel the extension runs in
- Chrome context menus API — how the right-click “Compress Image” entry is implemented
- MDN image file type and format guide — reference on JPEG, PNG, WEBP and GIF behaviour
- W3C PNG specification — the lossless format standard
- JPEG committee — the body that maintains the JPEG standard
- Google image SEO documentation — why image weight matters for search
Frequently asked questions
More answers, grouped by topic, are collected on the FAQ page.