Skip to main content

🧭 Lesson 1.2: A Guided Tour of the Scratch Editor

Open Scratch and let's walk through every panel together. By the end, nothing on the screen will feel mysterious β€” and you'll know exactly what to point at when your child asks "what's that?"

πŸ“š What You'll Learn

By the end of this lesson, you will be able to:

  • Open the Scratch editor (with or without an account)
  • Name the four main areas of the editor and what each does
  • Find any block using the colored category menu
  • Use the green flag and stop button
  • Save your work and set up a safe kid account

Estimated Time: 30 minutes  β€’  Best done: at a computer, following along

Ages 5–7 (with help) Ages 8–11 Ages 12+
In This Lesson

πŸŽ“ Learn It: Opening the editor

Go to scratch.mit.edu and click β€œCreate” at the top-left (or the big β€œStart Creating” button). That's it β€” the editor opens with the friendly orange cat waiting for you. You don't need an account to start playing.

βœ… Account or no account?

Without an account: you can build and test anything, but your project won't save automatically. Great for a first look.

With a free account: projects save to the cloud and can be shared. We'll set one up safely at the end of this lesson.

πŸŽ“ Learn It: The four areas (your map)

The editor looks busy at first, but it's really just four zones. Learn these and you've learned the editor.

The full Scratch editor with four regions: the blocks palette on the left, the empty coding area in the middle, the stage with the cat on the upper right, and the sprite list on the lower right.
Figure 1: The whole editor. Four zones β€” palette (left), code area (middle), stage (upper-right), sprite list (lower-right).
flowchart LR P["1 Β· Blocks Palette
pick instructions"] --> C["2 Β· Code Area
snap them together"] C --> S["3 Β· Stage
watch it happen"] S --> L["4 Β· Sprite List
choose who you're coding"] L --> P style P fill:#4C97FF,color:#fff,stroke:#333 style C fill:#e2e8f0,color:#1e293b,stroke:#333 style S fill:#59C059,color:#fff,stroke:#333 style L fill:#9966FF,color:#fff,stroke:#333
#ZoneWhereWhat it's for
1Blocks PaletteLeftThe menu of instructions, sorted by color/category
2Code AreaMiddleThe workspace where you drag & snap blocks together
3StageUpper rightThe "screen" where your sprites act out your code
4Sprite ListLower rightAll your characters/objects; click one to code it

πŸŽ“ Learn It: The Blocks Palette

The left strip is where every instruction lives. Down the far-left edge is the category menu β€” a column of colored dots. Click a dot (or scroll) and the palette jumps to that category's blocks.

Close-up of the Scratch blocks palette. A left column lists categories: Motion, Looks, Sound, Events, Control, Sensing, Operators, Variables, My Blocks β€” each with a colored dot. To the right are blue Motion blocks like 'move 10 steps' and 'turn 15 degrees'.
Figure 2: The category menu (left) and the Motion blocks it reveals. Color = category.

Here's what each category is for. You don't need to memorize this β€” just know the color story:

  • Motion β€” move, turn, glide
  • Looks β€” say, show, costumes, size
  • Sound β€” play sounds
  • Events β€” "when… " starters
  • Control β€” wait, repeat, if/then
  • Sensing β€” touching, keys, mouse
  • Operators β€” math & text
  • Variables β€” store scores & values
⭐ Most-used starter: the gold Events category holds β€œwhen 🟩 clicked” β€” the block that kicks almost every program off. You'll use it constantly.

πŸŽ“ Learn It: The Stage & the green flag

The Stage (upper right) is your movie screen. Whatever your code does, you'll see it here. By default it holds one sprite: the Scratch cat.

The Scratch stage, a white rectangle showing the orange Scratch cat standing in the center.
Figure 3: The Stage with the default cat sprite.

Just above the stage sit the two most important buttons in all of Scratch:

Two buttons: a green flag and a red octagon stop button.
Figure 4: The green flag (Go) and the red stop button.

🟩 The Green Flag

Click it to run your project. Any script that starts with β€œwhen 🟩 clicked” springs to life.

πŸ›‘ The Red Stop

Click it to stop everything immediately. Your child will use this a lot β€” that's healthy experimenting.

You can also make the stage bigger: the icons at the top-right of the stage switch between small, large, and full-screen "presentation" mode β€” perfect for showing off a finished project.

πŸŽ“ Learn It: Sprites & the sprite list

A sprite is any character or object you can code β€” the cat, a ball, a dragon, a button. Below the stage is the sprite list, showing every sprite in your project. Click a sprite to select it; the code area then shows that sprite's blocks. This is the #1 thing beginners forget.

The sprite information panel showing Sprite1 selected, with fields for name, x and y position, show/hide, size, and direction, plus the sprite thumbnail and a Stage/backdrops panel.
Figure 5: The sprite info panel (name, position, size, direction) and the sprite list.

⚠️ The classic "why isn't my code working?"

Nine times out of ten, the code was added to the wrong sprite. If a block does nothing, first check: is the right sprite selected (highlighted) in the sprite list?

To add more characters, use the round cat "+" button at the bottom-right of the sprite list β€” it opens a library full of ready-made sprites. The Stage panel to its right lets you change the background (called a backdrop).

🌱 Growth mindset: nobody memorizes the map on day one

A screen full of panels, tabs, and nine colors of blocks can feel like a lot. That "where was that button again?" feeling isn't a sign you're bad at this β€” it's what every new tool feels like, like the first week in a new grocery store. You'll find things by looking, and after a few sessions your hands will simply know where they are. If you catch yourself thinking "I'll never remember all this," swap it for "I don't know my way around yet." And let your child see you hunting for a block and saying "Hmm, let me look" β€” it shows them that looking things up is what capable people do, not a failure.

πŸŽ“ Learn It: Costumes, Sounds & saving

At the very top-left are three tabs: Code, Costumes, and Sounds.

  • Code β€” where you've been (blocks). This is home base.
  • Costumes β€” a sprite's different "outfits" or frames. Switching costumes is how animation works (the cat has two walking costumes).
  • Sounds β€” record or pick sounds for a sprite to play.

πŸ’Ύ Saving your work

Signed in? Use File β†’ Save now. Scratch also autosaves periodically.

Not signed in? Use File β†’ Save to your computer to download a .sb3 file you can reload later with File β†’ Load from your computer.

πŸ‘ͺ Setting up a safe kid account

Click β€œJoin Scratch” and follow the steps. Scratch asks for a birth month/year and, importantly, a parent or guardian's email address β€” that's you. Use a username that doesn't reveal your child's real name, and keep the password somewhere you both can find it. We'll cover community and sharing safety in depth in Module 5 (Lesson 5.2).

πŸ’¬ Teach It: Give your child the tour

Resist the urge to deliver a lecture. Kids learn this interface fastest by clicking everything. Your job is to give them a tiny map, then let them explore.

The 60-second tour to give them

"See these four parts? Over here (left) are the blocks β€” that's your toy box. In the middle is where you build. Up here (stage) is where the cat does what you say. And this green flag makes it GO. Want to press it?"

A great first exploration game

  1. Ask them to find every color of block by clicking the colored dots. "How many colors can you find?"
  2. Have them drag any one block into the middle and click it once to see what it does.
  3. Let them press the green flag and the red stop a few times. Demystify the two big buttons.

πŸ‘§ Ages 5–7

Point to zones using nicknames: "toy box," "stage," "GO button." Skip the vocabulary. Click things for them if the mouse is tricky.

πŸ§’ Ages 8–11

Let them run the tour back to you: "Can you teach me the four parts?" Teaching it cements it.

πŸ§‘ Ages 12+

Point out the Costumes/Sounds tabs and the sprite library, then step back. They'll happily rabbit-hole.

πŸ–οΈ Hands in your lap

The hardest parenting skill in coding: don't grab the mouse. Point with your finger, ask questions, but let them do the clicking. Their hands, their learning.

🎯 Quick Check

Question 1: Your child dragged in some blocks but nothing happens when they run it. What's the most likely cause?

Question 2: Which button runs the project?

Question 3: In the editor, what does a block's category color help you do?

πŸ““ Learning Journal

Take five minutes to write it down

Open the journal you started in Lesson 1.1. Date the entry, write "Lesson 1.2" at the top, and jot a few honest lines for each prompt.

  1. Key concepts: Sketch a rough box diagram of the editor and label the four areas β€” palette, code area, stage, sprite list. What does each one do?
  2. What clicked: Which part suddenly made sense? The color-coded categories? Realizing code belongs to whichever sprite is selected?
  3. Questions & confusion: Which button, tab, or menu are you still unsure about? Write it down and keep an eye out for it in the next lessons.
  4. Ideas to try: Browse the sprite library or a block category you haven't opened. What caught your eye that you'd like to use in a project?
  5. Progress & feelings: Did the editor feel less intimidating by the end? What was your child's first reaction when they saw it?

πŸ’‘ Teach It tip: In your child's coder's notebook, have them draw the Scratch screen and color the category dots (blue Motion, purple Looks, gold Events…). Making their own "map" helps it stick, and they'll love flipping back to it.

Summary & What's Next

πŸŽ“ Key Takeaways

  • The editor is just four zones: palette, code area, stage, and sprite list.
  • The colored category menu helps you find any block; gold Events holds the β€œwhen 🟩 clicked” starter.
  • Green flag runs, red stop halts. Code always belongs to the selected sprite.
  • Save via the File menu; kid accounts use a parent's email and a name that hides their identity.

The map is in your head now. πŸ—ΊοΈ

You could sit down at Scratch right now and not feel lost. That's a big deal.

πŸ… What You've Accomplished

  • Opened the Scratch editor and found your way around
  • Learned the four areas and the color-coded block categories
  • Used the green flag and red stop button
  • Learned how to save your work and set up a safe kid account

πŸ“‹ Before the Next Lesson

  • Decide: kid account now, or File β†’ Save to your computer for a while
  • Let your child play the "find a block" exploration game once more
  • Write your journal entry

❓ Common Questions at This Stage

Should we use the website or the downloadable Scratch app?

Either works β€” the editor looks and behaves the same. The website is easiest and lets you save to a Scratch account; the free desktop app is handy if your internet is unreliable or you'd rather keep everything offline for now. You can move projects between them with File β†’ Save to your computer and Load from your computer.

My child clicked something and the blocks or sprite disappeared. Did we lose everything?

Probably not. Check that the right sprite is selected in the sprite list β€” each sprite shows only its own code. If you deleted something by accident, Edit β†’ Restore Sprite (for a deleted sprite) or right-click the code area and choose Undo will often bring it back. And saving often means a mistake never costs more than a few minutes.

Should my child have their own account, or share mine?

A separate kid account (made with your email as the parent/guardian) is usually best β€” their projects stay theirs, and you get notified about account activity. Until you're ready for that, you don't need any account at all; just save files to the computer.

πŸ”­ Looking Ahead

Enough looking β€” time to build! In Lesson 1.3: Your First Project β€” Make the Cat Move & Talk you'll create your first real program: making the cat walk and say hello when you click the green flag. This is the "whoa, I did that!" moment.

πŸ’› Encouragement for the Journey

Learning a new tool is always the slowest part β€” and you've just done it. From here on, every lesson is about making things, and you already know where everything lives. One more lesson and you'll have written your first program.