Pixel art trees

Pixel art trees

Trees are usually the first thing a 2D scene needs a lot of, and the first place repetition becomes obvious.

Tile or sprite, and why it matters

Decide this before you draw. A tree that tiles across the ground is part of the tilemap and sits behind everything. A tree the player walks behind is a sprite with its own depth sorting.

Getting this wrong is behind most of the layering bugs in a first 2D game. The player passes in front of a trunk they should be hidden by, or a canopy draws over a character standing well in front of it.

If a tree needs a collision box, it is a sprite. That rule resolves nearly every case.

Three trees make a forest

You do not need twenty tree sprites. You need three, used well.

Draw three distinct silhouettes, then place each at two or three scales, flip half of them horizontally, and shift the canopy hue slightly between instances. A player moving through the scene reads that as variety. Twenty hand-drawn trees costs seven times the work for a difference nobody registers.

Vertical placement helps more than anything. Trees at slightly different heights break the horizon line that makes a repeated row look pasted.

Seasons come free

A tree is the cheapest seasonal asset in a game because the change is entirely in the canopy.

Autumn is the same sprite with greens swapped for oranges and deep reds. Winter is the trunk plus a bare branch silhouette, with the canopy simply removed. Spring adds a handful of blossom pixels.

Color swap does the recolour across the whole sprite in one pass, so a full set of four seasons from one tree takes minutes rather than an afternoon.

Trunks are where trees go wrong

Canopies get all the attention and trunks are what fail. A trunk that is a straight two-pixel column reads as a pole.

Widen it at the base, give it one kink, and put the shadow on the opposite side to the canopy highlight. That is three decisions and it is the difference between a tree and a lollipop.