Baby and toddler typing: keyboard smash, made safe

Under two, a keyboard is not a writing tool. It is the most responsive object in the room: dozens of buttons, all the same size, all within reach, and every one of them belongs to the machine the grown-ups stare at. A baby pressing keys is running a cause-and-effect experiment, and the experiment only works if the effect arrives instantly and arrives again on the next press.

That is the entire design brief for baby typing, and it is a narrow one. No goal. No losing: points only ever go up. No wrong answer, because there is no question. Press a key on the playground and you get a giant letter A–Z, almost always with a picture of something that starts with it, or a numeral 0–9 with that many little things to count; press anything else — Tab, Space, Enter, a punctuation key — and the same hand-drawn character appears for that key every time. There are 34 characters, and the key-to-character mapping is fixed, which is the part babies eventually notice.

We are deliberately not claiming this makes anyone smarter. What we can say is what the screen does when a key goes down, which is the only thing a parent can actually verify.

Apply these to anything, including ours.

• One action. Press or tap — nothing that needs holding, dragging or aiming. A palm on the keyboard has to count as playing.
• One reaction, instantly. No loading screen between the press and the result, and no ad in between. A delay of a second is long enough for a baby to lose the connection between what they did and what happened.
• No way to lose. No timer, no points taken away, no wrong answer. Failure is a concept for later.
• No way out for the baby, and an easy one for you. The screen should not hand a baby a menu, a link or a settings gear; the parent should be able to leave in one deliberate gesture.

What fails them is worth naming. App-store “baby” games that play a video ad between rounds fail the second test in the worst way: the ad is the most stimulating thing on the screen. A character who looks sad at a wrong answer fails the third, since a baby reads the face, not the rule. Anything with a login form inside the play screen fails the fourth, because a baby finds the form long before you do. And an ordinary laptop desktop fails all four. Babies are not bad at computers; a computer is a bad toy, and a good baby computer game is mostly a matter of removing everything a computer normally offers.

Babies do not play alone, and pretending otherwise is how these sessions go wrong. The version that works is lap play: your baby sits with you, and the laptop sits on a table rather than on a knee.

• Go fullscreen in Chrome or Edge before you hand the keyboard over. The keyboard lock exists only inside fullscreen and only on Chromium browsers, so this is the one step that has to come first.
• Keep the volume where you can talk over it. Sound is feedback here, not a soundtrack.
• Let your baby set the length. We will not pretend to have a screen-time rule for your family; sessions this age are short because interest is short, and that instinct beats any timer we could put on a website.

What to say, what to leave alone and what week two looks like is the subject of how to introduce a toddler to the keyboard; this page stays on what the playground does and where its limits are.

Every press produces three things at once: something appears at a random spot on the screen, it drifts and fades, and a sound plays. For a baby that combination is the reward — visual, audible, and caused by them.

There is a limit to how much stimulation is useful, so the playground escalates on a schedule rather than constantly. Confetti fires every twenty-fifth press and a larger surprise every fiftieth, so most presses stay quiet and simple. If your device is set to reduce motion, the ambient animations on the start screen are skipped entirely; the response to your baby’s own presses stays, because that is the feedback they are pressing for.

One honest caveat about touch. Tapping a key on the on-screen keyboard gives you that letter. Tapping the open background is a different behaviour — it spawns a random letter, numeral, character or emoji where you touched. Fun, but random; it is not standing in for a specific key press.

An older child aims. A baby does not — they land on whatever is under their hand, several keys at a time, repeatedly. That is precisely the input pattern that finds Ctrl+W, F11 and the address bar, which is why fullscreen matters more at twelve months than it ever will again.

Here is what fullscreen actually buys you, stated with the limits intact:

• On Chromium browsers (Chrome, Edge), in fullscreen: the Keyboard Lock API captures normally-reserved shortcuts — Ctrl+W, Ctrl+T, F11 and friends — and routes them to the page, where they just make another character appear.
• On Safari and Firefox: that API is not available. The lock is a harmless no-op there, so those shortcuts still do what they normally do. Use Chrome or Edge if you want the lock.
• On every browser: keys the operating system claims first — PrintScreen, the Windows key, Cmd+Q on a Mac — are handled before the browser sees them, so no website can block them. That is a platform limit, not something we can engineer around.
• Exiting: hold Esc on a desktop — Chrome and Edge leave fullscreen after a second or two of holding, Safari and Firefox on a single press — or hold three fingers for three seconds on a touchscreen, where a ring fills while you hold. That leaves fullscreen and drops you on the playground’s own start screen — the tab stays open.

