Why Won’t My Scratch Project Save? | Fix It Now

When a save stalls or the banner says “Project could not save,” the editor isn’t writing your changes to the site. You might be offline, logged out, out of storage, or hitting limits on assets and project data. This guide gives quick fixes first, then deeper steps that match the way Scratch saves both online and offline. If you’re mid-build, download a backup right away from File ▸ Save to your computer so work isn’t at risk.

Why Won’t My Scratch Project Save? Common Triggers

Here are the usual culprits behind failed saves in the online editor. The “Try again or Download” prompt confirms that the site didn’t store your latest edits; the download option gives you a .sb3 copy as a safety net.

• Signed-out session — Scratch can time out or drop a session, which blocks saves to your account until you sign in again. Forum posts advise checking login status and grabbing the backup download when this appears.
• Large or long audio — Sounds that exceed the asset ceiling often block saving. Users report saves working again after trimming long MP3s. Scratch enforces per-asset and JSON size limits.
• project.json too large — The JSON inside your project must stay under 5 MB, even if the full .sb3 file can be much bigger. Heavy lists, clones, or generated blocks inflate it.
• Browser or device issues — Out-of-date browsers, blocked cookies, or strict site settings can prevent saves or login. Scratch points to current Chrome, Edge, Firefox, and Safari builds.
• Network or site trouble — Temporary server blips or a weak link can interrupt autosave. Waves of forum reports line up with outages; “Try again” tends to work once the link is stable.

Quick Checks That Fix Most Saves

Do this first: these actions clear most “project could not save” popups fast.

1. Confirm you’re signed in — Click your avatar. If you see Join or Sign in, log in and reopen the project. If the banner appears again, press Try again once, then download a copy.
2. Force a manual save — Open File and click Save now or Save as a copy. If that still fails, use Download to your computer to grab an .sb3.
3. Trim oversized sounds — Export a sound to check size; keep each asset under 10 MB. Replace long tracks with shorter loops or lower-bitrate files, then save again.
4. Reconnect the browser — Refresh the tab after verifying the link, then save. Many “can’t save” runs match short connection drops.
5. Switch browsers — Try a current Chrome, Edge, Firefox, or Safari build. Saves often work after moving away from an older version.

Browser And Device Settings That Block Saves

Scratch relies on login cookies and web storage while you edit and save. If your browser blocks those, you can’t stay signed in or write changes. Tweak these settings, then retry a save.

Browser	Setting To Check	What To Do
Chrome / Edge	Third-party cookies, site data	Allow cookies for scratch.mit.edu; clear site data, then log in again.
Firefox	Enhanced Tracking Protection	Add a site exception for scratch.mit.edu; retry save.
Safari	Prevent cross-site tracking	Leave on, but ensure cookies for scratch.mit.edu aren’t blocked; test a fresh profile.

Threads and the FAQ point to up-to-date Chrome, Edge, Firefox, and Safari as the best route for editing. Phone browsers can view projects but not edit them.

Clean Start Steps

• Open a private window — Log in fresh and test a save. If it works here, cached data or extensions in your main profile were in the way.
• Disable extensions briefly — Turn off ad-blockers or privacy add-ons for a minute, then try Save now. Re-enable once you find the culprit.
• Create a new browser profile — Profiles with old site data can break saves; a new one isolates the editor with clean storage.

Account, Cloud, And Offline Editor Quirks

Know how saves work: online editing keeps a copy on Scratch’s servers and autosaves on a timer. You can’t disable autosave on the website, but you can work offline and save by hand when you want.

• Autosave vs. manual saves — The online editor autosaves; the offline editor writes an .sb3 to your drive. Use the offline tool on slow links or for long work sessions.
• Use “Download” as a safety switch — When the alert appears, click Download to grab a working .sb3 before more edits. That copy opens in Scratch Desktop or the web editor.
• Login hiccups — If saves stop and your avatar vanishes, the site thinks you’re logged out. Sign in again; if logins keep dropping, clear cookies for the site and try a second browser. Users describe random sign-outs that clearing data often fixes.
• Studios and remixes — Editing a remix still saves to your account, but heavy remix chains can carry large assets. If saves fail, download, prune, and re-upload a slimmer copy.
• School networks — Managed filters or security tools can break saves. Test on a home link; if that works, ask the admin to allow editor traffic. Forum threads connect save errors with filtering and outages.

Safe Save Workflow (Every Session)

1. Start with a local copy — Grab File ▸ Save to your computer before big edits. Keep the file on your desktop while you build.
2. Name a version — Add date or v1/v2 in the filename to make rollback simple.
3. Work in small steps — Add a sprite or sound, save, then test. If a step breaks saving, you’ll know which change did it.
4. Finish with an upload — When the link is stable, open your project online and update it from the .sb3 you kept.

