For most uses, 4096 × 2048 (4K) is the minimum for a 360° image and 8192 × 4096 (8K) is the size that looks sharp. The reason is that a viewer only ever shows a slice of the sphere, magnified to fill the screen, so a 360° image needs far more pixels than a flat picture shown on the same screen. Use 4K for small web embeds, mobile games and blurred or distant skies, and 8K for full-screen viewing, desktop games, VR and lighting. Beyond 8K, most displays cannot show the extra detail.
Pixels per degree: the number that matters
A 360° image covers the full circle of the horizon, so its width is spread across 360°. Divide the width by 360 and you get how many pixels describe each degree of the view:
| Image size | Name | Pixels per degree | Pixels across a 90° view |
|---|---|---|---|
| 2048 × 1024 | 2K | about 5.7 | 512 |
| 4096 × 2048 | 4K | about 11.4 | 1,024 |
| 8192 × 4096 | 8K | about 22.8 | 2,048 |
| 16384 × 8192 | 16K | about 45.5 | 4,096 |
Now compare that with the screen. A 360° viewer shows a slice of the sphere, typically somewhere around 70° to 100° wide, and stretches it across the whole window. Say the window is 1920 pixels wide and shows 90° of the view. To look pixel-sharp, the image needs 1920 ÷ 90, about 21 pixels per degree. A 4K image has 11.4, so every pixel of it is spread across about two pixels of the screen and the view looks soft. An 8K image has 22.8, just enough.
That is the whole secret of 360° resolution. “4K” sounds generous because a flat 4K photo is sharp on almost any screen, but a 4K panorama spends those 4,096 pixels on the full circle. Only about a quarter of them are on screen at any moment. Zooming in narrows the view and raises the demand further, and a larger or higher-resolution screen raises it again.
Recommended size by use
| Use | Recommended | Why |
|---|---|---|
| Small web embed or thumbnail | 4096 × 2048 JPEG | The viewer is small, and the download matters more than fine detail |
| Full-screen web viewer | 4K first, then 8K | Show a 4K copy straight away and swap in the 8K when it arrives |
| Desktop or console game | 8192 × 4096, compressed | The sky fills large, sharp screens, and players look around slowly |
| Mobile game | 4096 × 2048, compressed | Smaller screens, tighter memory, and far more to fit in it |
| VR headset | 8192 × 4096 | Headset lenses magnify the view; see the best resolution for VR 360° images |
| Lighting a 3D scene | 4K is plenty for lighting; 8K where the sky is seen or reflected | Lighting uses broad areas of the image, not fine detail |
| Print of the flat image | 8192 × 4096 or larger | At 300 pixels per inch, 8,192 pixels print about 69 cm wide |
Headsets deserve their own note, because they magnify the view more than any monitor does. Even 8K sits just below what a current standalone headset can show. That comparison, headset by headset, is in the best resolution for VR 360° images, and the VR environments page covers making worlds for headsets.
What the extra detail looks like
The difference between 4K and 8K is not spread evenly across a scene. It shows most in anything with fine, hard-edged detail at the horizon: the windows of a distant city, the branches of a treeline, rigging, railings, lettering on signs. It shows least in soft subjects: clear or hazy skies, mist, night scenes, water, and anything a game renders out of focus. A cloudy seascape at 4K can look almost identical to the same scene at 8K, while a city skyline at 4K turns to mush the moment a viewer fills the screen.
So the right size depends on the scene as well as the screen. When in doubt, open both sizes in the viewer you will actually use, at the size you will actually show it, and look at the busiest part of the horizon.
File size and memory
Doubling the width and height of an image quadruples its pixels. An 8K image has 33.6 million pixels to a 4K image’s 8.4 million, and it costs accordingly in two separate places.
- On disk and over the network, the file size depends on the format and the scene. The ten 4096 × 2048 JPEG worlds on this site range from about 0.4 MB for a dark hall to 2.6 MB for a courtyard full of blossom. Busy detail costs bytes; smooth skies compress well. The same image as a PNG is several times larger, which is why the web gets JPEGs and engines get PNG or EXR.
- In memory, the file size stops mattering. Once decoded, an image takes its full size: 32 MB for a 4K image and 128 MB for an 8K image at four bytes per pixel, whatever the JPEG weighed. Mipmaps add about a third. Game engines shrink this four-fold or more with GPU texture compression, which is covered in skybox texture size and memory, explained.
Memory is where 8K most often hurts: on phones, standalone headsets and web pages opened on older devices. Some older mobile graphics chips cannot take a texture wider than 4,096 pixels at all, so a web viewer should check the device’s limit before loading an 8K image, and fall back to 4K.
WorldGen360 Studio
Generate at the size you need
Studio generates worlds from a 1024 × 512 draft up to 8192 × 4096, and one generation costs one credit whatever the size. Start with five free credits and 4K downloads, no card required.
- Draft, 2K, 4K and 8K sizes
- One credit per world at any size
- Commercial use on every plan
When 4K is enough
- The viewer is a small embed rather than full screen.
- The sky is soft: night, fog, haze, open water, or plain cloud.
- The game blurs the background with depth of field, or the camera moves too fast to study the horizon.
- The image only lights a scene and is never seen directly.
- Memory is tight, as on phones, and the sky has to share it with everything else.
When 16K is overkill
A 16384 × 8192 image gives about 45.5 pixels per degree, roughly double what an 8K image offers and well beyond what most screens and headsets can resolve in a normal view. It costs four times the memory of 8K, 512 MB uncompressed, and 16,384 pixels is the largest texture many engines and graphics cards accept. It earns its place for deep zoom on very large displays, and for high-resolution renders where the sky fills the frame. For almost everything else, 8K is the practical ceiling.
How to downscale a 360° image well
It is common to keep one 8K master and make smaller copies for the web, phones or quick previews. Three habits keep the copies clean:
- Use a good resampling filter. Lanczos or bicubic keeps detail crisp; the “nearest neighbour” option some tools default to leaves jagged edges.
- Protect the seam. Resizing filters look at neighbouring pixels, and at the left and right edges ordinary software cannot see that the neighbours are on the opposite side. That can leave a faint line where the image wraps. The fix is to copy a narrow strip from each edge onto the opposite side, resize, then crop the strips off again.
- Sharpen lightly, once. A small unsharp mask after resizing brings back crispness lost in the resample. Keep it subtle: halos around the horizon and banding in smooth skies are far more visible in a viewer than on a flat preview.
Keep the copies exactly 2:1 and in even sizes, such as 4096 × 2048 or 2048 × 1024. In WorldGen360 Studio you pick the size when you generate, from a 1024 × 512 draft up to 8192 × 4096. One generation costs one credit whatever the size, so there is no saving in generating small: make the master at the size you will need most, and scale down from there. The complete guide to 360-degree images puts resolution alongside projections and formats.
Frequently asked questions
Is 4K enough for a 360° image?
For small embeds, phones, soft skies and lighting, yes. For a full-screen viewer, a desktop game or a VR headset, 4K looks noticeably soft, because only about a quarter of its width is on screen at once. Use 8K there.
How many pixels is an 8K 360° image?
An 8K 360° image is 8192 × 4096 pixels, about 33.6 million in total. That is four times the pixels of a 4096 × 2048 image, and four times the memory once it is loaded.
How much detail per degree does 8K give?
About 22.8 pixels per degree: 8,192 pixels divided by 360°. That is roughly double the 11.4 of a 4K image, and close to what a 1920-pixel-wide window needs to show a 90° view without softening.
Will an 8K panorama slow down my website?
It can if it is the only thing the viewer loads. Show a 4K JPEG first so the view appears quickly, then load the 8K copy in the background and swap it in, and fall back to 4K on devices that cannot take an 8K texture. How to add a 360° image viewer to your website explains the approach.
