Move a project from Glitch to Coolify

Take it out

1. 1

   Step 1

   Use the copy you already saved

   Glitch's May 22, 2025 post says the dashboard, including code downloads, stayed up through the end of 2025. This guide was checked on November 2, 2026. If the project is not in a Git repository or a zip you saved, Coolify cannot fetch it from Glitch.

2. 2

   Step 2

   Write down the environment

   Copy any keys, the start command, and the port the app listened on. Coolify has an environment-variable screen. It will not remember Glitch's panel for you.

Put it in

1. 1

   Step 1

   Put the code in Git

   Coolify deploys from Git or a Dockerfile. Push the project to a repository you control. A Glitch remix link is not a source Coolify can clone.

2. 2

   Step 2

   Deploy it on a server you run

   Install Coolify, connect the repository, and set the domain. Coolify's docs cover domains, HTTPS, and environment variables for the build and the running container. This guide did not click through a deploy.

3. 3

   Step 3

   Point the old URL if you still have a redirect

   The May 22, 2025 post says redirects set up before December 31, 2025 would stay active at least through the end of 2026. This guide did not request a live project subdomain. If a redirect still answers, aim it at the new domain. If it does not, update the links yourself.

What you lose

• The browser editor and the remix button

  Coolify does not edit the project in a browser and does not copy someone else's Glitch in one click. The code is yours to change in a normal editor.

• Projects you never downloaded

  The download promise in the shutdown post ended with 2025. There is no later archive this guide can send you to.

• Glitch Pro

  The same post says new Pro subscriptions stopped on May 22, 2025, and existing ones ran until July 8, 2025. Always-on from that plan does not transfer. The app stays up only while your server stays up.