web.dev uses Glitch to embed web-based sample apps and development environments in its posts and codelabs. See the Sample apps post for information about how to set up a Glitch.
This post will show you how to resolve some common Glitch issues.
Subscribing to Glitch and paying for Boosted Apps will automatically increase memory and disk space as well as improve your rate limits. That's an always an option if you run into any of the disk/memory issues mentioned in this post. Learn more.
Project is suspended
If you see a "Project has been suspended" message when opening a new project, contact support via their public forum or by emailing
firstname.lastname@example.org. You should receive a reply soon with steps you can take to fix your project.
Exceeding disk usage
If you see an App Status warning with exceeded disk limits, you'll need to clear up some space before you can edit and use the project.
- Remove any unnecessary dependencies from
- In the terminal, run
git pruneto remove unneeded files
du -hd1to to see which directories are taking up disk space
If an unneeded directory is bloating up on every build and taking up disk space:
Remove it (
rm -rf directory_name)
Consider adding a
package.jsonto ensure it gets deleted on every build
"prestart": "rimraf directory_name",
.git directory is taking up disk space:
git log --name-only --format="" | cat | sort | uniq -c | sort -nbrto see which files are being committed to history (note: this will still include files previously committed even if they are now in
- If you see any directories committed many times that shouldn't be, add them to
- If you don't need
.githistory, remove the
rm -rf .git)