There’s something satisfying about watching a flat, boring plane turn into a mountain range.

That’s exactly what a height map does in Unity. With a simple grayscale image, you can shape landscapes, add depth to materials, and create worlds that feel real instead of flat. It’s one of those tools that looks technical at first, but once you understand it, it becomes surprisingly simple and powerful.

In this guide, we’ll break down what a height map is, how it works in Unity, how to use it for terrain, how it differs from normal maps, and how to control it with C#.

What Is a Height Map?

A height map is a grayscale image where each pixel represents elevation.

• Black = lowest height
• White = highest height
• Gray = values in between

Think of it like a topographic map, but simplified into brightness levels. Unity reads this image and uses the brightness values to push parts of a surface up or down.

The result? Hills, valleys, cliffs, and surface details created from a simple image.

Height Maps in Unity Terrain

The most common use of height maps in Unity is terrain generation.

Unity’s Terrain system allows you to import a height map and automatically generate a 3D landscape from it.

How to Import a Height Map into Terrain

1. Create a Terrain: GameObject → 3D Object → Terrain
2. Select the Terrain object.
3. Open the Terrain Inspector.
4. Choose Import Raw under the heightmap settings.
5. Select your grayscale RAW file.

Once imported, Unity converts the grayscale values into elevation data.

If your height map is smooth, you’ll get rolling hills. If it has sharp contrast, you’ll get steep cliffs.

Height Map Resolution Matters

Resolution affects how detailed your terrain will be.

A low-resolution height map creates blocky terrain. A high-resolution height map creates smoother, more detailed landscapes.

However, higher resolution also increases memory usage and processing cost. If you’re building for mobile, balance detail with performance.

Height Maps vs Normal Maps

This is where many beginners get confused.

Height Map

• Actually changes geometry (in terrain or displacement).
• Creates real depth.
• More performance cost if geometry changes.

Normal Map

• Does NOT change geometry.
• Fakes lighting to simulate bumps.
• Much cheaper performance-wise.

If you need real terrain shape, use a height map. If you just want surface detail like cracks or scratches, a normal map is usually better.

Using Height Maps in Materials (Parallax & Displacement)

Height maps are not limited to terrain. You can also use them in materials.

In Unity’s Standard Shader (or URP/HDRP equivalents), height maps can be used for:

• Parallax Mapping – creates depth illusion without changing geometry.
• Displacement Mapping – actually modifies mesh vertices (HDRP).

For example, if you apply a brick texture, adding a height map can make the mortar appear recessed and bricks raised.

Creating Height Maps

You can create height maps using:

• Photoshop or GIMP (grayscale images)
• Blender (baked displacement maps)
• World Machine or Gaea (terrain generation tools)
• Procedural generation with code

The key is keeping it grayscale and avoiding compression artifacts.

Generating a Height Map with Code

You can also generate terrain procedurally using Perlin Noise. This is common in open-world or survival games.

Here’s a simple example:

using UnityEngine;

public class TerrainGenerator : MonoBehaviour
{
    public Terrain terrain;
    public int depth = 20;
    public int width = 256;
    public int height = 256;
    public float scale = 20f;

    void Start()
    {
        terrain.terrainData = GenerateTerrain(terrain.terrainData);
    }

    TerrainData GenerateTerrain(TerrainData terrainData)
    {
        terrainData.heightmapResolution = width + 1;
        terrainData.size = new Vector3(width, depth, height);
        terrainData.SetHeights(0, 0, GenerateHeights());
        return terrainData;
    }

    float[,] GenerateHeights()
    {
        float[,] heights = new float[width, height];

        for (int x = 0; x < width; x++)
        {
            for (int y = 0; y < height; y++)
            {
                heights[x, y] = Mathf.PerlinNoise(x / scale, y / scale);
            }
        }

        return heights;
    }
}

This script generates a terrain using Perlin Noise, which creates natural-looking hills and variation.

Controlling Height Strength

Sometimes height maps look too extreme. Other times they look flat.

In terrain settings, you can adjust:

• Terrain height (Y scale)
• Brush strength (when sculpting manually)

In materials, you can adjust height intensity inside the shader settings.

Small adjustments make a big difference. Subtle depth often looks more realistic than exaggerated displacement.

Common Problems and Fixes

Terrain Looks Blocky

Increase heightmap resolution or smooth the terrain.

Edges Look Stretched

Make sure your height map is square and uses proper dimensions (like 512×512 or 1024×1024).

Lighting Looks Strange

Check your normal settings and ensure lighting is baked or set correctly.

When to Use Height Maps

Use height maps when:

• You need large landscapes.
• You want realistic terrain shaping.
• You’re building procedural worlds.
• You need true geometric depth.

Skip them when:

• You only need small surface detail.
• Performance is extremely limited.

Final Thoughts

Height maps are one of those tools that feel technical at first, but once you use them, they become creative tools.

You’re not just editing numbers. You’re sculpting mountains. Carving valleys. Designing the shape of a world.

Start simple. Import a grayscale image. Adjust the scale. Play with noise. Watch how small changes affect the landscape.

Once you understand height maps, Unity stops feeling like a flat engine. It starts feeling like a world builder.