Asset Size, Extensions, And Limits

Scratch 3 doesn’t cap the total .sb3 size the way Scratch 2 did, but it enforces limits that explain many save errors: each asset must be under 10 MB, and the project JSON must be under 5 MB. Large sounds and runaway lists are the common triggers.

• Keep sounds lean — Cut silence, export mono, and use a lower bitrate for music. Users report saves working again once long tracks get trimmed.
• Watch JSON growth — Massive arrays or thousands of cloned blocks bloat project.json. Split work into smaller projects, or prune data you can rebuild at runtime.
• Trim sprites — Vector art scales well, but hundreds of costumes or huge bitmaps increase upload time. Delete unused costumes and compress images before import.
• Use the right extension — Offline saves should end with .sb3. Some older desktop builds had save-dialog quirks; if you see “All Files” with no extension, type .sb3 before saving.
• Remixing and migrations — When opening SB or SB2, save in Scratch 3 to convert to SB3, then continue editing.

Audio And Image Slim-Down Tips

• Shorten music — Loop a 10–20 second segment instead of uploading a full track; keep each sound under the 10 MB ceiling.
• Export mono — Stereo doubles size with little benefit in many projects.
• Lower sample rate — 22.05 kHz often sounds fine for game music and cuts size sharply.
• Compress images — Shrink large PNGs before import; prefer SVG for flat art so the JSON stays lean.

Network, Firewalls, And School Filters

Saving needs a steady line to the site. If your tab hangs on “Saving…” or loses the green saved tick, check the path between your browser and Scratch.

1. Test the connection — Open a second tab and load your profile. If it spins, your link is shaky. Save a backup to .sb3, then wait a minute and retry the banner’s Try again.
2. Check firewalls and filters — School filters, antivirus web shields, or VPNs can block editor calls. Reports tie clusters of save errors to filtering; a home link test confirms it.
3. Mind big uploads — Long audio or many sprites mean larger uploads; saves take time and drop more easily. Trim assets, then save when the page is calm.
4. Watch captive portals — Public Wi-Fi that needs a sign-in page can stall uploads until you accept the portal page.
5. Turn off the VPN — Some VPNs throttle or block the calls the editor uses; a quick off-test will tell you.

Taking A Closer Look: Symptoms And Fixes

This cheat-sheet maps common messages to likely causes and a fast fix. Keep it open while you troubleshoot “Why Won’t My Scratch Project Save?”.

Symptom	Likely Cause	Fast Fix
“Project could not save. Try again or Download.”	Lost login or shaky link	Sign in, press Try again; grab Download as backup.
Save now does nothing	Oversized sound or huge JSON	Trim sounds under 10 MB; reduce lists/blocks; save again.
Stuck on “Saving…” for minutes	Slow upload or filter	Wait, then refresh; test another network; save a local .sb3.
Saved file has no .sb3 extension	Desktop dialog quirk	Type a name ending with .sb3, then reopen in Scratch.
Edits vanish after reload	Autosave missed; not logged in	Log in again; use manual Save now and keep a local backup.
Can view on phone, can’t edit	Phones can’t edit projects	Edit on desktop/tablet with a supported browser.

Why Won’t My Scratch Project Save? Close Variations To Watch

Searches like “Scratch project not saved,” “project could not save,” or “save now not working” usually point to the same root causes: a dropped login, blocked site data, over-limit assets, or a shaky link. Users flag long audio as a frequent trigger, and forum helpers steer people to download a safety copy, trim the oversized parts, and retry.

Preventive Habits That Keep Saves Safe

These habits make “Why Won’t My Scratch Project Save?” far less likely and keep your work recoverable if the site blinks.

• Back up every session — Use File ▸ Save to your computer when you start and when you finish. That gives you a local .sb3 even if the site stops saving mid-way.
• Name versions clearly — Add v1, v2, v3 in filenames. If a change corrupts project.json, you can roll back without digging.
• Keep assets tidy — Compress music, delete unused costumes and sounds, and split giant lists into smaller data you can rebuild. The JSON stays lean, so saves don’t choke.
• Update your browser — Run a current Chrome, Edge, Firefox, or Safari. The editor is built for modern engines; older versions can stumble.
• Work offline for big edits — On slow links, switch to Scratch Desktop to edit and test, then upload the .sb3 when your connection is solid.

One Last Pass Before You Close The Tab

Protect the work: download a copy before any big change. If the save banner returns, try once, then move to backups and slice down assets. That path keeps projects moving while you sort out login, browser, or network snags.