Sukat · 200 KB

Compress an image to an exact 200 KB

200 KB is the web-performance sweet spot — large enough for retina-sharp blog images, small enough to keep LCP under 2.5 seconds on average mobile. It’s the size most front-end developers target by default for hero photos, featured images, and product thumbnails. Tell Sukat the limit; the algorithm picks the highest quality that fits. All in your browser, no upload.

Compress to 200 KB now →
Last reviewed: May 2026
A 4 MB image reduced to fit under a 200 KB limit, with an LCP-friendly page-speed callout Animation: you set a 200 KB limit; the file size counts down through a binary search from 4 MB and lands at 198 KB, under the limit. A side callout flags 200 KB as the LCP-friendly page-speed sweet spot. YOUR LIMIT 200 KB CORE WEB VITALS LCP-friendly · page-speed sweet spot CURRENT FILE SIZE 4.0 MB 1.18 MB 412 KB 280 KB 198 KB binary search · ~7 re-encodes, highest quality that fits DONE198 KB — under your limit
How to

Compress an image to 200 KB

Three steps. The algorithm does the searching; you just state the limit.

Upload your image

Drop a JPG, PNG, WebP, HEIC, AVIF, or GIF onto Sukat’s drop zone. iPhone HEIC works directly — no separate convert step needed.

Set 200 KB as the limit

Type 200 in the Maximum File Size field and pick KB. Choose WebP for the web (smallest, recommended), JPEG for older CMSes or platforms that require JPG.

Convert and download

Click Convert & Download. Sukat binary-searches for the highest quality that fits under 200 KB and saves the file locally.

When you need it

When a 200 KB image matters

200 KB is the modern web’s default thumbnail size — large enough to look professional on retina displays, small enough to keep your Core Web Vitals green.

  • Blog hero images. The opening image on a long-form post almost always becomes the page’s LCP element. Keeping it under 200 KB is the cleanest way to keep LCP under 2.5 seconds on mobile.
  • WordPress featured images. The platform’s own performance guidance recommends staying under 200 KB for hero thumbnails — anything heavier shows up in Site Health warnings.
  • Substack newsletter images. Substack renders post covers at roughly 1500 px wide and benefits from images in the 150–250 KB range — sharp in the email client, light enough that the inbox renders fast.
  • Shopify product photos at the upper end. 70–100 KB is Shopify’s minimum-page-speed recommendation; 200 KB is the practical ceiling for higher-detail hero product shots that still load instantly.
  • Portfolio thumbnails. Design and photography portfolios that show 12–24 work tiles per page need every tile in the 100–250 KB band to scroll smoothly on mobile.
  • LinkedIn cover photos. The 1584×396 cover renders best pre-compressed to ~200 KB — LinkedIn’s server-side compression pass is less aggressive when the source is already lean.
  • Magazine-style editorial content. Inline content images on news sites and online magazines typically sit at 150–250 KB — the band where retina sharpness meets page-speed budgets.
  • Page-speed-conscious thumbnails. Any grid view — category pages, archive pages, related-posts widgets — benefits from a hard 200 KB ceiling per tile.
Why Sukat

Built around an exact 200 KB ceiling

The control most compressors expose — a quality slider — is the wrong one for the job.

Hits 200 KB, not “around” 200 KB

The standard online compressor exposes a quality slider and lets you guess. The same quality 75 produces an 80 KB file from a flat headshot and a 480 KB file from a busy landscape. Sukat takes the constraint directly: 200 KB, find the highest quality that fits. Internally it runs a binary search over the quality scale, converging in roughly seven re-encodes. You see the result, not the loop.

Full dimensions preserved at this cap

200 KB comfortably holds a 1500–1800 pixel WebP or JPEG at quality 82–88 — visually indistinguishable from the original on a retina display. Sukat reduces quality before touching dimensions, so for almost every photo, the output keeps its original pixel size. The live preview shows the actual output dimensions before you download.

WebP advantage holds at 200 KB

Pick WebP and you typically get 25–35% better quality at 200 KB than JPEG can deliver — that’s the difference between a slightly soft hero image and one that still looks pin-sharp at 200 KB. Sukat defaults to WebP because every modern browser supports it natively.

LCP-aware sizing

200 KB is the largest hero image you can ship without hurting Largest Contentful Paint on a median mobile connection. Sukat is built around that reality — the target field is the same control front-end performance engineers reach for when they audit a site against Core Web Vitals.

HEIC-aware

Shot it on iPhone? Sukat decodes HEIC directly — no separate convert-to-JPG step. Most online compressors fail silently on HEIC input, which is the source format for almost every photo taken on a modern iPhone.

Privacy by default

Compression runs entirely in your browser via the Canvas API. Your images never reach a server. Verify by switching to airplane mode after the page loads — the conversion still works.

Questions

FAQ

Will my photo still look sharp at 200 KB?

Yes — 200 KB comfortably holds a 1500–1800 pixel WebP or JPEG at quality 82–88, which is visually indistinguishable from the original on most displays. This is the sweet spot for web publishing: sharp on retina, fast on mobile. Even busy images (foliage, textured fabrics, crowds) compress cleanly at this size in WebP.

Should I pick JPEG or WebP for a 200 KB target?

WebP almost always wins at 200 KB — typically 25–35% smaller for the same visual quality, which means a sharper image at the same size. Pick WebP if your CMS or destination accepts it (WordPress, Substack, Shopify, Ghost, and every modern browser do). Pick JPEG only if the target explicitly requires JPG.

Can I compress PNG to 200 KB?

Yes, but PNG compresses inefficiently for photos — a 200 KB PNG holds a much smaller pixel image than a 200 KB JPEG or WebP. PNG at 200 KB makes sense for screenshots, line art, logos, and anything with transparency. For photos, switch the output to JPEG or WebP for far better quality at the same size.

How does a 200 KB image affect Core Web Vitals?

200 KB is roughly the upper bound for a Largest Contentful Paint element on a median mobile connection while still landing LCP under 2.5 seconds. Heavier hero images are the most common cause of failing LCP scores. Compressing the page’s LCP image to 200 KB is one of the highest-leverage Core Web Vitals fixes available.

Does Sukat preserve image dimensions at 200 KB?

Yes — Sukat reduces quality first, then dimensions only as a last resort. For typical 1500–1800 px hero photos, Sukat hits 200 KB at original dimensions with no visible quality loss. Very large source files (4000+ px panoramas at fine-detail subjects) may be downscaled slightly to fit; the live preview shows the actual output dimensions before download.

Is my image uploaded to a server?

No. Compression runs entirely in your browser via the Canvas API. Your images never reach a server. Verify by switching to airplane mode after the page loads — the conversion still works. Nothing leaves your device.

Can I batch-compress multiple images to 200 KB?

Yes. Drop several images at once, set 200 KB as the target, and Sukat compresses each independently to the same ceiling. Output downloads as separate files or as a single ZIP — useful when prepping a full gallery or blog-archive sweep in one pass.

State the limit. Sukat hits 200 KB.

Free, browser-based, no upload, no watermark. Drop your image, type 200, download.

Compress to 200 KB now →