Madalas pinagsasama ng designers at developers ang file size(KB/MB) saimage dimensions(px) atruntime memory usage. Ang heavily compressed 4000×3000 px JPEG ay puwedeng 450 KB lang sa disk, pero kapag na-decode ng mobile browser o GPU compositor, lumalawak ito sa 48 MB uncompressed 32-bit RGBA bitmap (4000 × 3000 × 4 bytes).
Kina-calculate ng Image Size Inspector namin ang bawat geometric at storage metric nang sabay:
| 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 |
Tinutukoy ang sharpness sa Retina/4K displays at CSS layout reservation |
| Aspect Ratio | $\frac{W}{\gcd(W,H)} : \frac{H}{\gcd(W,H)}$ | 16:9 (1.778:1) |
Iniiwasan ang cropping mismatch sa responsive grids at social cards |
Megapixels (MP) |
$\frac{\text{Width} \times \text{Height}}{1,000,000}$ | 8.29 MP |
Standard benchmark para sa camera sensor resolution at print detail |
| Uncompressed RGBA RAM | $\text{Width} \times \text{Height} \times 4\text{ bytes}$ | 31.64 MB (33,177,600 B) |
Puwedeng mag-crash ng mobile Safari tabs ang high MP images kung tumaas ang decoded RAM |
Bits Per Pixel (BPP) |
$\frac{\text{File Bytes} \times 8}{\text{Width} \times \text{Height}}$ | 0.48 bpp (sa 500 KB file size) |
Sinusukat ang compression efficiency; < 1.0 bpp ay nagpapahiwatig ng modern WebP/AVIF encoding |
Kung sobra ang pixel dimensions o bloated ang BPP sa inspection, i-optimize agad ang file gamit ang Resize Image o Compress Image tools namin.