Glitch, a great Platform for Developers

Glitch ended project hosting and user profiles on July 8, 2025.

The hands-on tutorial that originally appeared on this page can no longer be followed. You cannot create, remix, edit, or host an application on Glitch today.

Glitch kept project dashboards available for code downloads through the end of 2025. That deadline has also passed.

What Glitch was

Glitch was a browser-based coding and hosting platform.

You could open a project, edit its files, see the application update, and share a public URL. It supported static sites and Node.js applications.

Its defining idea was remixing. Instead of starting from an empty folder, you could copy a working project and change it.

Glitch also combined several tools in one friendly interface:

• a code editor
• application hosting
• logs and a console
• environment variables for secrets
• npm package installation
• project history
• real-time collaboration
• embeds for tutorials

That made it especially useful for teaching. A reader could inspect a complete example and experiment without setting up a local development environment.

What changed

Glitch announced the hosting shutdown in May 2025.

The company explained that operating millions of applications had become expensive and increasingly difficult to protect from abuse. Project hosting and profiles then shut down on July 8, 2025.

Glitch allowed project owners to:

• download their code through December 31, 2025
• configure redirects for old project subdomains before that deadline

Glitch said configured redirects would remain active at least through the end of 2026.

An old glitch.me URL may therefore redirect somewhere else, but the application itself is no longer running on Glitch.

What happened to old tutorials

Many programming tutorials used embedded Glitch projects.

Those examples now need one of these replacements:

• source code committed to a public repository
• a downloadable archive
• a new live demo on another hosting service
• a local setup section readers can follow

A redirect can preserve an old link, but it cannot preserve an interactive editor or a server that was never migrated.

When maintaining an old tutorial, check both the source link and the running demo. A page that still loads is not enough if readers cannot inspect the matching code.

The lasting lesson from Glitch

Glitch showed how much easier learning becomes when setup takes seconds.

Its remix model also made examples feel less fragile. Readers started from working code, made one change, and immediately saw the result.

Those ideas remain useful when publishing a demo today:

• keep the source easy to copy
• document the runtime and dependency versions
• avoid hidden setup
• provide a direct path from code to a running result
• keep a copy outside any single hosting platform

The final point matters most. A tutorial should not depend on one vendor being available forever.

For the official timeline, read Glitch’s announcements: Important changes are coming to Glitch and Until we meet again.

Related posts about services: