Building a convincing Earth is one of those projects that looks simple from the outside and turns into a week of shader tweaking once you start. A sphere, a texture, a sun lamp — that is the naive plan. The realistic plan involves understanding how scale, color space, atmospheric scattering, and render sampling interact. This walkthrough covers the full pipeline for a photorealistic 4K Earth in Blender 2.8 and later, from sourcing data to final frame, with the decision points that actually change the result.
Why the Earth Is Still a Benchmark Project
Every environment artist builds a planet at some point. It is the 3D equivalent of learning to draw hands: deceptively familiar, brutally unforgiving. Viewers have seen the Earth from orbit thousands of times. They may not be able to articulate what a real satellite photograph looks like, but their pattern recognition is instant and merciless. A blue ball with a stamp of continents reads as fake within a fraction of a second.
That makes Earth an excellent test of fundamentals. To sell the shot you need:
- Physically plausible scale, so the terminator curves correctly and the horizon feels huge.
- Correct color space handling, so land does not turn neon and oceans do not go black.
- A shader that treats ocean, land, and ice as three different materials responding differently to light.
- An atmosphere that softens the limb and scatters blue at grazing angles.
- Render settings that survive a 4K crop without visible noise, banding, or fireflies.
Get those five things right and the planet holds up from almost any angle. Skip one and the image collapses into "CG sphere," no matter how many texture maps you stacked on it.
What "4K" Actually Means for a Planet Asset
The phrase "4K Earth" gets used loosely. It helps to separate three different things it can mean.
Texture resolution versus output resolution
A 4K render is a 3840 x 2160 output. A 4K texture is a 4096-pixel-wide image map. You can render at 4K from a 2K texture set and get a soft but acceptable result, and you can render at 1080p from an 8K texture set and throw away most of the detail you paid for in VRAM. The two numbers are independent, and confusing them is the most common source of disappointing first attempts.
Pixels per degree
Because an equirectangular map wraps 360 degrees of longitude across its width, a 4096-pixel map gives you roughly 11 pixels per degree of longitude. Zoom the camera so the globe fills a 4K frame horizontally and you are showing about 140 degrees of the planet at 3840 pixels — 27 pixels per degree. In other words, your texture is under-sampled by more than a factor of two. This is why surfaces look mushy at full frame even when the source map seemed sharp.
Where detail actually reads
Detail on a planet reads in three places: the coastline silhouette against the ocean, mountain relief catching low-angle sunlight, and cloud structure. Everything else — subtle land color variation, fine river networks — is mostly invisible at typical framing. Spending your resolution budget on coastline masks and normal or displacement maps pays far better than hunting for an enormous diffuse map.
Collecting and Preparing Source Imagery
You do not need exotic data for this. You need the right set of maps, consistently projected, and colour-managed before they ever touch the shader.
The maps you actually need
For a solid result, gather or author these:
- Albedo / diffuse colour — land and ocean base colour, ideally free of baked-in lighting.
- Ocean mask — a clean black-and-white map separating water from land. This drives roughness, specular, and displacement more than any other single input.
- Elevation / height — for bump or true displacement. Even a modest resolution map adds convincing relief at the limb.
- Night lights — city emission, used as an emissive texture masked to the dark side.
- Cloud map — with alpha, or as a density input for volumetric rendering.
- Specular or water mask variants — useful for controlling sun glint on oceans.
If you author your own masks, build them at a higher resolution than the colour map. Masks cost almost nothing in VRAM compared to a colour pass, and crisp coastlines are where the eye lands first.
Colour space and projection discipline
Every map has one correct colour space setting and getting it wrong is silent and painful. Colour data (albedo, night lights) belongs in sRGB. Data maps (height, ocean mask, roughness) belong in Non-Color. Set these at the image datablock level, not in the shader, so nothing gets double-converted. All maps must share the same equirectangular projection and the same longitude offset. A height map rotated ten degrees relative to the albedo produces mountains sliding into the sea.
One practical trick: assemble every map in the same document at the same resolution with a consistent naming convention before importing. Bulk-importing a tidy folder is far less error-prone than adding images one by one.
Modelling the Globe: Scale, Geometry, and Displacement
Scene units and true scale
The Earth's radius is about 6,371 kilometres. You do not have to model it at that scale, but you do have to be consistent, because the atmosphere thickness and displacement strength are both relative. A practical approach is to work in units where the radius is 1 and define your atmosphere shell at roughly 1.01 to 1.02, which corresponds to the real 60 to 100 km of visible atmosphere. If your atmosphere is 1.2 times the radius, the planet will look like it is wrapped in fog.
Set the scene unit scale explicitly. Blender's clipping distance defaults are not kind to tiny or enormous scenes, and clipped geometry at the horizon is a classic beginner giveaway.
Subdivision and displacement
Start from a UV sphere rather than an icosphere if you intend to use displacement with a UV-mapped height texture — the UV sphere's pole pinching is a minor issue, whereas an icosphere requires a smart UV project that complicates texture alignment. Use roughly 128 to 256 segments so the silhouette is smooth at 4K, then add a Subdivision Surface modifier before displacement.
For displacement, a Subdivision modifier followed by a Displace modifier fed by your height map is the classic stack. Keep strength low — often 0.002 to 0.005 in unit-radius terms. Over-displaced terrain looks like crumpled foil, not a planet. If you want the silhouette to benefit, you need real geometry; if you only need shading detail, a bump node in the shader is cheaper and often sufficient. A hybrid works well: real displacement at modest strength plus bump detail on top.
Shading Land, Ocean, and Ice
This is where most of the perceived realism lives. A single Principled BSDF with one albedo map will look flat. You want layered control.
Separating water from land
Use your ocean mask as the factor input of a Mix Shader or, better, as a mask driving roughness, specular, and normal strength. Oceans should be smooth (roughness around 0.05 to 0.15), highly specular, and slightly darker in base colour than the albedo suggests, because open water absorbs light. Land should be rough (0.6 to 0.9) with no broad specular highlights except on snow and ice.
If you are using a Principled setup rather than a full node tree, you can still get most of this by plugging the mask into a Color Ramp and driving the roughness socket. The visual difference between the simple and complex approach at 4K is smaller than people expect.
Fresnel and the limb
Water at grazing angles is highly reflective. Add a Fresnel or Layer Weight node to boost reflectivity near the silhouette. This one tweak does more for realism than upgrading your albedo from 2K to 8K, because it makes the planet read as a physical body with an edge rather than a flat disc.
Ice and snow
Ice caps need to be brighter, rougher at micro scale, and slightly blue in shadow. A separate mask or a Color Ramp keyed on latitude works. Avoid pure white; real snow in space photography sits around 0.85 to 0.92 luminance with visible blue in the shadowed regions.
Night-side city lights
Feed your night-lights map into an Emission shader and mix it in using a mask derived from the light direction. The easiest reliable method is a Geometry-based setup: use the dot product of the surface normal and the sun direction, remapped through a Color Ramp so emission only appears past the terminator. Add a slight blur to the emission for bloom-like glow, and let your render's glare or bloom pass handle the rest. Randomly scattering small emissive speckles on the map before importing also helps; real city lights are clustered, not uniform.
Clouds, Haze, and the Atmosphere
The atmosphere is what separates a rendering from a photograph. Two layers do the heavy lifting: clouds and the rim.
A convincing cloud layer
Slice your cloud map into two or three bands at slightly different scales and rotations, then combine them with low-opacity mix nodes. Real cloud systems have macro structure — cyclones, bands, clear zones — plus micro texture. A single tiled cloud texture looks like wallpaper. Using a Principled Volume with the combined cloud map as density, contained in a thin shell around the planet, gives genuinely volumetric clouds that catch light at the terminator.
Keep density low and the shell thin. Thick volumetric clouds turn the whole planet into a wool ball and multiply render times dramatically.
Rim glow and scattering
For the blue limb, the simplest reliable approach is a slightly larger transparent sphere with a shader combining Layer Weight (facing) and a blue-to-transparent gradient. Multiply by the sun direction so the glow appears mainly on the lit side, and add a subtle orange tint where the sun grazes the atmosphere, mimicking Rayleigh scattering at sunset angles. If you want the physically accurate version, volumetric scattering inside a thin shell will do it, but expect a large sample-count cost at 4K.
Lighting, Camera, and Composition
Sun placement
Use a Sun lamp with a physically plausible strength rather than an arbitrary bright value. A strength around 1.0 to 3.0 with a slightly warm white colour (around 1.0, 0.96, 0.9) reads correctly. Angle matters enormously: a three-quarter lit globe shows the terminator, city lights on the dark side, and specular glint on the ocean all at once. A fully lit globe is the most boring and least believable framing.
If you want the sun itself in frame, keep it out of frame or heavily flared. A visible unfiltered sun disc almost always looks like a mistake.
Camera framing and composition
Focal length controls how much the planet feels like a distant object versus a nearby one. Long focal lengths (85 mm and up) compress the scene and give that distant-satellite feel. Wide lenses make the planet look like a ball in a room. Place the camera far back and use a long lens; this also reduces perspective distortion on the cloud shell.
Leave headroom. A globe dead-centre in the frame of a 4K render looks like a test. Offset it toward a corner and let the star field or empty space balance the composition. Depth of field is usually unnecessary and often harmful here — real orbital cameras have enormous depth of field, and everything should be crisp.
Render Settings for a Clean 4K Frame
Samples, denoising, and memory
Start with a low sample count (32 to 64) to iterate on look, then raise it for the final. If you use volumetric clouds or atmosphere, expect the noise to concentrate in those regions; adaptive sampling helps a lot. Enable denoising for the final pass, but always compare a denoised and undenoised crop before committing, because denoisers can smear small city lights into grey mush.
Texture memory is the real constraint at 4K. A handful of 8K maps can exceed the VRAM of a mid-range card. If renders fail or slow to a crawl, downscale the least visually important maps first — night lights and roughness — and keep the ocean mask and height map at full resolution.
Output and colour management
Keep the scene in a linear, wide-gamut working space and let the view transform handle the display conversion. Filmic-style tone mapping tames the specular glint and keeps the bright ice from clipping. For output, render in a format that preserves bit depth for further grading.
Common Mistakes and How to Fix Them
Neon continents. Almost always a colour space error. Albedo must be sRGB; if it is marked Non-Color it will be treated as raw linear data and come out oversaturated.
A visible seam. Equirectangular maps have a longitude wrap. If the seam is visible, either your height map and albedo are offset from each other, or the sphere's UVs are not aligned to the map's zero meridian.
Mountains poking through the ocean. The height map was applied without masking water. Multiply the height by the ocean mask so sea floor relief never displaces upward.
A flat, pasted-on atmosphere. The rim shell is too thick or too uniformly bright. Reduce thickness, increase falloff, and modulate by sun direction.
Clouds that look like a decal. Too few layers, too uniform scale. Add at least two scales with different rotations and make sure they cast and receive light volumetrically.
Oversaturated stars. A star field that is pure white with no colour variation looks generated. Real star fields have subtle colour temperature variation and uneven density.
Noise that only appears at 4K. Small details that look clean at 1080p magnify visible noise at 4K. Raise samples rather than blurring the image.
Performance Tuning and Workflow Variations
If you are working on a modest machine, there are several ways to lighten the load without gutting quality.
- Replace volumetric clouds with a well-shaded alpha-mapped shell. You lose terminator interaction but save an enormous amount of render time.
- Bake the atmosphere rim into the diffuse pass for still frames, and only keep the volumetric version for hero shots.
- Render the planet and the star field separately and composite. The star field needs no expensive sampling.
If you are producing video instead of a still, the calculus flips: at 24 fps, every second costs 24 frames. Use the cheaper cloud shell, drop samples to the lowest acceptable value, and lean on denoising. A slightly softer limb in motion is invisible; consistent noise is not.
Finally, consider whether you need the whole Earth at all. Many of the best-looking shots are partial: a curved limb at the edge of frame, a terminator sweeping across a continent, a night-side city cluster. Restricting the framing lets you spend your resolution and sample budget where the viewer is actually looking.
FAQ
Do I need 8K textures for a 4K render?
No, but you need to know which maps deserve the resolution. Keep the ocean mask and height map sharp; you can downscale night lights and roughness maps substantially with almost no visible loss.
Should I use a UV sphere or an icosphere?
UV sphere for texture-driven displacement, because the UV layout maps cleanly to equirectangular data. Icospheres distribute polygons more evenly but need extra UV work.
How do I make the terminator look right?
The terminator is not a hard line. It is a gradual falloff plus a warm tint from atmospheric scattering. Layer Weight combined with sun direction, run through a soft Color Ramp, gives a natural transition.
Why does my ocean look like plastic?
Usually because roughness is too uniform. Water needs low roughness with a Fresnel boost near grazing angles, and it should be noticeably darker in base colour than the land.
Can I animate this setup?
Yes. Rotate the cloud shell a fraction faster than the globe, animate the night-light mask with the terminator, and keep the atmosphere shell static. The parallax between the three layers is what sells the motion.
How long should a 4K frame take to render?
With simple shading and no volumetrics, a few minutes on a modern GPU. With full volumetric clouds and atmosphere, expect substantially longer, which is exactly why the alpha-shell fallback exists for animation work.
What is the single highest-impact improvement?
The atmosphere rim and the ocean/land separation. Between them they account for most of the difference between a sphere with a map and something that reads as a photograph of a planet.
