Preparing your workspace
Jobbit
Guides14 min read

How to Compress Images for a Website in 2026: WebP, Exact Sizes, Under 100 KB, No Blur (Squoosh, TinyPNG, ShortPixel, Jobbit)

Compress images for a website without blur in 2026: the pixel sizes Shopify, WordPress, Squarespace and Wix actually want, when to use WebP or AVIF instead of JPG, how to get every photo under 100 KB in one message to an AI agent, what it does to your Core Web Vitals, and what Squoosh, TinyPNG and ShortPixel allow for free.

How to Compress Images for a Website in 2026: WebP, Exact Sizes, Under 100 KB, No Blur (Squoosh, TinyPNG, ShortPixel, Jobbit)
Read in:

The florist's new homepage looks lovely on her laptop and takes six seconds to appear on a phone, because the hero photo is a 4.8 MB file straight from the camera and the twelve bouquet pictures below it are the same. Nobody waits six seconds. To compress images for a website is the single cheapest speed fix there is, and it is the one most small-business sites never do, because the photos were uploaded once, in a hurry, and never looked at again.

The scale of the problem is measured every year. The HTTP Archive's Web Almanac 2025 puts the median mobile home page at 2.56 MB, of which 911 KB is images, spread over about 15 pictures, and page weight grew another 8.4% in a year. Google's Core Web Vitals ask for the largest element on the screen, usually that hero image, to appear within 2.5 seconds for most visitors. This guide gives you the exact pixel sizes each platform wants, the format choice that cuts a third off every file, the order of operations that keeps photos sharp under 100 KB, and the one message that does a whole folder at once.

Attach the photos on the free image resizer page, choose "Website images under 200 KB" or "PNG or JPG to WebP", and get them back resized, converted and renamed in one zip: 100 credits a day, no card. Start at jobbit.uk.

Compress a folder of website images on Jobbit in one message

The free image resizer page takes JPG, PNG, HEIC or WebP, one file or a whole folder, and asks three things: what should happen to them (there are presets for "Website images under 200 KB", "PNG or JPG to WebP", exact sizes for social platforms, or "another size"), which output format you want, and how many files there are. It writes the message, you create a free account with an email address, and the agent sends back one zip with every image resized, converted and sensibly named, the originals left as they were, and a note on the settings it chose to meet your size limit with the least visible loss.

For a website the message is worth writing yourself once, because it teaches you the vocabulary:

text
1Here are 24 product photos for my Shopify shop. Make each one 2048 by 2048 on a white background, export a JPG under 150 KB and a WebP under 90 KB, keep the colours accurate, name them like oak-side-table-01.jpg, and give me a table of before and after sizes. Then make a 1920 by 1080 hero crop of IMG_4471 under 200 KB.

What comes back is the zip, the table, the hero crop and a line about anything that could not meet the limit without visible loss. The next message can be "write alt text for each one, naming the product and the material", "give me a 1200 by 630 image for sharing on social", or "open my site in your browser and list every image over 300 KB". None of that needs a second tool.

The right size for every image on a website in 2026

Image on your sitePixel size to uploadTarget file sizeBest formatWhy
Full-width hero or banner1920 wide (2500 for large screens)Under 200 KBWebP, JPG fallbackIt is usually the Largest Contentful Paint element
Blog or page content photo1200 to 1600 wideUnder 100 KBWebP or JPGDisplayed at 700 to 800 px, so 1600 covers retina screens
Shopify product photo2048 by 2048, squareUnder 300 KBJPG or WebPShopify's recommendation; zoom needs the pixels, speed needs the KB
Squarespace full-width section2500 on the long edgeUnder 500 KBJPG or WebPSquarespace's own guidance of 1500 to 2500 px
Squarespace product image1500 by 1500Under 300 KBJPGSquare keeps the grid tidy
WordPress featured image1600 to 2000 wideUnder 150 KBWebPWordPress scales anything over 2560 px down anyway
Thumbnail or card image600 to 800 wideUnder 40 KBWebPDozens per page add up faster than one hero
LogoSVG, or PNG 400 wideUnder 20 KBSVGSharp at every size, tiny file
IconsSVGUnder 5 KB eachSVGNever a JPG
Team headshot800 by 800Under 60 KBWebP or JPGShown small; detail is wasted
Gallery image1600 on the long edgeUnder 150 KBWebPLightbox needs size, grid needs speed
Background texture or pattern1920 wideUnder 100 KBWebP, or CSSOften removable altogether
Social sharing image (Open Graph)1200 by 630Under 300 KBJPG or PNGWhat Facebook, LinkedIn and WhatsApp show when the link is shared
Favicon512 by 512 PNG plus ICOUnder 20 KBPNG and ICOBrowser tab and bookmarks
Email newsletter image600 wideUnder 100 KBJPG or PNGEmail clients ignore WebP and block big files

Two rules sit behind every row. Upload roughly twice the displayed width so phones with sharp screens get detail, and never upload the camera original, which is 4000 to 6000 pixels wide and 3 to 8 MB. The platform makes smaller copies for phones, but it starts from what you give it, and a blurry upload stays blurry.

