At 10MB most photos fit at full quality, so the tool checks a quality 100 encode first and uses it if it fits. Only when that overshoots does it search down for the highest quality that does. Both steps run in a background worker, which matters here because files this large take longer to encode.
The usual reason an image is over 10MB is its format, not its quality. A photo or screenshot saved as PNG is stored losslessly, and re-encoding it as JPEG, WebP or AVIF often shrinks it to a fraction of the size with no visible change. Very large pixel counts are the other cause; if a site also limits dimensions, set Max width/height.
Where 10MB limits come from
10MB is a common default for attachments. GitHub's documentation, for example, allows images and GIFs up to 10MB in issues and pull requests. Other sites set their own figures, so check the limit the site states.
How 10MB is counted
This tool uses decimal units: 1 MB is 1,000 KB and 1 KB is 1,000 bytes, so a 10MB target means at most 10,000,000 bytes. Sites that count 1 MB as 1,048,576 bytes allow slightly more, so the result passes either way. If the limit is tighter, use compress to 5MB instead.