Move a 3D player with the keyboard in Unity

Keyboard movement is one of the first patterns many learners want to build because it makes a 3D scene feel interactive right away. Unlike a passive demo, movement lets you test your own input, feel the response, and judge whether the controls seem stable or awkward.

This lesson focuses on a readable approach using CharacterController and Input.GetAxisRaw. That combination is practical for beginners because it keeps movement code explicit. You can clearly see where input comes in, how a movement vector is created, and how it becomes actual motion in the scene.

• Read horizontal and vertical input from Unity's standard input axes.
• Turn two input values into a normalized 3D movement direction.
• Move a player with CharacterController without immediately dealing with full Rigidbody physics.
• Rotate the player toward the movement direction so the result feels more natural.

• A player object with a CharacterController component attached.
• A visible floor or platform so movement direction is easy to judge.
• Basic knowledge of the difference between local forward and world forward.
• A camera angle that lets you clearly see whether the player turns and moves correctly.

using UnityEngine;

public class KeyboardMove3D : MonoBehaviour
{
    [SerializeField] private float moveSpeed = 5f;
    [SerializeField] private CharacterController controller;

    private void Update()
    {
        float x = Input.GetAxisRaw("Horizontal");
        float z = Input.GetAxisRaw("Vertical");

        Vector3 move = new Vector3(x, 0f, z).normalized;
        controller.Move(move * moveSpeed * Time.deltaTime);
    }
}

• Input.GetAxisRaw gives direct values without smoothing, which makes the beginner behavior easier to observe and explain.
• Normalizing the vector prevents diagonal movement from becoming unintentionally faster than single-axis movement.
• CharacterController.SimpleMove or Move handles practical movement nicely for this stage before you step into more advanced physics-driven controllers.

• WASD or arrow keys move the player.
• Diagonal speed is controlled by normalizing the movement vector.
• Movement logic is readable enough to extend later with jumping or camera-relative input.

• Make the movement camera-relative instead of local-forward relative.
• Add a sprint key that temporarily increases moveSpeed.
• Introduce a jump later and compare how CharacterController changes your vertical movement logic.

• The heart of keyboard movement is simple: read input, build a direction, normalize it, then move with a stable speed.
• CharacterController is a useful educational stepping stone between static scenes and more advanced player systems.
• Once this movement is comfortable, adding jump, sprint, camera-relative control, or animation becomes much easier.