Step by step: under 100 KB without the blur

The order matters more than the tool. Compressing first and resizing second throws away quality twice.

  • Resize first. Set the long edge to the pixel size in the table. This alone removes 80 to 90% of the bytes in a camera photo, with no visible change, because the pixels being removed were never going to be shown.
  • Choose the format second. Photos become JPG or WebP; flat graphics, logos and anything with transparency become PNG or SVG. A photo saved as PNG is three to five times bigger for no gain.
  • Set quality between 75 and 82. Above 85 the file grows fast and the eye sees nothing; below 70 skin and sky start to band.
  • Strip the metadata. Camera make, GPS position and colour profiles add 20 to 100 KB and tell visitors where you took the picture.
  • Sharpen lightly after downscaling. Resizing softens edges; a small sharpen brings them back. The agent does this by default and says so.
  • Check on a phone, not a monitor. If it looks sharp at phone size and the file is under the target, it is done.

WebP, AVIF or JPG

The Web Almanac measured it: WebP needs about 1.3 bits per pixel for the same visual quality where JPEG needs 2.0, so a WebP is roughly a third smaller than the same JPG. AVIF comes in at about 1.4 and does best on photos with smooth gradients. Browser support is no longer the worry it was: WebP works in about 96 to 97% of browsers in 2026 and AVIF in roughly 93 to 95%, so the sensible default is WebP with a JPG fallback for the few that need it, and AVIF only if your platform serves it automatically. The surprising statistic from the same report is that only 19.7% of sites use WebP at all and 1.3% use AVIF; most of the web still ships JPEGs from 2012, which is why doing this at all puts you ahead of most competitors.

What your platform does to your images

Shopify

Shopify recommends product photos at 2048 by 2048 pixels, accepts up to 5000 by 5000 and 20 MB, and serves scaled copies through its CDN, often as WebP, without you doing anything. That hides the problem rather than fixing it: the original still has to be processed, zoom views use the big file, and a 6 MB upload becomes a slow product page on a weak signal. Upload at 2048 and under 300 KB and the CDN's copies get smaller too.

WordPress

Since version 5.3 WordPress scales any upload wider than 2560 pixels down to 2560 and uses that as the largest size; it also creates several smaller sizes per upload, which is why a media library of 400 photos becomes 2,000 files. Upload at 1600 to 2000 pixels and under 150 KB, and let a plugin such as ShortPixel convert the library to WebP if your theme does not already.

Squarespace

Squarespace asks for 1500 to 2500 pixels on the long edge and files under 500 KB, with product images square at 1500 by 1500 and under 300 KB. It builds responsive copies for phones from your upload. Larger uploads are accepted but slow the editor and the page.

Wix and the site builders

Wix, Weebly and most builders convert on delivery and resize for phones. The same rule applies: they start from your file. A 5 MB upload never becomes a crisp 80 KB image on its own; a 1600-pixel, 120 KB upload does. If your site was built by an AI agent, ask it to audit the images it used; the agent that built the page can also fix the page.

Core Web Vitals: how images decide your speed score

Google measures three things on real visits, and images drive two of them. Largest Contentful Paint is the time until the biggest thing on the screen appears, and for most small-business sites that is the hero photo; the target is 2.5 seconds or less for 75% of visitors. Cumulative Layout Shift is the page jumping as images load, which happens when an image has no width and height set. The fixes a non-developer can ask for:

  • The hero image under 200 KB, in WebP, and not lazy-loaded. Lazy loading delays the one picture that should load first.
  • Everything below the fold lazy-loaded. Thumbnails, galleries and footer logos can wait until the visitor scrolls.
  • Width and height on every image, so the browser reserves the space and nothing jumps.
  • Responsive sizes. Modern platforms do this automatically with srcset; a custom site should too, so a phone downloads the 800-pixel copy and a desktop the 1600.
  • Fewer images. The median page loads 15. If three of them are decorative, remove them.

Measure before and after with Google's PageSpeed Insights, which reports the real-visit numbers for your address once it has enough traffic, and the lab numbers immediately.

What the image tools allow for free in 2026

Squoosh is free, runs in the browser without uploading anything, and handles one image at a time with every format and a quality slider; it is the best way to learn what the settings do. TinyPNG compresses about 20 images per batch free and sells Web Pro for $39 a year for unlimited files up to 75 MB, with WebP and AVIF output. ShortPixel gives 100 free credits a month and starts at $3.99 a month for 7,000 images, mostly as a WordPress plugin that converts your library in place. Canva Pro, at £13 a month, resizes inside a design tool but is not built for bulk compression. The head-to-head, with scores and the bulk alternative, is in Image Compressors Head to Head in 2026; the general resizing guide, including social media sizes and HEIC from an iPhone, is How to Resize and Convert Images for Free.

The pattern to notice is the one from every single-purpose tool: free for one file, a subscription for a folder. An AI agent treats the folder as one job, and the subscription you would have paid for it buys nothing the agent does not already do.

How an AI agent helps, and the bigger job it can do

