UltKit

Compress Image to 70 KB

Upload a photo and get it back at 70 KB or a little under, with the highest quality that still fits. The page is set up for forms and websites that put the line at 70 KB, and for anyone who wants a file comfortably below a 100 KB cap.

Compress Image

or drop JPG, JPEG, JFIF … files here ·

Max 95 MB per file· Up to 20 files· Deleted after 30 minutes

Compress to

Files are processed on our servers and deleted after 30 minutes.

How to use this tool

  1. 1

    Add one photo or a batch

    Drop JPG, PNG, HEIC, WebP, GIF, BMP or TIFF files on the box. You can queue up to 20 at once, each as large as 95 MB.

  2. 2

    Check the 70 KB target

    Target size already reads 70 and Unit reads KB. Lower it to 68 if a portal has rejected a file that looked like exactly 70 KB.

  3. 3

    Press Compress and download

    Press Compress. Each file is written at or below the target, and the uploads are deleted from the server after 30 minutes.

A 70 KB image is about 1 bit per pixel at 600 × 800 px: enough for a sharp face or product shot, far too little for a full-size phone photo, so the tool lowers quality first and only then reduces the pixel count.

Who asks for an image under 70 KB

A 70 KB cap is less common than 50 KB or 100 KB, which is exactly why it catches people out. It turns up on smaller recruitment and admission portals, membership forms and older content management systems where an administrator picked a round number years ago. The rule is enforced by a script that reads the file size, so a file of 72 KB fails even if it looks perfect.

Plenty of people also choose 70 KB on their own. Product thumbnails, author photos on a blog, staff pages on an intranet and images placed in email newsletters all load faster when each file stays well under 100 KB. If your limit is the more common 100 KB and you want headroom, this page gets you there with about 30% to spare; if it is 50 KB, use compress image to 50 KB instead.

70 KB in bytes and pixels

Bytes in 70 KB when 1 KB = 1,024 bytes
71,680
Largest possible EXIF (APP1) segment in a JPEG, in bytes
65,535
A 4032 × 3024 phone photo, about 0.05 bits per pixel at 70 KB
12.2 MP
Bits per pixel for 600 × 800 px at 70 KB
≈ 1.2

The numbers explain what the tool does. A JPEG at a medium-high quality setting typically needs somewhere around 1 to 2 bits for every pixel of a portrait. At 12 megapixels that would mean well over a megabyte, so a 70 KB target forces a choice: keep every pixel and push quality into blocky territory, or keep quality and drop pixels. With Allow downscaling on, the tool takes the second route once quality reaches the floor set in Lowest quality allowed (40 by default).

Metadata is the hidden cost. The EXIF standard, first published by the Japan Electronic Industry Development Association in 1995, stores camera model, lens, exposure, GPS position and often a small preview image. Inside a JPEG that block can approach 64 KB on its own, which is nearly the entire budget of this page. Removing it before compression means every remaining byte describes the picture you actually see.

Compress JPEG, PNG or HEIC to 70 KB: what changes

DoDon't
Crop a portrait to head and shoulders before uploadingKeep a photo of a scene as PNG; it will lose many pixels to fit
Choose JPG output for HEIC photos going to a formRaise Lowest quality allowed above 80 at this size
Choose WebP output for a website that serves WebPTurn off Strip metadata unless you need the camera data
Keep Chroma subsampling on Auto for photosRename a .heic file to .jpg; the contents stay HEIC
Set Minimum width when the form states a pixel minimumCompress the same JPEG to 70 KB again and again

Compress image to 70 KB: answers

How many pixels can a photo keep at 70 KB?

For a face or a single object, roughly 600 × 800 px stays clean at 70 KB, which works out to a little over 1 bit per pixel. A busy outdoor scene needs more bytes per pixel, so the tool may settle on a smaller size such as 500 × 667 px. A full 12 MP phone frame cannot stay at full size.

Why does stripping metadata matter so much at this size?

A JPEG's EXIF block can be as large as 64 KB, and phone photos often carry a preview thumbnail inside it. At a 70 KB budget those bytes are better spent on the picture. Strip metadata is on by default, and Auto orient rotates the photo first so it still displays the right way up.

Can I stop the photo from being shrunk below a certain width?

Yes. Open Advanced settings and enter a value in Minimum width. If the tool cannot reach 70 KB at that width with the lowest quality you allow, the file comes out slightly over the target instead of narrower, so pick a realistic width.

Is 70 KB a good size for a photo on a web page?

For a thumbnail, avatar or inline picture under about 800 px wide, yes. For a full-width banner it is usually too small; the compress image to 400 KB preset is closer to what a 1920 px hero image needs.

My iPhone photo is HEIC. What do I get back?

With Output format on Same as input, the result keeps the original format. Many forms only take JPG, so switch Output format to JPG first; the 70 KB target still applies.