How do I introduce children to D&D without overwhelming them?

Start playing before you teach the rules

The rules examples here use the 2024 D&D Free Rules. If your table uses the 2014 rules, use the 2014 Basic Rules as your reference instead; some terms and character features differ. The DCs and creature statistics below are examples for this adventure, and the optional simplified turn order is a teaching choice rather than the standard combat procedure.

A first session for children aged roughly 8 to 12 fails most often before play begins, when character creation, dice notation and a long explanation of actions take the whole sitting. Children learn D&D the same way they learn a playground game: by taking a turn, seeing what happens, and taking a better turn next time. Your job in session one is to protect that loop and keep every child making decisions.

Open in the middle of a small problem, not at the start of a campaign. Say where the characters are, what has just gone wrong, and what they can see. Then ask one child: what does your character do? Accept answers in ordinary language. A child who says "I hide behind the barrel and watch the bridge" has understood the game, even if they have never heard the words Hide action or Stealth check.

Keep the first explanation brief. Name the twenty-sided die (the d20), point to the big modifier numbers on the character sheet, and explain that you will tell them when to roll. Everything else can wait until it matters at the table.

Introduce the rules in stages

Teach each rule at the moment a child needs it. The stages below follow the order most groups meet them in play:

• Stage 1: the basic conversation You describe a situation, the player declares what their character tries, and you describe the result. No roll is needed when the action is easy, impossible, or has no interesting cost for failure. "I look under the bridge" needs no roll if the lantern light is plainly visible underneath it.
• Stage 2: the ability check When the outcome is uncertain and failure changes the situation, ask for an ability check. The child rolls a d20 and adds the modifier you name. For example, crossing the slippery stones under the bridge might call for a Dexterity (Acrobatics) check against Difficulty Class (DC) 11. A roll of 13 plus a +3 modifier gives 16, which meets or beats 11, so the character crosses without slipping. On a total below 11, do not end the child's turn in embarrassment: they slip into ankle-deep water, make a splash that alerts whoever is below, and can still act from there.
• Stage 3: the attack roll, only if a fight happens An attack roll also uses a d20, but it is compared with the target's Armour Class (AC), not a DC you set for a task. If a giant fire beetle (AC 12) lunges at the party and a child swings a shortsword with a +4 attack bonus, a d20 roll of 9 gives 13, which hits. Only then roll damage: 1d6 plus 2, so a four on the six-sided die deals 6 damage. A miss deals no damage; the character can use any remaining movement or available actions before their turn ends. Do not teach this sequence before the first fight, and do not require a d20 roll before every damage or healing effect: a spell or item does exactly what its description says.
• Stage 4: the saving throw, when something happens to them A saving throw is a d20 roll your players make to resist an effect, such as a Dexterity saving throw to jump clear of a falling lantern. Name the difference in one sentence: a check is for something you try, a saving throw is for something you resist, and an attack roll is for hitting a creature. That distinction is enough for session one.
• What to leave out for now Full initiative order, the complete action list, spell slots and spell preparation, opportunity attacks, conditions and levelling can all wait. Say so plainly: "We are leaving those out today so we can play. We will add them when we need them." Temporarily omitting a rule is a teaching choice, not a mistake, provided you are consistent within the session.

Use pregenerated characters children can read at a glance

Build or borrow pregenerated characters and let each child choose by picture, job or favourite tool rather than by statistics. A readable sheet for this age group puts the character's name and one-line description at the top, followed by the three numbers they will use most (Armour Class, hit points and speed), their main attack or useful trick, and one special ability written as a plain sentence. For example: "Pip the rogue can hide as a bonus action and carries a coil of rope" tells a child more than a dense list of class features.

Offer three or four characters with obviously different jobs: one strong and sturdy, one sneaky and curious, one with a small amount of magic, and one who helps and heals. Give each a helpful item (rope, lantern, snack for an animal, small healing kit) so every child has something to contribute outside combat. Let children rename the character, choose how they look, and decide one thing the character likes. That small ownership matters more than an optimised build.

Do not ration choices. A simple sheet should make the first decision easy, not limit what a child may attempt. If a child asks whether their fighter can sing to the creature under the bridge instead of fighting it, the answer is yes: decide whether a Charisma (Performance) check is needed and play the result. An older or confident child who wants the full sheet, more spells or the job of tracking initiative should be allowed to take that on. Judge confidence child by child rather than by age alone: some eight-year-olds will track hit points happily, and some twelve-year-olds would rather describe actions and leave the numbers to you.

