AI says the file is under one megabyte. Does the limit mean MB or MiB?

Compare actual bytes with the stated limit. 1 MB is 1,000,000 bytes; 1 MiB is 1,048,576 bytes, so the same file can pass one threshold and exceed the other.

NIST distinguishes decimal megabytes from binary mebibytes. A rounded size label is not enough to determine whether an upload will be accepted. Check the service’s documented unit and boundary.

A file between the two limits

We created our own disposable binary fixture and read its size: 1,024,000 bytes. That is 1.024 MB or 0.9765625 MiB. Under our invented inclusive limits, it exceeded 1 MB but was within 1 MiB. No upload was attempted.

Ask for the byte comparison

Suggested input: “Show the actual file’s byte size and the documented maximum in bytes. State whether the boundary is inclusive. Do not infer acceptance from a rounded display value.” Confirm the measurement on the final exported file.

Do not assume every app labels size the same way

If a service writes MB without explaining the limit, record that ambiguity and check its help or actual validation. Our unit comparison does not establish that service’s rule. A compressed file’s size also does not tell you the size after extraction.

Size is only one acceptance condition

A file that fits the byte limit can still have an unsupported type or other unmet requirements. Check the intended destination’s rules. Changing the displayed unit or renaming the file does not reduce its actual bytes.

Published October 14, 2026. Only a new 1,024,000-byte fixture and fictional threshold comparisons were tested locally. No user file, compression operation, AI output or upload service was tested or changed.

Sources: NIST · Binary prefixes.