Compress a JPG to 200 KB
Three steps. State the limit, pick JPEG, download a .jpg under 200 KB the portal will accept — usually at full resolution.
Upload the image
Drop a JPG, PNG, WebP, HEIC, AVIF, or GIF onto the drop zone. A profile photo, blog hero, or product shot is the usual input at this size — iPhone HEIC works directly.
Set 200 KB and pick JPEG output
Type 200 in the Maximum File Size field and pick KB. Switch the output format to JPEG so the download keeps the .jpg extension the portal expects.
Convert and download
Click Convert & Download. Sukat binary-searches the JPEG quality scale and saves a .jpg that fits under the 200 KB ceiling — usually at full original dimensions.
When 200 KB is the right JPG target
200 KB is the sharp-but-fast ceiling — comfortable for photographic content that still has to load quickly. It clusters around a specific set of uploads.
- LinkedIn profile photos. LinkedIn re-compresses uploads, but pre-compressing to a sharp 200 KB JPG skips a lossy server pass and keeps a recognisable face at the 400×400 display size. Its older recommended specs accept JPG cleanly.
- Blog and CMS featured images. 200 KB is a common editorial ceiling for a hero or featured image — the point where WordPress, Ghost, and Substack pages stay fast without the photo going soft.
- Recruiter portals and resume attachments. Many ATS and application forms reject headshots above a few hundred KB and accept JPG only. 200 KB clears the cap with detail to spare.
- Marketplace and e-commerce listings. Product photos that need to load quickly across a grid of listing thumbnails — 200 KB keeps each one crisp without dragging the page down.
- Forum and community avatars or post images. Older forum software and community platforms often cap uploads around 200 KB and transcode or reject WebP, so a JPG is the safe choice.
Built for the JPG-plus-200-KB constraint
The right format and a comfortable ceiling at once — usually without touching your resolution.
Hits 200 KB and JPG together, in one pass
Set JPEG as the output, type 200 KB as the maximum file size, click convert. The binary search converges on the highest JPEG quality that still fits under the cap, and the download lands with a .jpg extension and the right header bytes for the portal’s file-type check. One pass, no format round-trip.
Full resolution, most of the time
200 KB is roomy for a typical 1080p–1500p photo, so Sukat usually converges around JPEG quality 80–90 at full original dimensions — visually indistinguishable from the source. It only downscales pixel dimensions if quality alone can’t reach the target, which is rare at 200 KB. The live preview shows the real output size first.
The WebP gap is real — the destination decides
WebP would give you better quality per byte at 200 KB. If the upload target accepts WebP, take it. If it requires JPG — as LinkedIn, most ATS widgets, and many CMS libraries do — that gap doesn’t matter, because the portal will reject the smarter file. Sukat gets you the best JPEG possible under the cap.
HEIC or PNG input, JPG output, one step
If the source is an iPhone HEIC or a PNG screenshot and the form needs a JPG under 200 KB, Sukat handles the decode and the format conversion in the same compression pass — no separate “convert to JPG first” widget.
Local-only, no upload
Compression runs entirely in your browser via the Canvas API. Your files never reach a server, EXIF and GPS are stripped on re-encode, and you can verify by switching to airplane mode after the page loads — the conversion still works.
FAQ
Can I compress a JPG to 200 KB without losing quality?
Why do platforms ask for around 200 KB?
Why JPG and not WebP for a 200 KB target?
.jpg, Sukat gets you the best JPEG under the cap.