One more split, about the screen rather than the keys. Desktop Chrome and Edge give the page genuine fullscreen. Safari on an iPhone offers no Fullscreen API to any web page, so there the playground pins itself across the visible area instead: it looks almost the same, without the browser-level guarantees underneath.

The practical version: open the playground in a window that has nothing you care about behind it. Fullscreen plus a Chromium browser is a strong fence, and it is still a fence rather than a vault.

The software side is the easy half. The other half is that babies chew, drip and slam, and a laptop keyboard is directly above the expensive parts. This is ordinary household advice, not a safety guarantee from us — you know your baby and your hardware better than we do.

• A silicone keyboard cover is the single highest value item here. Keys still register through it, and spills and drool sit on top instead of going in.
• A cheap external USB keyboard is better still: the laptop moves out of reach, the sacrificial keyboard takes the abuse, and it is trivially replaceable.
• Watch the small parts. Loose or already-popped keycaps come off easily and are exactly the wrong size to have near a baby’s mouth. Check the board before you hand it over, and stay within arm’s reach.
• Keep drinks off the table for the length of the session. Most keyboard deaths are a cup, not a baby.
• Table, not lap. A flat, stable surface at the right height means a slam lands on the desk instead of tipping a laptop onto the floor.
• Wipe down after, not during. Interrupting to clean mid-session ends the session; a damp cloth afterwards costs nothing.

This deserves a plain sentence rather than a reassuring one: we count how many keys were pressed, never which ones. That running total is batched up and sent to our server, where it feeds the all-time counter on the home screen. The identity of each key — the actual letter your baby hit — never leaves the browser and is never transmitted.

If nobody is signed in, there is no profile for that count to attach to. If a parent has signed in and picked a child nickname, the count is credited to that profile so the Learning Insights view has something to show. Either way, no keystroke content is involved.

The full picture — analytics, advertising, what a paid account stores — is on the privacy page, which is the authoritative version if anything here reads ambiguously.

While your baby plays, the playground shows a points counter in the corner that goes up with every press and never down, because a baby cannot lose at it. Everything else resembling a score waits until you hold Esc (or three fingers) to leave, and then arrives as one card — provided the session registered at least five presses. Below that the exit is silent: a card reading “two keys, four seconds” is noise, not a summary.

• Keys smashed — presses and taps together.
• Duration — from Start to your exit.
• Pace — keys per minute, which for a two-handed nine-month-old is a startling figure.
• Discovered — how many different letters and characters turned up, a rough measure of how much of the board got explored.
• Chaos level — a label that climbs from Just a peek to Keyboard destroyer at 600 presses in one sitting.

The card is calculated in the browser from the session that just ended, and a copy button puts the summary on your clipboard. It can also become a picture to save or share, drawn on your device: we never receive the picture or the first name you can add to it, only a count that one was saved or shared. Smashing feeds the site-wide counter and never a leaderboard standing; the ranked boards are built from game scores.

What the shift looks like from the lap is covered in how to introduce a toddler to the keyboard; here is what sits on the other side of it, with the ages we publish for each game and what it costs to open.

Counting Garden (1–3) and Shape Tap (1–3) are the gentlest step: any tap or any key produces the next flower or the next shape, so a baby who can only smash can still play them. Animal Sounds (1–4) works the same way with animals. Color Splash (1–3) is the first one that asks something back: it names a colour, your child taps the matching one from a few big choices — or presses 1–3 — and the screen floods with it; a wrong tap is simply named and asked again. Bubble Pop Letters (2–5) floats lettered bubbles up the screen; tap any bubble, or press the letter shown on it, and it pops and is named. Nothing calls out a letter to find, and bubbles that get away drift off the top.

All five sit on the free tier and, like the playground, open and play with no account at all. A free parent account, with no card, only adds what an account is for: saved progress, badges and certificates. All five are voice-narrated, so a pre-reader can follow them without you translating.

Where to go next

• Games by age — the ladder from letter-hunting through first words and real typing.
• How to introduce a toddler to the keyboard — a first-session script and the specific mess to expect.
• Typing milestones by age — the sequence from cause-and-effect to real words per minute, with realistic ranges.
• All learning games, tagged by age, or plans and pricing if you want the free-versus-paid split in one table.
• Much later, when “typing game” stops being a selling point: the arcade, 59 original games inspired by the classic genres — a demo run of each with no account, and unlimited play with a free account with a verified email.

The playground opens in a browser tab with no account, no download and no card. Put it fullscreen in Chrome or Edge, sit your baby on your lap, and press one key to show them how it works. They will take it from there — that was always the plan.