Requirement guide
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.
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 Blob, 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.
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
No. JPG, PNG, and WebP files are decoded and exported in the browser. This website does not need an upload endpoint for the MVP.
Yes. Add multiple files, reorder them, prepare the batch, and download the validated results individually or as one local ZIP.