4K UHD Dimensions
Recommended size: 3840 × 2160 pixels
4K UHD (3840×2160 pixels) is four times the resolution of 1080p, used primarily for high-end displays, digital signage, print-quality web assets, and video production. While 4K monitors are increasingly common, serving 4K images to web visitors requires careful optimization — a single uncompressed 4K image can exceed 10 MB. For most web use cases, 4K serves as the 2× Retina source for visitors on high-DPI displays viewing full-width content.
Specifications
| Width | 3840px |
| Height | 2160px |
| Aspect Ratio | 16:9 |
| Platform | general |
| Category | standard |
When You Actually Need 4K Images
4K is not always necessary or even beneficial. Use 4K specifically when:
- Retina hero images: As the 2× source in
srcsetfor visitors on 2× or 3× displays viewing full-width content - Photography portfolios: Where image quality is the product and visitors expect maximum detail
- Print preparation: Images that may be printed at high resolution (300 DPI)
- Digital signage: 4K displays are standard in commercial signage
- Video production: Source footage and thumbnails for 4K video content
Do NOT use 4K for:
- Standard web images that display at 600-800px — this wastes enormous bandwidth
- Mobile-first audiences — mobile screens max out at ~1290px width (iPhone 15 Pro Max) and even that's 3× points, not pixels needed
- Email images — email clients don't benefit from 4K resolution
Compression Is Critical at 4K
At 3840×2160, file size management is critical:
- Uncompressed: ~25 MB per image (completely impractical for web)
- JPEG quality 85: 1-3 MB (too large for web without CDN optimization)
- JPEG quality 70: 500 KB - 1.5 MB (usable with lazy loading)
- WebP quality 75: 300 KB - 800 KB (recommended for web delivery)
- AVIF quality 60: 200 KB - 500 KB (best compression available)
For web use, always pair 4K images with modern formats (WebP/AVIF) and lazy loading. A 4K WebP at quality 75 is often comparable in file size to a 1080p JPEG at quality 85.
Use an image CDN (Sirv, Cloudinary, Imgix) to serve the optimal format and size automatically based on the visitor's device and connection.
Responsive Delivery Strategy
Never serve a 4K image to everyone. Use responsive images:
- srcset and sizes: Let the browser choose between 640w, 1024w, 1920w, and 3840w versions
- Image CDN: Automatically generates and serves the right size based on
Acceptheaders and client hints - Art direction: Use
Example responsive image implementation: 
With this approach, 4K is only downloaded by visitors who actually benefit from it — those on large, high-DPI displays with sufficient bandwidth.
Quick Tips
- → Use 4K only as the 2× option in srcset — never as the only image size
- → Compress aggressively: WebP quality 75 or AVIF quality 60 keeps 4K under 500 KB
- → Use an image CDN to auto-serve the right size and format per visitor
- → For most web use, 1920×1080 is sufficient — 4K is only needed for high-DPI full-width content
Related general Sizes
Frequently Asked Questions
Should I use 4K images on my website?
Only as the high-resolution option in a responsive image setup. Never serve 4K as the only size — most visitors are on 1080p screens and would download 4× more data than needed. Use srcset to offer 4K alongside smaller sizes, and let the browser choose. For most web content, 1920×1080 is the practical maximum.
What is the file size of a 4K image?
It varies widely by format and compression. Uncompressed: ~25 MB. JPEG quality 80: 1-3 MB. WebP quality 75: 300-800 KB. AVIF quality 60: 200-500 KB. For web delivery, use WebP or AVIF and target under 500 KB per 4K image with appropriate compression settings.
What's the difference between 4K and 1080p for web images?
4K (3840×2160) has exactly 4× the pixels of 1080p (1920×1080). On a standard 1080p display, 4K provides no visible benefit — the extra pixels are wasted. On 2× Retina displays, 4K provides 1:1 pixel mapping for full-width content, resulting in sharper images. Use responsive images to serve the right size to each device.