Scratch can stop working for a few different reasons: sometimes the whole site is having issues, sometimes it’s your browser or device, and sometimes it’s a problem inside a specific project script.

Quick Scoop: What’s Going On With Scratch?

When people ask “why is Scratch not working?” they usually mean one of these:

  • The Scratch website won’t load or shows an error.
  • The editor opens, but projects don’t run or respond.
  • “My Stuff,” messages, or account pages stay stuck loading.
  • A single project suddenly broke after editing it.

Recent forum and Reddit posts show that this kind of thing still happens on and off, especially when servers are busy or when a browser update causes odd glitches.

1. Common Reasons Scratch “Isn’t Working”

Here are the most frequent causes, based on community reports and discussions.

  1. Scratch servers are having issues
    • Pages like “My Stuff,” messages, or projects may not load, or you get “Whoops! Our server is scratching its head.”
 * Multiple users sometimes report at the same time that they can’t log in or their projects won’t open.
  1. Browser problems
    • Some users report that Scratch misbehaves in one browser (often Chrome) but works fine in another (like Edge or Firefox).
 * Browser extensions, ad‑blockers, or privacy tools can interfere with Scratch’s scripts and assets loading.
  1. Local project or code issues
    • A project with a huge amount of code or many clones can lag or appear “frozen,” especially right after hitting the green flag.
 * A misplaced `stop all` block or missing event (like `when green flag clicked`) can make it look like the project “does nothing.”
  1. Account or login glitches
    • Users sometimes can’t log in, or they log in but can’t reach messages, projects, or account pages.
 * This is often temporary and tied to site load or cookies/session issues.

2. Quick Things You Can Try

If Scratch isn’t working for you right now, you can walk through these steps like a mini checklist.

  1. Check if it’s Scratch, not you
    • Try opening another random project from the front page (no login needed).
    • If nothing loads or you see server error messages, it’s likely a Scratch‑side issue; waiting is often the only real fix.
  1. Switch browser or device
    • Open the same project or the Scratch site in a different browser (for example, Edge or Firefox instead of Chrome).
 * If it works there, the issue is probably browser‑specific (extensions, cache, or a recent update).
  1. Refresh your session
    • Log out of Scratch, close the tab, wait a moment, then log back in on a fresh tab.
 * Some users report that simply closing the tab and signing in again fixes login and loading problems.
  1. Check for project‑specific bugs
    • Make sure your scripts actually start with an event (like when green flag clicked or when this sprite clicked).
 * Look for any `stop all` blocks you might have added for testing and forgotten to remove; they can silently stop everything once they run.

 * If your project suddenly became slow or unresponsive after adding more code, heavy scripts or many clones may be overloading the engine.

3. “My Stuff” or Pages Not Loading

Several users recently have complained that “My Stuff” or other account‑related pages just sit on a loading screen or show partial content.

  • One shared workaround: if you see an “X” or a broken UI element near “My Stuff,” right‑click it and choose “Open in new tab” instead of left‑clicking.
  • Sometimes, only certain parts of the site are slow (like messages or project lists) while the editor still works, which almost always points to a temporary server or UI issue.

4. If a Single Project Stopped Working

If Scratch loads fine but one project suddenly broke:

  • Review your most recent changes.
    • In one forum case, a platformer worked until the author changed custom blocks and blinking behavior; after that the player would only blink and nothing else happened.
  • Look for:
    • A missing event block that used to start the logic.
    • Logic moved into a custom block that no longer gets called.
    • A fresh stop all or similar control block cutting execution short.
  • Reducing or restructuring heavy scripts (especially those using many clones or forever loops) can remove lag that makes the project seem “dead.”

5. Mini FAQ: Latest Discussion & Trend Context

Even in 2024 and 2025, people are still posting things like “Why isn’t Scratch working?”, “My Stuff is not loading,” and “Is Scratch down or is it just me?” in forums and Reddit threads.

“I tried everything. signing in and out, reloading the tab. nothing is working. i don't know what's going on.”

These posts usually end with:

  • It fixed itself after some time (server side).
  • Switching browsers solved it.
  • Or the user eventually found a bug in their own scripts (missing events, stop all, too much code).

SEO Bits (for your post draft)

  • Focus keyword ideas to weave in naturally:
    • “why is scratch not working”
    • “Scratch not loading”
    • “Scratch latest news and forum discussion”
    • “trending topic: Scratch down”
  • A possible meta description (under ~160 characters):
    • “Wondering why Scratch is not working today? Learn the most common causes, from server issues to project bugs, plus quick fixes users say actually help.”

TL;DR

Most of the time, Scratch “not working” is either a temporary server or login issue, a browser quirk, or a bug in a specific project’s code.

Trying another browser, logging out and back in, and double‑checking your scripts for missing events or stop all blocks will solve a surprising number of cases.

Information gathered from public forums or data available on the internet and portrayed here.