Why a 500 GB drive shows 465
The drive holds 500,000,000,000 bytes. Windows divides by 1024 at each step and still calls the result GB, so it reports 500e9 / 2^30 = 465.7. Nothing is missing — one side counts in powers of ten, the other in powers of two. The first row of the converter is the honest number: bytes.
Mbps is bits, MB/s is bytes
A byte is 8 bits, so 100 Mbps = 12.5 MB/s. A 1 GB file needs 80 seconds at that rate with no overhead at all; TCP, TLS and Wi-Fi framing take a slice, which is what the efficiency field models. ISPs quote bits; file managers show bytes; that factor of eight is the whole confusion.
Bitrate, resolution and frame rate
A 4K60 8-bit 4:2:0 frame is 3840 × 2160 × 1.5 = 12.4 MB, so raw video runs at 746 MB/s — nearly 6 Gbps. An encoder gets that to 40 Mbps by throwing away detail the eye is slow to notice, a ratio near 150:1. Raise the frame rate and the bitrate has to follow; that is why 60 fps costs more than twice 30 fps at the same quality.
Where the last few percent go
The file you get is video plus audio plus container: 40 Mbps of video and 128 kbps of audio is 40.128 Mbps, and MP4 or MKV headers, indexes and keyframes add one or two percent. A target size works backwards the same way — size × 8 ÷ duration, minus the audio, with the overhead divided out.