ChatGPT, Claude, Gemini, Microsoft Copilot, Manus and Meta's Muse all give good advice about image sizes, write alt text well, and some generate images. Where Jobbit differs is that it works on your actual files and your actual site:

  • A folder in, a zip out. Every image resized, converted to WebP with a JPG fallback, renamed and under the limit you set, with a before-and-after table.
  • Alt text for every image, written from what is in the picture and your product names, which is both an accessibility requirement and a search signal.
  • The missing sizes made. The 1200 by 630 sharing image, the favicon, the square product crop, the 1920 hero, from the same originals.
  • An audit of the live site. The agent's browser can open your page, list every image with its size and dimensions, and tell you which five are costing you the most.
  • The page fixed, not just the pictures. On Jobbit the agent builds and hosts sites, so the width and height attributes, lazy loading and responsive sizes can be applied to the page itself, with a custom domain on the Go plan at £7 a month.
  • A person when you need one. New product photography is a job for a photographer, and Jobbit can bring a UK freelancer in from the same place, with payment held in escrow until you have the photos.

Ray, 66, a retired joiner, sells garden benches from a workshop behind his house. His first site, built by a nephew, had 40 photos averaging 3 MB and took nine seconds to load on a phone. One message resized and converted the lot and wrote the alt text; the second rebuilt the gallery page with proper sizes; the third added a simple order form. The images were the smallest thing the agent fixed. How to Get a Free Website for Your Business covers the site side.

Mistakes that make website images slow or ugly

  • Uploading camera originals. 5 MB, 6000 pixels wide, GPS data included. Resize first, always.
  • Photos saved as PNG. Three to five times the size of a JPG at the same quality. PNG is for logos and transparency.
  • Stretching a small image. A 400-pixel image shown at 1200 looks like a 2005 phone photo. Go back to the original.
  • No width and height. The page jumps as each picture arrives and the layout-shift score suffers.
  • Lazy-loading the hero. The one image that should load first loads last.
  • Quality 100. Doubles the file for a difference no screen can show.
  • Forgetting retina screens. Uploading exactly the displayed width looks soft on phones; upload about twice.
  • GIF animations. A 10 MB GIF where a 400 KB WebP or a short video would do.
  • Text inside images. Invisible to search and to screen readers, and blurry on phones. Put the words on the page.
  • Missing alt text. Every image should say what it is; the agent writes it in minutes.
  • Sideways photos. Phone pictures carry a rotation flag that some platforms ignore. Ask for the rotation to be applied before upload.

A one-afternoon plan to fix every image on your site

  • Hour 1: find them. Ask the agent to open your site and list every image over 300 KB, or export your media library. Put the originals in one folder.
  • Hour 2: one message. Attach the folder on the image resizer page with the sizes from the table above and a limit per type. Check the zip on your phone.
  • Hour 3: replace and check. Upload the new files in place of the old, set the hero to load first, and run PageSpeed Insights on the home page and your best-selling product page. Keep the before and after numbers.
  • Next month: make it a habit. Every new photo goes through the same message before it goes near the site. Two minutes, not an afternoon.

Frequently asked questions

What size should images be for a website?

Upload about twice the width they are displayed at: 1920 pixels wide for a full-width hero, 1200 to 1600 for content images, 2048 by 2048 for Shopify products, 1500 to 2500 on the long edge for Squarespace, and 600 to 800 for thumbnails. Keep heroes under 200 KB and most other images under 100 KB.

How do I compress images for a website without losing quality?

Resize to the display size first, then save as WebP or JPG at quality 75 to 82, strip the metadata and sharpen lightly. Done in that order, a 4 MB camera photo becomes a 90 KB image that looks identical on a phone. Compressing before resizing, or saving at quality 100, is what causes blur and bloat.

Should I use WebP or JPG for my website?

WebP, with a JPG fallback. It is about a third smaller than JPG at the same visual quality and works in 96 to 97% of browsers in 2026. Use AVIF only if your platform serves it automatically, and keep JPG or PNG for email newsletters, which do not support WebP.

Does image size affect SEO?

Yes, through speed. Google's Core Web Vitals, which feed its page experience signals, measure how fast the largest image appears and whether the page shifts while loading. Oversized images are the most common cause of a failing Largest Contentful Paint score on small-business sites, and alt text on each image is a separate, direct signal.

How do I compress many images at once for free?

Attach the folder to an AI agent such as Jobbit and describe the sizes and limits; it returns one zip with everything resized, converted and named. Free web tools handle one image (Squoosh) or about 20 per batch (TinyPNG) and sell a subscription for more.

What is a good file size for a website image?

Under 200 KB for a hero, under 100 KB for a content image, under 40 KB for a thumbnail, and under 20 KB for a logo as SVG. A page should total well under 1 MB of images; the median page carries 911 KB, and the fast ones carry far less.

What is the fastest way to resize a whole folder for my site?

One message on the Jobbit image resizer page: attach the folder, choose "Website images under 200 KB" or give exact sizes, pick WebP, and get the zip back with a size table and alt text if you ask for it. The Free plan on Jobbit gives 100 credits a day with no card, and the same chat can fix the page the images sit on.

Related guides