Pixels are fixed; bytes are not
The pixel size is a count: 200 × 230 is 46,000 pixels whatever is in them. The file size is how many bytes the encoder needed to describe those pixels, and that depends almost entirely on how much detail there is. A JPEG stores smooth areas cheaply and edges, texture and noise expensively.
So two photographs at exactly the same pixel size can differ several times over in kilobytes. A face against a patterned curtain, shot in dim light with a phone's noise in it, is expensive. The same face against a flat, even white is cheap, because a third of the frame is now one value.
Why the floor bites after a background change
Replacing a busy room with pure white removes most of what the file was spending bytes on. At a small form size that can push a photo under the window's minimum — the opposite of the problem people expect. A portal's minimum exists to catch blank or over-compressed uploads, and a very efficient file can trip it.
Take the public-sector bank photograph row: 200 × 230 px preferred (4.5 × 3.5 cm), 20–50 KB, 200 DPI or more. This site reads that window as 20,480 to 50,000 bytes — the bottom in 1,024-byte kilobytes and the top in 1,000-byte kilobytes, so a file inside it passes under either reading of “KB”.


