Designers and developers often conflate file size (KB/MB) with image dimensions (px) and runtime memory usage. A heavily compressed 4000×3000 px JPEG might only weigh 450 KB on disk, but once decoded by a mobile browser or GPU compositor, it expands into a 48 MB uncompressed 32-bit RGBA bitmap (4000 × 3000 × 4 bytes).
Our Image Size Inspector calculates every geometric and storage metric simultaneously:
| Metric Name | Mathematical Formula | Real-World Example (3840×2160 4K Hero) |
Why It Matters for Web & Print |
|---|---|---|---|
| Pixel Dimensions | $\text{Width} \times \text{Height}$ (px) |
3840 × 2160 px |
Determines sharpness on Retina/4K displays and CSS layout reservation |
| Aspect Ratio | $\frac{W}{\gcd(W,H)} : \frac{H}{\gcd(W,H)}$ | 16:9 (1.778:1) |
Prevents cropping mismatch in responsive grids and social cards |
Megapixels (MP) |
$\frac{\text{Width} \times \text{Height}}{1,000,000}$ | 8.29 MP |
Standard benchmark for camera sensor resolution and print detail |
| Uncompressed RGBA RAM | $\text{Width} \times \text{Height} \times 4\text{ bytes}$ | 31.64 MB (33,177,600 B) |
High MP images can crash mobile Safari tabs if decoded RAM spikes |
Bits Per Pixel (BPP) |
$\frac{\text{File Bytes} \times 8}{\text{Width} \times \text{Height}}$ | 0.48 bpp (at 500 KB file size) |
Measures compression efficiency; < 1.0 bpp indicates modern WebP/AVIF encoding |
If your inspection shows excessive pixel dimensions or bloated BPP, optimize the file immediately with our Resize Image or Compress Image tools.