Reduce Image Size to 70KB

How to use this tool

1. Upload a JPEG, PNG, or WebP image.
2. Set the maximum edge in pixels to remove unnecessary resolution.
3. Reduce to 70KB, check the new dimensions, and download the JPEG.

Preparing a photo for a small web tile

Review the output alongside nearby tiles. Compression artifacts can become noticeable when one tile is much sharper than another.

Resize first for a 70KB upload

Unlike quality-first compression, this tool first fits the image within your maximum edge while keeping proportions. A compact web photo is a good starting point. Inspect fine lines, hair, and any lettering after compression, especially if a portal also specifies pixel dimensions.

Check the file and dimension limits separately

The tool treats 70KB as 70000 bytes, using the stricter decimal convention. A service that counts 1KB as 1,024 bytes allows 71680 bytes. Check the downloaded byte count against the receiving service’s rules.

When to use the dimension-first workflow

For example, a 4,000 × 3,000 camera photo rarely needs all its pixels for a small profile box. Limiting the long edge can reduce the amount of quality loss needed. If every original pixel matters, use the JPEG compressor instead.

Choosing dimensions before reducing to 70KB

Think about the tile’s aspect ratio before deciding its maximum edge. A source that is twice as wide as the slot may lose half its width when the website crops it later. Make that crop deliberately first, so the reduction process spends its available pixels on the visible subject.

For a photo for a small web tile, start with the pixel dimensions needed at the destination. This workflow first limits the longest edge, then encodes a JPEG against your byte allowance. If the initial resize already removes important information, a higher quality setting cannot put those pixels back.

A practical 70KB file-size example

Suppose your source is 1,500KB and the permitted result is 70KB. The output must be no more than 4.7% of the source file size—a reduction of at least 95.3%. This calculation describes the requirement, not a predicted compression result. A quality setting of 5% would not reliably produce that percentage of the original bytes.

For a 2400 × 1800 source, setting the maximum edge to 800 produces 800 × 600 pixels before any further target-driven downscaling. That removes 89% of the pixel count. The final dimensions can become smaller if the first JPEG still exceeds the target.

Maximum edge and quality work together

Maximum edge is a ceiling, not a request to stretch the image. A portrait is usually limited by its height; a landscape is usually limited by its width. The other dimension follows proportionally. A source smaller than the chosen ceiling is not enlarged by this control.

Quality controls the JPEG encoding after resizing. Start with a moderate value and inspect the result. If the target requires further reduction, the tool can lower quality and dimensions. Use the dedicated resizer when exact width and height are mandatory, then check the file-size result separately.

Tools for this step: Resize to exact dimensions

If the 70KB image is rejected or looks unclear

Check the exact byte count before making another attempt. The result can be below 70KB without being exactly that size because the tool does not append padding. If it reports an unmet target, choose a smaller source crop or a larger allowance rather than assuming that the download already qualifies.

A soft result may have lost detail during the initial resize, before compression. Increase the maximum edge only if the receiving form allows it. If a specific subject is too small, crop closer to that subject instead of spreading more pixels over unused background.

• Confirm the destination really requests 70KB rather than 70MB.
• Open the exported image and check small text at normal reading size.
• Keep the original so you can make a fresh attempt without recompressing a damaged copy.