Roadmap

Where Natsura is heading

Leaving Early Access and how we will reach Natsura 1.0

Release 6 of 7. Use the left and right arrow keys to move between releases.

0.8Next(In progress)

The finished tree

Q4 2026

0.8 is about everything that sits on top of the skeleton. A tree can go from a seed, a scanned trunk or a SpeedTree tree to a rigged export inside Natsura.

A tree is built in stages. Simulate grows the skeleton. Decorations mesh the wood and place leaves and parts. The export sends the rigged tree to Unreal.

In 0.8 the whole tree is meshed as one surface with shaped junctions and branch ends. Bark is built from stacked layers. Leaves and clusters share one placement engine. Growth gains pruning with regrowth, a natural width model and stiffness for wind. The growth engine is substantially faster.

We listen closely to your feedback and requests, so please keep it coming. Based on your input, 0.9 and 1.0 will be filled out more completely.

Examples shipping alongside

  • Mapping and Effector Zoo
  • Leaves and Clusters Zoo
  • Assemblies Zoo

Documentation

  • Meshing
  • Surfaces
  • Leaves and clusters
  • Growing
  • Shaping
  • Mapping
  • Environment
  • Node help
  • GrowthPlanned

    Pruning and regrowth

    Prune branches by chance, or let a map such as height or shade decide. A delay sets when the cuts happen, and a seed rerolls them. Growth beyond a cut dies back. New growth can sprout from each cut. The prune map has presets for common cases. The mesher knows a cut tip is a broken end and caps it to match.

  • GrowthPlanned

    Forks and buds

    Forks trigger by probability, frequency or count. An offset holds back the first fork. Fork spread and whorl angle set how new branches fan out. Crowded branches at a fork are pushed apart. A child never grows inside its parent, even when it leaves at the parent's angle.

    Buds are spaced by interval or by count. An internode is the stretch of stem between two buds, and an interval below one places several buds on each.

  • GrowthPlanned

    Phyllotaxy presets

    Phyllotaxy is the pattern buds follow around the stem. It now has presets:

    • Spiral at the golden angle
    • Alternate in two ranks
    • Spiral 2/5 and 3/8
    • Opposite
    • Decussate
    • Whorled
    • Custom

    You can save your own settings as a preset.

  • GrowthPlanned

    Width and open space

    Width has three modes. Taper narrows from base to tip as before. Absolute sets the width directly and can be mapped. Natural is the new default. It splits each branch's width between its children at every fork, so widths stay plausible across the tree. A tip width can be a fraction of the base, a width in metres or a share of the trunk base. Each grow can use its own mode.

    A new effector turns tips away from shade and toward open space. It also outputs how open each part of the tree is as a map.

  • WindPlanned

    Wind from viewport to Unreal

    Wind in the viewport now looks similar to wind in Unreal. Sun, sky and wind are set in one place. Wind presets follow the Beaufort scale. Light presets are built in. You can save your own. Gusts travel across the ground so neighbouring trees move together.

    Each part of the tree has a stiffness that sets how far it bends. Thick wood holds and twigs move. You can change stiffness without regrowing the tree. Later it will also drive sag and other deformations.

    This builds on two 0.7 builds. 0.7.2 added a wind preview on the display toolbar. 0.7.3 added Wind Config, which sets a stiffness for each wind layer in Unreal.

  • MappingPlanned

    Effectors and maps across the tree

    A map is a value that varies across the tree, such as height or age. An effector steers how branches grow. Noise, gravity and direction effectors now sit in the growth graph on a new Shaping tab. Their strength can be mapped, so each part of the tree bends by its own amount. Enhance Shape is on every grow. Gravity works in every effector slot. Shape effectors reshape branches after they have grown.

    You can colour the tree while you edit. Colour it by branch order, height or width. Or show any attribute or map.

  • MappingNew nodeExperimental as of 0.7.2.0

    Shader-graph-style map nodes

    Map nodes work like the functions in a shader graph. You can build a map without writing VEX. Map Remap remaps a value. Map Blend gains a Mask input and six more modes. Map Wrangle writes a map in VEX in the same way as a custom effector. See Mapping.

    Status:The first nodes are in.

  • ShapingExperimental as of 0.7.1.0

    Post-process stage on Simulate

    After growth, Simulate can refine the branches before they are meshed. It adds substeps and smooths the curves. It also has its own effector stack. Every decoration inherits the refined shape, so leaves and parts stay on their branches. See Simulate.

  • ShapingExperimental as of 0.7.1.0

    Natsura Shape

    Shape reshapes a tree after it has grown. It does not run the simulation again. A stack of effectors deforms the rig and its geometry, so branches and leaves bend together. See Drawing a Tree.

  • Learning & contentPlanned

    Example zoos

    New example scenes show every setup side by side. They open from the Project Browser.

  • MeshingPlanned

    Junction shaping

    Every branch is stitched into its parent. The tree comes out as one connected surface instead of intersecting tubes.

    Each junction is a premade mesh. Blend spaces deform it live to fit the branch angle, the child's width against its parent and whether the branch is dead. The type is picked from the simulation, and you can override it. You can sculpt your own junctions in ZBrush or Houdini. You can also project a scanned junction into the same space. Thin twigs sink into a socket. Larger branches lift into a collar and flare. Heavy limbs carry extra wood underneath.

    The flare runs from a ring on the parent's surface to a ring on the child. Overlapping junctions merge, and the largest outward push wins instead of a dent. Crotches between close branches fill with a web. The parent's UVs carry into the flare so the bark pattern runs on into the branch. Footprint and crotch size are mappable. Junctions have their own density, so you can add detail there alone.

  • MeshingPlanned

    Branch ends

    Every branch ends in a cap. A cap is a living tip, a pruning cut or a break with splinters. Breaks can be hollow where the wood has decayed. Caps use the same blend spaces as junctions and are picked by the branch's size and decay. A scanned cap can be projected in. Caps have their own density. Their length and decay are mappable.

  • MeshingPlanned

    Any cross-section

    A branch can take any closed outline as its cross-section. The outline can be drawn as a curve, generated from lobes and ridges or taken from a scan. New growth starts on a scanned trunk's exact outline and keeps its ribs. Further up it eases toward round. One profile can blend into another along a branch. A trunk can be built as a stack of profiles.

  • MeshingPlanned

    A new sweep

    The sweep turns each strand into a tube mesh. A strand is a branch's centre curve. The sweep is rebuilt as a single pass over the whole tree.

    One resolution slider sets the density of the whole tree. It replaces many separate sliders and it is mappable. Rings are spaced by one step length in world units. Quads stay square and texel density stays constant from trunk to twig. Ring resolution scales with branch radius so thin branches carry fewer edges.

    UVs run by arc length along the strand and by perimeter around the cross-section. Texture scale holds on any profile. The cross-section also responds to load. It widens under heavy children and flattens between them.

  • MeshingShipped in 0.7.1.0

    Progressive sweep

    Surface Decoration sweeps each branch at a resolution that can change along its length. Density is mappable. The trunk can be dense and the tips light. See Surface Decoration.

  • SurfacesPlanned

    Bark in layers

    Build the bark as stacked layers. A bark layer can have a wood layer under it, which shows where the bark rips. Moss or lichen can sit on top. Each layer is placed by a property of the tree such as age, width or height. Buildup layers add on top and erode layers cut in. Moss can settle into the low spots of the bark. Junctions and branch ends can each have a surface of their own.

    The layers are built into the mesh. They are not blended in a shader. The bark is cut along each layer's border, and every face belongs to one layer and carries its material. Each layer has its own relief height, so moss sits proud of the bark and a rip drops below it. Borders get a band of finer faces where the height eases from one layer to the next. Relief such as ridges, plates and scales wraps around each branch.

    The result is plain geometry with ordinary materials. Your engine needs no custom layered shader. Each layer's material holds its textures and shader settings. One texture file fills the rest by matching names, and textures can be baked to disk.

  • SurfacesPlanned

    Scattering on the surface

    Scatter decals and small geometry over the trunk and branches, such as knotholes, moss and splinters. Placement covers the whole surface or runs in rows along a branch. Spacing is mappable. Size and displacement scale with the branch. Decals cut the bark under them and avoid each other. Their edges tuck into the bark.

  • SurfacesPlanned

    Colour on the surface

    Tint the trunk and branches with colour effectors, maps and ramps. Each junction carries a gradient mask. Export it to Unreal to blend materials across the joint.

  • SurfacesShipped in 0.7.1.0

    Surface Decoration overhaul

    Surface Decoration is the node that meshes the wood. It gained surface effectors, so any effector can displace the surface. It also gained mappable width, strand resampling before meshing, end caps, displacement and separate U and V scale. Assembly Decoration got its own effector stack in the same build. See Surface Decoration.

  • SurfacesShipped in 0.7.1.0

    Material bindings

    Materials now come through on instanced parts. Before, only the trunk arrived bound. The material list updates itself before every export. See Nanite Skeletal Assemblies.

  • Foliage & instancingPlanned

    Leaves from atlases and your own geometry

    The atlas workflow now lives in one place. It cuts leaves from a texture sheet. Your own leaf geometry goes through the same steps. Each leaf gets a mesh, a midrib traced from its shape, a pivot and joints to bend on. You can redraw a midrib by hand and scale leaves against a ruler. Each leaf can be tagged with its age and size.

  • Foliage & instancingPlanned

    One placement engine for leaves and clusters

    Clusters are small leafy twigs placed as one piece. Leaves and clusters are now placed by one shared engine, so every placement works for both. Leaves bend along their twig or stay rigid. They sit along a twig, at its tip or at its junctions. They are picked by size and age. Placed leaves can be grouped by shape and turned into shared instances. A tree for a game then keeps only a small set of unique leaf meshes.

  • Foliage & instancingShipped in 0.7.2.0

    Clusters Decoration 2.0

    Clusters Decoration places leafy twigs on the tree. Version 2.0 has a simpler interface and new internal utilities. They lay the groundwork for mapping and effectors. Clustering utilities let you pick from existing libraries or regenerate the clustered parts. Clusters Decoration 1.0 stays so older scenes keep working. See Clusters Decoration.

  • Starting a treePlanned

    Growing from any trunk

    Start a tree from any trunk through one entry point. The trunk can be a scan, an imported assembly or a procedural trunk. A scan plugs straight into Simulate as the seed. The same input takes a Natsura tree or a SpeedTree tree to grow on. A procedural trunk has controls for flare height and spread. The scan mesh passes through into the finished tree. A multistem trunk grows a tree from every stem.

    The scan's rig is computed for you, and you can edit it with Scan Rig. Assembly Unpack opens the result into its geometry, rig and profiles.

  • Starting a treePlanned

    SpeedTree import

    Import a whole SpeedTree tree as a Natsura tree. Joints sit where each branch leaves its parent. Wood is skinned up to a chosen branch order and smaller parts stay rigid. Repeated meshes become shared instances, including rotated copies. You can then reshape the tree, break it into reusable branches, simplify it or export it to Unreal.

  • Starting a treeNew nodeExperimental as of 0.7.0.1

    SpeedTree skeleton import

    Bring in the curves of a SpeedTree tree exported as USD. Then grow on them, decorate them and reshape them like a grown tree. Only the curves come in. See Drawing a Tree.

    Status:Experimental, and still a bit rough.

  • Starting a treeNew nodeExperimental as of 0.7.0.1

    Drawing a skeleton by hand

    Draw a tree's branches by hand with Houdini's Skeleton node. Pass them through Custom Module. Then grow on them, decorate them and reshape them like a grown tree. See Drawing a Tree.

    Status:Experimental, and still a bit rough.

  • Foliage & instancingPlanned

    Branches as reusable parts

    Break a grown tree into branch modules and keep one of each kind. Place them on another tree as assemblies. An assembly is a set of rigged parts, and these still sway in the wind. Plain geometry can be rigged into parts in the same way. Parts from a library can be fitted to a tree's own branches.

  • Foliage & instancingExperimental as of 0.7.1.2

    Merge Assemblies

    Merge Assemblies combines several assembly libraries before the decorator. One Assembly Decoration can then draw on all of them. See Assembly Workflow.

  • Foliage & instancingExperimental as of 0.7.2.0

    Assembly Inspect

    Assembly Inspect shows an assembly's polycount, instance count, joint count and more. The assembly passes through unchanged. See Assembly Workflow.

  • Foliage & instancingExperimental as of 0.7.2.0

    Simplify Assembly

    Simplify Assembly reduces an assembly's polycount. LOD chains come with LOD generation, planned for 0.9 and 1.0. See Assembly Workflow.

  • Export to UnrealPlanned

    Vertex colours and extra UV sets on export

    The export writes vertex colours and extra UV sets with each part so they reach Unreal. Materials with opacity import as Masked.

  • Export to UnrealShipped in 0.7.1.0

    Batch export, with USD as layers

    Export a whole library of trees at once. Import it into Unreal from one root file. Shared parts go in parts/. Each tree gets its own layer and wind file in assemblies/. See Nanite Skeletal Assemblies.

  • Export to UnrealShipped in 0.7.3.0

    Export node rework

    The export node has a Simplified mode for everyday exports. It adds versioned folders and naming. Materials can be renamed or linked to ones already in Unreal. Save to Disk checks the export first. Bones now point along their branches as Unreal's Dynamic Wind expects. See Export Unreal Nanite Assembly.

  • Core enginePlanned

    Simple Tree opens in 13.6 seconds

    On the Simple Tree example our development build opens and cooks the scene in 13.6 seconds. 0.7.4 takes 24.7. A regrow after an edit takes 1.6 seconds against 4.2.

    Three changes do most of it. Nodes no longer reload unused definition data when a scene opens. The growth graph is smaller and compiles faster. Branches no longer carry each other's inactive points through every growth step. Cooked trees are kept in a scene cache, and an edit recooks only the tree it changes.

  • Core engineShipped in 0.7.0.3

    Speed-ups across 0.7

    Speed-ups across the 0.7 line:

    • 0.7.0.3: wrangles cook faster.
    • 0.7.1: selecting a node in a scene with a thousand Natsura nodes takes 0.6 seconds instead of 3.8. The Spans panel refreshes in milliseconds instead of over a second.
    • 0.7.4: Simple Tree opens and cooks in 24.7 seconds instead of 40. A regrow takes 4.2 seconds instead of 5.0. Growth output is the same as in 0.7.3. These are the smaller speed-ups from the 0.8 engine work, brought back early.
  • InterfacePlanned

    A toolbar in build order

    The toolbar is grouped by the stage of the build. N opens every tool at the mouse. A floating hub can stand in for the toolbar. Hovering over Simulate shows a quick toolbar for it. Each input pin offers the tools that fit it, and pins are coloured by data type. A tool can be dropped onto a wire.

  • InterfaceShipped in 0.7.2.0

    Project Browser

    The Hub, Projects and Examples panels are now the Project Browser. It has collections, favourites and project versions. Opening an example opens a copy as a new project. See Interface.

  • Core engineShipped in 0.7.4.0

    Better upgrades from 0.5 and 0.6

    Scenes made in 0.5 and 0.6 now upgrade much closer to how they looked. More of their fork, prune and decoration settings carry over. If an old scene does not come through well, send it to us.

  • Core engineShipped in 0.7.1.0

    Houdini 22 support

    Natsura runs on Houdini 22. Before, it failed to start without saying why. Setup still marks Houdini 22 as untested. See Installation.

  • LicensingShipped

    Education licences

    Education licences for schools and universities, which also cover their students. Details on the pricing page.

    Launched:October 2026

  • LicensingShipped

    Site licences

    Site licences for studios, covering everyone at one location. Details on the pricing page.

    Launched:October 2026

  • Learning & ContentShipped

    Natsura Store

    A store with content you can use in Natsura. A free asset shows how assemblies are set up. A free trunk scan comes next, then scanned tree packs.

Get started

Sign up for Natsura and start creating stunning foliage today

Join the Natsura community and join other artists and developers in the conversation.

“I workshopped something in Houdini. It worked enough for a release or two, but was never going to hold long-term, so that's how I found you guys eventually. Much easier.”

Joseph Bardolph

“Natsura's power comes from its ability to give artists full creative freedom over the final results. Leveraging a combination of simulated, procedural and manual artistic input has allowed us to get past the generative look that would otherwise hold us back on our quest to create truly photo-realistic natural environments.”

Johan Stoerkersen, Founder, Apex Nature

“I love Natsura's approach of combining simulation with parametric control - the developers are passionate and it shows in the product.”

RealBiomesJan Klasen, Co-Founder - Realbiomes

“Natsura is a groundbreaking new approach to an age old problem in video games and film- how do artists create non-cookie cutter realistic foliage that doesn't compromise. To me? Natsura is to technical artists what C was to programmers, and personally, I am excited to see it grow.”

Lillian Salehi, Environment Artist

“i love that we can make all kinds of trees with the tools”

Lea Kronenberger, 3D Art Lead - Frictional Games