Image requirement guide

Resize an image to a KB maximum

When a form rejects an image because it is too large, the useful answer is not a mystery slider. Aftermath shows the final byte count, tells you what passed, and keeps the file on your device.

A byte limit is a validation rule, not a quality guess

Upload fields usually compare the final file bytes, not the quality percentage shown by an editor. Aftermath encodes the image in your browser, measures the resulting file, and reports the actual number that a destination is likely to inspect. The original remains untouched, so you can try a stricter limit without losing the source.

Keep dimensions intentional when the limit is tight

A large canvas can remain too heavy even after quality is lowered. Start with the destination dimensions when they are known, then choose fit or crop so the image does not become distorted. If the final result still fails, the report says whether the byte limit or the pixel requirement is the constraint instead of silently changing both.

Questions people ask

Does the image leave my device?

No. JPG, PNG, and WebP files are processed in this browser and are not sent to an Aftermath conversion server.

Can I prepare several files at once?

Yes. Add multiple files, reorder them, prepare the batch, and download the validated results individually or as one local ZIP.

How to use this tool

Set a maximum KB value when the destination specifies a ceiling rather than a fixed output size. The starter setting is 100 KB and can be changed. For JPEG or WebP, the local processor searches for the highest encoder quality that stays at or below the ceiling, then may reduce dimensions if quality tuning is exhausted. PNG receives a size check but does not use that quality search, so an oversized result can fail.

What to choose and what you get

What to choose

  • one supported local image

Result

  • a separate processed image copy or local measurement report

Supported use

  • A changeable maximum-byte requirement applied to verified JPG, PNG, or WebP source files without a mandatory output width or height.
  • JPEG and WebP quality search followed by bounded canvas reduction when encoder quality alone cannot satisfy the ceiling.

Before you start

  • The result is not padded to equal an exact byte count; the validator checks that it is at or below the entered maximum.
  • A PNG byte ceiling is checked but is not reached through JPEG/WebP-style quality search, and no external portal acceptance is guaranteed.

Supported formats

  • Accepted formats: JPG, PNG, WebP, HEIC, AVIF, GIF, BMP.
  • Output formats: JPG, PNG, WebP.

Browser support and permissions

  • Modern browser with JavaScript, a supported image decoder, and enough memory for the selected image.
  • No camera, microphone, or screen permission is needed.

Choose the right settings

  • Use this page when the destination states an arbitrary maximum KB value and does not require a fixed pixel canvas.
  • Use a 20, 50, 100, or 200 KB preset page when that exact named ceiling is the search intent and desired starting point.
  • Move to /custom when dimensions, minimum bytes, crop behavior, or format must be configured together with the maximum.

Worked example

An application accepts a photograph up to 150 KB but does not prescribe an exact pixel canvas.

Starting facts

  • The selected JPG is larger than the stated maximum.
  • No exact width or height is part of the requirement.

Observed operation: Set 150 KB as the maximum and let the local quality search reduce encoding quality before it considers reducing the canvas.

Review the result: Use the measured output bytes and preview to decide whether the downloaded copy is both under the ceiling and still legible.

Boundary: A maximum-size pass does not prove visual quality, minimum-size compliance or acceptance by the destination.

What you can do

Compress an image under a user-selected maximum KB ceiling when no fixed output dimensions are required.

If it does not work

  • Even the smallest result reached by bounded quality and dimension reduction can remain above an unusually restrictive maximum.
  • Adding fixed width or height constraints prevents automatic dimension reduction, so the required canvas can fail the byte check.
  • Unsupported, empty, oversized, signature-mismatched, or browser-undecodable sources are rejected before a valid result is offered.

Things to know

  • The measured result still needs review against the intended destination or use.

Privacy boundary

The selected image stays in the current browser session and is not sent to an Aftermath processing service. How local processing is verified.

What this tool verifies

Checks the displayed limits and reports or creates a separate processed image copy or local measurement report from one supported local image.

Check before sharing

A local measurement or export does not guarantee acceptance by an external destination.

How it works · Privacy · Terms of use · Contact