A Glitch Alternative For Static Sites

You opened a glitch.me link you have had bookmarked for years and got a mostly empty page that says "Well, you found a glitch."

Or you went to the editor, and glitch.com bounced you to a blog instead.

Neither of those is a hiccup. Glitch switched off project hosting on 8 July 2025, and the parts you would use to rescue your work have since gone too. So looking for a Glitch alternative is not shopping any more. It is a migration, and what decides where you go is something most people have not checked.

Was your project ever a static site?

A folder of HTML, CSS and JavaScript moves to any static host in about a minute. An Express app, a Discord bot, or a project with a server.js and a few rows of data under .data, does not. That needs a host which runs code, and most of the friendly drag-and-drop options cannot.

Below is the state of Glitch as I checked it on 9 October 2026, what is still recoverable, and where each half of that split should go.

a static hosting comparison across every option covers the whole field. This post is about getting off a platform that has already closed.

Is Glitch Still Hosting Anything In 2026?

No. Nothing runs, nothing is editable, and the download window shut on 31 December 2025.

Here is the timeline.

Those dates come from Glitch's own announcement of 22 May 2025 and the coverage that followed. The Register on Glitch ending app hosting Anil Dash, Glitch's chief executive, gave three reasons: rising costs, extensive abuse of free hosting, and an ageing architecture that compared poorly with newer platforms.

I ran the checks myself on 9 October 2026 rather than trust the announcement:

• glitch.com, glitch.com/edit and glitch.com/dashboard all answer with a 307 redirect to blog.glitch.com. There is no editor and no dashboard behind them.
• A project address on glitch.me answers HTTP 410 Gone, the status code for something that existed here and is never coming back, then refreshes to the shutdown announcement after 30 seconds.
• support.glitch.com, the community forum, has no DNS record. Neither does api.glitch.com, where the git endpoint used to live, nor cdn.glitch.global, which held uploaded assets.

That third bullet matters most. Guides from mid-2025 still tell you to clone your project from api.glitch.com, and that hostname no longer resolves, so the instructions cannot be followed.

The redirects were a courtesy with an expiry date on them, not a permanent arrangement. If you rely on one, it has weeks left, not years.

Can You Still Get Your Code Off Glitch?

Not from Glitch. The download route closed with the dashboard on 31 December 2025, and project files were deleted after that.

Three routes are left, all partial.

1. Your own copy. A git clone on an old laptop, a zip in a downloads folder, a repository you pushed to GitHub. This is by far the likeliest place your code still exists.
2. The Wayback Machine. It archived rendered pages, not source. For a static project that is often enough, because the rendered page was the source. For a server app you get its HTML output and none of the code behind it.
3. The Archive Team collection. Volunteers crawled Glitch before the shutdown and the result sits on the Internet Archive as archiveteam_glitch. Public project metadata was saved, source code and CDN assets only partially, and access to the collection is restricted. Archive Team's record of the Glitch shutdown

One warning covers all three. A Glitch git repository never contained your uploaded assets, your .data folder or your .env file, so even a complete clone is missing the images, the little database and every secret key. If your project stored anything while it ran, that data is gone.

What Glitch Was Genuinely Good At

It is easy to be rude about a dead platform. Glitch earned none of that.

The editor opened in a browser tab and the app was live at a real URL from the first keystroke. No install, no build step, no deploy. I have watched people who had never written a line of code get a working page inside five minutes, and nothing since has matched that for a standing start.

Remix was the other real idea. Every project was a fork button, so you learned by taking something that worked and breaking it. The forum was unusually kind, and teachers built courses on it.

Behind all of it was a full Node container with a writable filesystem, not a static host dressed up as one. That is why so many Glitch projects were bots and tiny APIs rather than pages. Free projects slept after five idle minutes and woke on the next request, which is the trade that made it free.

It is also the bit that makes migrating awkward.

Your Glitch Project Was Probably Not Static

Open your recovered folder and look for three things. It takes twenty seconds.

• A package.json with express, discord.js or similar in it, or a server.js. You had a server. A static host will not run it.
• A .data folder, or a .sqlite or .db file. You had data your app wrote while it ran. Static hosts have nowhere to put it.
• An .env file. You had secrets, so something was calling an API from the server side.

None of those three? You had a static site all along and were using Glitch as an editor, so this move is easy. what a static website is and is not draws the line properly if you are unsure which side you are on.

There is a middle case that looks like a server app and is not. If the only reason you had a backend was a contact form posting to an Express route, you do not need a server now. Static hosts handle form submissions themselves, and getting a form working on a static site covers how. That one substitution turns a surprising share of old Glitch projects into plain static sites.

Picking A Glitch Alternative For Each Side Of The Split

Here are the four axes that decide it for a Glitch refugee. Every cell was checked on 9 October 2026.

Two cells there are worth reading twice. Render's free web service spins down after 15 minutes without traffic and takes about a minute to wake, close to how a free Glitch project behaved. And Fly.io has no free tier left, only a trial measured in hours, so the honest figure for an always-on app is a couple of dollars a month.

For a static page the shortest routes are Netlify Drop and Cloudflare Pages Direct Upload. Both take a dragged folder in a browser, neither needs git, and both issue HTTPS and allow your own domain free.

Where we are the wrong answer: if your project was an Express app, a Discord bot, or anything that wrote to .data, OxyPages will not run it. We serve files exactly as stored and never execute them, so this is a category boundary, not a plan you can upgrade past. Take Render if you want a free tier, Railway if you want it awake for $5, Fly.io if you want control by the second.

Do Not Forget The Domain You Pointed At Glitch

If you only ever used a glitch.me address, skip this.

If you pointed a domain you own at Glitch, that DNS record still aims at Glitch's edge, so visitors to your own domain are getting the gone page. There is no Glitch side left to fix it. You change the record at your registrar, after the new site is live and tested on the host's own subdomain.

What To Do Next

Half an hour, in this order.

1. Find your code. Old laptop, downloads folder, GitHub, a collaborator who remixed it. The official download closed on 31 December 2025, so there is no fallback.
2. Run the three-file test above. A package.json with a server in it, a .data folder or an .env file puts you on the server side.
3. If you are static, put everything in one folder with the main page named index.html and drag the folder to a host. One upload, no build, no repository.
4. If you need a server, start with Render's free tier. Its 15 minute spin-down is the same bargain Glitch made at five minutes, and $7 a month removes it.
5. Re-point your domain last, and test the new address on a phone on mobile data first.

put the folder online and get a working link if you are on the static route, or take Netlify or Cloudflare Pages from the table. If you have a single file rather than a folder, hosting one HTML file and getting a link is the four-step version.

If this is the second platform to close under you, you are not imagining a pattern. moving a project off Replit hosting is the same exercise with different dates, and the lesson both times is to keep a local copy of anything that lives only inside somebody's editor.