World Creator 4 Aims for Planetary Terrain

For those who don’t know the tool: World Creator is BiteTheBytes’ standalone terrain generator for games and VFX. It combines GPU acceleration with procedural filters, manual sculpting, terrain stamps and object scattering. Artists can shape a landscape, dress it and inspect its lighting with the integrated path tracer before moving it into a production scene.

A larger brief for the terrain department

World Creator 4 is planned for November 2026, with a Cloddy SDK-based architecture intended to take terrain generation to planetary scale. The announced workflow includes height and distribution data exportable for spherical mapping. Apparently, the environment brief now includes the other side of the planet. Nodes will supplement layers, while direct heightfield sculpting will dispense with the previous level-step system. New erosion, water and sand models, distribution controls and more than 110 noise types are also planned.

The announced renderer changes add a polygon-based realtime option alongside path tracing, with DLSS 4.5 support for both. Batch processing and an MCP server for external AI control are planned, as are macOS and Linux versions; Linux readiness remains a launch target. MapTiler streaming is on the roadmap, although its place in the initial release is still unclear.

Keep the handoff in the picture

Our earlier World Creator 2026.4 coverage examined expressions, decals and terrain normal blending. Version 4 raises the scale of the brief, but the handoff remains gloriously terrestrial: the landscape still needs to arrive in the application where the shot or level gets finished. A mountain imported at the size of a paperweight is technically a delivery, just not a particularly useful one.

The existing Bridge Tools documentation describes a file-based transfer. Sync exports terrain data and maps; the destination bridge reads them and builds scene assets. Its XML carries resolution, terrain dimensions, minimum and maximum height, tile counts and splat-layer information. Heightmaps use raw unsigned 16-bit data, colour and texture maps use PNG, and splat maps use TGA with up to four layers in RGBA channels. That distinction matters when writing an importer: these files carry different parts of the terrain, rather than interchangeable pictures of the same hill.

The guide lists bridges for Unreal Engine, Unity, Blender, Cinema 4D and Houdini, and explains the data layout for custom integrations. This is documentation for the existing workflow, not a specification for version 4’s planetary export. For pipeline teams, it provides a concrete baseline against which to evaluate the new build.

Current licences, future release

The current manufacturer price list offers Indie at US$149 perpetual or US$59 annually for annual revenue or funding below US$100,000. Professional costs US$289 or US$99 annually for individuals and single-person businesses with revenue up to US$200,000. Studio costs US$499 or US$179 annually for companies with multiple employees and revenue up to US$1 million; Enterprise costs US$1,499 or US$529 annually for organisations above that threshold. Taxes and VAT are added at checkout according to location.

Perpetual purchases include 12 months of updates and support; subsequent maintenance is optional, while the last-installed version remains usable. The licence lasts; the complimentary updates have a calendar. These are current store terms, not a separately verified version 4 launch offer.