GoDesign Technologies

Free generator · SEO and Visibility

Image Compressor and WebP Converter.

Runs on a canvas in your browser, so nothing leaves the tab. Cap the longest edge, convert to WebP, and see exactly how much weight came off — images are most of what makes a page slow.

Runs entirely in your browserNo signup, no email wallReviewed

Drop images here

Up to 20 at once. JPEG, PNG, WebP, AVIF, GIF or HEIC, if your browser can read it. Nothing is uploaded — the conversion runs in this tab.

Output format

WebP is smaller than JPEG at the same quality and is supported everywhere that matters.

Longest edge: 1600 px

Match the largest size the layout actually renders. A full-width hero rarely needs more than 2000.

Quality: 78

75–82 is the range where the saving is large and the difference is invisible. Below 60 it starts to show on skin and sky.

Check done

Want someone to fix what this found?

Finding a problem and fixing it are different jobs, and the second one is ours. Send the result over and you get back what it would take to put right — scoped and priced, from the person who would do the work, within one business day.

What this tool measures

Resize and re-encode images without uploading them anywhere. The conversion happens on a canvas in this page, so the files never leave your machine.

That is not a privacy slogan — there is no server on this site to upload to. It is the reason this can be pointed at a client's unreleased photography without a conversation about where the files went.

The case for doing it is boring and large. Images are most of the weight of most pages. A hero exported straight from a camera or a design tool is routinely twenty times larger than it needs to be, and the Largest Contentful Paint element — the Core Web Vital most sites fail — is usually an image.

How to use it

Drop in up to twenty images. Set the longest edge to the largest size your layout actually renders, which is almost always smaller than you think: a full-width hero rarely needs more than 2000 pixels, and a card thumbnail needs about 600.

Leave quality between 75 and 82 unless you have a reason not to. That is the range where the saving is large and the difference is invisible on a screen. Below 60 it starts to show, first on skin tones and gradients like sky.

The settings are live — changing one re-converts everything, so you can find the point where the file gets small before the picture gets worse.

How to read the result

The saving comes from two independent things, and the resize usually matters more than the quality setting. Halving the dimensions removes three quarters of the pixels; dropping quality from 90 to 78 removes perhaps a third of the bytes. If a photo is barely shrinking, check its dimensions before reaching for the quality slider.

A negative saving means the output is larger than the original. That happens when the source was already well optimised, or when the format is a poor fit — re-encoding a flat logo as JPEG produces a bigger, blurrier file than the PNG it started as.

Format follows content, not preference. WebP is right for almost everything. PNG is right for flat graphics with hard edges and for anything needing real transparency. JPEG is the fallback for a workflow that cannot accept WebP, which in 2026 is rare.

What to do next

Serve the compressed file at the dimensions it was made for, and add width and height attributes to the image tag. Without those the browser cannot reserve space and the page jumps as each image loads, which is Cumulative Layout Shift and is a separate Core Web Vital from the one you just improved.

Add loading="lazy" to everything below the fold, and leave the hero eager — lazy-loading the largest image on the screen delays the paint you were trying to speed up.

Keep the originals. This process is lossy and irreversible, and the day someone needs the print version is the day you find out.

Questions people ask

Is WebP safe to use?

Yes. Every current browser supports it, including Safari since 2020. The remaining cases where it is a problem are old email clients and some CMS uploaders that refuse the file type, neither of which is about the browser.

How large should an image on a web page be?

Under 200 KB for a hero and under 100 KB for anything else is a reasonable working target. The more useful test is the total: if a page loads more than about 1 MB of images, it will feel slow on a phone regardless of what any score says.

Does this remove EXIF data?

Yes. Redrawing through a canvas discards everything the original carried, including camera GPS coordinates. That is usually what you want on a public website — location data embedded in a property photo is a real problem — and it is worth knowing before you overwrite an original with the output.

Why is my PNG getting bigger?

Because PNG is lossless and a canvas re-encode cannot beat a well-optimised original. For photographs, choose WebP. For flat graphics that are already small, the honest answer is to leave them alone.

Where to go from here

Built by GoDesign FZE, who design and build fast sites in Dubai.

Get in touch

Want someone to just do this part?

The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.

  • You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
  • A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
  • One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
scale@godesign.ae+971 58 903 1983, WhatsApp enabled

Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan

One reply from the person who would do the work, within one business day. Your details stay with GoDesign FZE and are never sold or passed on.

Would rather type than fill in a form?

Message on WhatsApp