File size limit
A 1 MB cap is the most common upload limit on forms, forums, and content systems, and a photo from a modern phone is several times that. This page opens on the whole image with JPEG export and a 1 MB target already filled in, so the only thing left is to load the photo and press Fit. Cropy encodes at a handful of qualities, halving the range each time, and keeps the highest quality whose file actually fits. The size you see is the size of the file you download, because it is measured with the same encoder.
The target field already says 1 MB. Load a PNG, JPG, or WebP and press Fit: Cropy tries a few qualities, each time halving the range it still has to search, and stops at the highest one that fits under the target.
This page opens in the convert workflow, which exports the whole image at its own dimensions. A 4000x3000 photo stays 4000x3000; what changes is how hard the JPEG encoder compresses it.
Upload limits differ between services and change without warning, and some count 1 MB as 1,000,000 bytes while others count 1,048,576. Cropy targets the smaller, decimal reading, so a file that fits here also fits the other one. Read the limit on the form you are uploading to and type it in if it is not 1 MB.
Load it on this page and press Fit. Cropy searches the quality range for the highest quality whose encoded file stays under 1 MB and applies it, then shows the resulting size.
No. This page uses the convert workflow, which keeps the source dimensions. Only the compression changes. Switch to Crop when the dimensions should change too.
Cropy says so, and names the smallest file it could produce. At that point the dimensions are what is holding the file up: crop or resize the image, or try WebP, which usually encodes smaller than JPEG at the same quality.
Yes. It comes from encoding the image in your browser with the same code that produces the download, so it is a measurement rather than a prediction.