Running a mixed-age table without losing anyone

• Go round the table in the open Outside any fight, ask each child in turn what their character does before resolving any of it. Quiet children get a protected moment to speak, and confident children learn to build on a sibling's idea rather than replace it. In a short fight, keep the same round-the-table order so nobody has to learn initiative to take part.
• Plan for shorter attention, not lower ability If attention wanders, try changing the kind of problem or offering a small job, such as holding the map or rolling for the group, rather than giving a recap lecture. End on the planned closing beat even if you skip a middle detail.
• Use visual aids as props, not requirements A hand-drawn bridge, a few counters or figures, and dice each child can hold all help younger players follow where everyone is. They are optional. A sketch on scrap paper does the same job as a printed map, and a character can be a named bottle cap.
• Reward helping over winning Praise plans that combine two characters' abilities, and let a child who helps another add encouragement even before you teach any formal help rule. If one child dominates the dice, give the next decision to a different child by directing the question to their character specifically.
• Handle setbacks gently and briefly A failed roll should change the situation, not punish the child. Slipping on the stones means wet socks and a splash, not injury and ridicule. If a character is ever hurt, describe it plainly and move on. Keep any character from being knocked out in session one: at low hit points, have the opposition back off, flee or accept surrender instead.

Agree comfort boundaries before the dice come out

Before play, tell the adults and children involved what kind of story this is: a friendly adventure where the characters help people, nobody has to fight if they would rather talk, and any player can pause the game. Ask directly whether anything should stay out of the story, such as spiders, deep water, or being chased. With children, keep this short and concrete rather than formal. "If anything feels too scary or not fun, say pause and we will change it" is a complete safety rule for a first family session, and you must honour it the first time it is used so the children learn it is real.

Be clear that characters can be in pretend danger without anything bad happening to the player, and agree what happens if a character is badly hurt. Many family tables rule that characters get knocked down, captured or chased off rather than killed, at least until the group decides together that they want higher stakes. Do not assume every child enjoys fighting: the lantern adventure above can be finished entirely by following tracks, crossing stones and talking, and a child who prefers that route should reach the same happy ending as one who wanted the beetles.

Finish by asking each child what their favourite moment was. That tells you what to offer more of next time and ends the session on their choices rather than your narration.

Starter kits and maps are resources, not a checklist

If you already own a starter set, the Player's Handbook or a published adventure, you do not need to run all of it, in order, before the children are allowed to enjoy it. Take one small piece: the first location, one friendly non-player character (NPC), or a single map, and run only that portion with the staged rules above. A starter adventure's opening scene works well if you cut the first fight down to one or two opponents and let the party talk or sneak where the text assumes combat.

Nothing extra needs to be bought for session one. Dice can be shared or rolled with a free dice roller, characters can be handwritten on index cards, and the bridge in the adventure above can be three books on the table. Buy or print more only when the children ask to play again and you know what actually slowed your table down.

Minimum preparation checklist

Use this as a minimum preparation list. Add detail only where your group needs it:

• A three-sentence premise you can read aloud: what has gone wrong, where the trail leads, and who is involved. The lantern premise above is ready to use as written.
• One simple map or sketch: a market square, a river and a bridge on one sheet of paper is enough.
• Two or three NPC details each: Mina the baker is worried and kind and saw a small figure at dusk; Bram is frightened of the dark, sorry, and will cooperate if treated kindly.
• Pregenerated characters, one per child plus a spare, each with a main attack or trick and one helpful item written in plain language.
• The slippery-stones check (Dexterity (Acrobatics), DC 11) and, if you use the optional fight, the two beetles' custom statistics (Armour Class 12, 4 hit points each, +2 to hit, 1d4 plus 1 damage). Only one beetle attacks each round. Bram cooperates when treated kindly; no roll is needed for that response.
• One d20 per child if you have them, a spare six-sided die for damage, and pencils. Shared dice are fine.
• A clear ending and a sentence that closes the session when you get there.
• A pause rule the children have heard before play starts, and your decision that no character will be killed in this first session.