When you upload a photo to a job portal, it doesn't get displayed to the recruiter at full resolution. It gets stored in a database record alongside your CV, cover letter, and application responses, and then displayed as a thumbnail somewhere between 60 and 150 pixels wide inside the recruiter's application management dashboard. At that display size, a 96KB JPEG is pixel-for-pixel identical to a 6MB original. The recruiter cannot see any difference because there is none at that scale.
The 100KB limit isn't about quality. It's about storage and processing speed. A company receiving 500 applications for a single role would store 500 photos. At 5MB each, that's 2.5GB just for photos from one job posting. At 96KB each, it's under 50MB. Multiply that across thousands of job postings and hundreds of thousands of applicants, and the storage math becomes very clear very quickly.
The HEIC problem that blocks iPhone users
A significant portion of job application photo failures aren't about file size at all. iPhones save photos in HEIC format by default, and virtually no HR platform built before 2022 accepts HEIC. The portal rejects it silently with a generic error, which looks identical to a file size rejection. Many people go through multiple rounds of compression trying to fix a size problem that doesn't exist. The actual problem is the format.
If you're on an iPhone, the fix is to convert to JPEG first. This tool handles HEIC input and converts and compresses in a single step, outputting a JPEG under 96KB. If you want to check the format issue specifically, the HEIC to JPG converter handles that on its own. Either way, always output as JPEG for job portals. It's the one format every HR system was built to accept.
Why the target here is 96KB and not 100KB
File sizes are measured in bytes, not round numbers. A file your operating system reports as "100 KB" is actually 102,400 bytes. Some portals check against 100,000 bytes. Some check against 102,400 bytes. Some have off-by-one errors in their validation code. Compressing to exactly 100KB and submitting can still result in a rejection depending on which measurement the portal uses. Targeting 96KB gives a clean 4% margin that handles all of these edge cases. Your file passes first time without needing to guess the portal's exact byte threshold.