Your child has outgrown Scratch. What next?

By The Code Zone team · 28 June 2026 · 5 min read

Most children who have outgrown Scratch have not outgrown Scratch

This is worth saying before anything else, because getting it wrong costs children years. Scratch's ceiling is far higher than almost anybody who has hit it realises. People have built raycasting 3D engines in it. Platformers with dozens of levels, working physics, save systems and scrolling worlds. Playable recreations of Mario and Pokémon. There are Scratch projects on that site that would take a professional developer a fortnight just to plan.

So when a ten year old tells you they have done everything Scratch can do, what has usually happened is not that they found the edge of the tool. They found the edge of what they can reach on their own, with nobody there to show them what the next rung even looks like. A child who has never met an array will genuinely believe an inventory is impossible.

A child who has never been shown custom blocks will rebuild the same twenty blocks nine times over and conclude that the language is the problem.

That is not a ceiling. That is the absence of somebody standing next to them saying "right, now try it this way".

It matters enormously which one you are looking at, because they need opposite responses. If the tool really is the limit, a new language helps. If the guide is the limit, a new language actively makes things worse: you take a child who felt capable, hand them a blank file and a syntax error, and the thing they were actually missing is still missing.

How to tell the difference

• Ask what they would build if anything were possible. If they describe something concrete that Scratch genuinely cannot do (proper 3D, a real multiplayer server, something that runs on a phone), the tool is the limit. If the answer is "I don't know, I've done it all", it is not.
• Show them somebody else's ambitious Scratch project and watch their face. "How did they do that?" means there is a long way left to go. A shrug means there might not be.
• Ask how they would store a high score table, or make an enemy chase the player. If you get a plan, they are ready for more language. If you get a shrug, what they are short of is ideas, and a new language will not supply those.
• Notice whether they are bored or stuck. Bored children have run out of challenge. Stuck children have run out of help. They look almost identical from across the room and they need completely different things.

Working out which of the two you are looking at is a mentor's first job with any new child. They spend the early sessions finding out what a child has simply never been shown, and moving them up or down levels until the work actually fits.

It is nearly always a lot more Scratch than anyone expected, and watching a child realise their favourite tool had another two years in it is one of the better parts of the job.

An honest look at the options

If you have been through all that and they genuinely have hit the edge of the tool, here is the honest survey.

MakeCode is the step most people skip. It still uses blocks, but those blocks map onto real JavaScript and Python that your child can flip to and read side by side. For a child who is confident in Scratch but not ready to type everything from scratch, it does the translation work instead of asking them to make the leap cold. It is free, and it is where our own members usually go next.

Python is the destination for most children from around age 10. The jump from blocks to typed code is real, and syntax errors are a new kind of frustration, but Python keeps that frustration small. Everything they learned in Scratch (loops, conditions, variables, events) transfers directly.

TypeScript after that, if they stay with it. Fewer clubs take children this far, which is a shame, because it is the point where a child stops making games that look like exercises and starts making games. It is also a language plenty of them will meet again if they ever work in software.

Minecraft modding, if they already live in Minecraft. Minecraft Education has a code editor built in, and writing a mod your friends can play on your world is close to the most motivating thing available to a nine year old. It is a genuine route rather than a gimmick.

The ones we would not pick as the immediate next step. Roblox and Lua come up constantly, and the motivation is real because friends can play what you build, but Roblox Studio is a professional-grade tool with a steep curve, and children working through YouTube tutorials alone often end up copying without understanding.

Godot and Unity are where teenagers with a serious game-making itch eventually land, and both are excellent, but there is far too much happening at once for a child straight out of Scratch. We do not teach any of the three ourselves, so take that as an opinion rather than a pitch.

The thing that matters more than the language

The move from Scratch to typed code is where most children quit. It isn't that typed code is too hard. The first few weeks just feel like going backwards: in Scratch they were capable, and suddenly they're beginners again, with a missing colon breaking everything.

What gets children through that dip is someone alongside them who can spot the problem in seconds and turn it into a lesson rather than a wall.

That's essentially what our clubs are for. At The Code Zone, children move from Scratch to Python (and on to TypeScript) through a level system, building their own games the whole way, with a mentor in a small group who knows exactly where they are. For our members, the transition that ends most children's coding is just the next level.

If your child is at this crossroads, they can try a session with us for free. Book a taster and their mentor will meet them exactly where Scratch left off.