SaaS
Codeberg
Codeberg Pages v2, the original in-house static-site hosting for Codeberg repositories, is shut off completely on December 31, 2026. Sites still served the old way — the ones whose repository never had a Pages webhook set up — stop being served after that date and must migrate to the new git-pages-backed Codeberg Pages before then.
departs 31 Dec 2026
Quick answers
- Is it true that Codeberg Pages v2 shuts down on December 31, 2026 — migrate to the new git-pages backend?
- Yes. Codeberg has officially announced it, effective 31 Dec 2026. Codeberg hosts static sites from a repository's `pages` branch (or a `pages` repo) at `*.codeberg.page`.
- When does it take effect?
- 31 Dec 2026. Verified against the vendor's own announcement.
- What should I use instead?
- First, find out which backend you are on.
What this means for you
Codeberg hosts static sites from a repository's `pages` branch (or a `pages` repo) at `*.codeberg.page`. The original implementation — now called Pages v2 — is being retired in favour of a new git-pages backend, and Codeberg will shut Pages v2 off completely on December 31, 2026. After that date, any site still served by the old system simply stops being served; the repository and its files stay intact, but the published page goes dark. The sites affected are specifically the ones that never had a Pages webhook configured in their repository — if you set your site up a long time ago and have never touched its Pages configuration, it is very likely still on v2. This matters to anyone hosting project docs, a personal page, or a small static site on `codeberg.page`: unmigrated sites will 404 after the cutoff until they are moved to the new backend. The new git-pages-backed Pages remains free and uses the same branch-based model, so migration is a configuration change rather than a move to a different host.
Where to go
First, find out which backend you are on. Codeberg provides a migration-check tool at codeberg.page/migration-check/ where you paste your site URL and get a definite answer; as a manual rule of thumb, a repository that never had a Pages webhook set up is still on v2. If you are on v2, follow Codeberg's migration guide at docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/ to move onto the new git-pages backend before December 31, 2026 — the guide walks through configuring the webhook and the current branch/repo layout so the new system serves your site. Do this well ahead of the deadline so you can confirm the site still resolves on `codeberg.page` after the switch. Sites that are not migrated by the cutoff stop being served and will need to be migrated afterward to come back online.
- The new git-pages-backed Codeberg Pages — the direct, free successor on the same `*.codeberg.page` domains; the intended migration target
- GitHub Pages or GitLab Pages — if you are moving the project's hosting off Codeberg entirely
Codeberg Pages v2 — the original in-house system that serves static sites from a repository’s pages branch at *.codeberg.page — will be shut off completely on December 31, 2026, per Codeberg’s announcement (published October 7, 2026). Sites still served by the old backend need to move to the new git-pages-backed Codeberg Pages before then.
What shuts down
After December 31, 2026, Codeberg stops serving any site that is still running on the v2 backend. The repository and its files are untouched — it is the published page at codeberg.page that goes dark. The new git-pages backend is the free successor and keeps the same branch-based, *.codeberg.page model, so this is a migration between Codeberg’s own implementations, not a move to a different host.
Who this affects
The sites at risk are the ones whose repository never had a Pages webhook set up — typically sites configured a long time ago and never touched since. If that describes your page, it is very likely still on v2 and will stop being served after the cutoff.
What to do
- Check which backend you’re on. Codeberg’s migration-check tool at
codeberg.page/migration-check/takes a site URL and gives a definitive answer. The manual rule of thumb: no Pages webhook in the repository means you’re still on v2. - Migrate before December 31, 2026. Follow Codeberg’s migration guide to move onto the new git-pages backend — it covers the webhook and branch/repo layout the new system expects.
- Confirm it still resolves. After switching, load your
codeberg.pageURL to verify the new backend is serving the site, with time to spare before the deadline.
Sites not migrated by the cutoff simply stop being served; they can be migrated afterward to come back online, but there will be downtime in the meantime.
This entry tracks Codeberg’s official announcement; if the shutdown date changes, the entry will be updated with a changelog note.
Entry changelog
- — last reviewed.
- — Entry created from Codeberg's official blog announcement (2026-10-07), which states Codeberg Pages v2 "will be shut off completely on 2026-12-31" and directs users of the old backend (repositories without a Pages webhook) to migrate to the new git-pages-backed Pages. Surfaced via a Hacker News discussion of the announcement; written from the vendor's primary post. Not machine-detectable from a code repository (the v2-vs-new distinction is Codeberg-side hosting configuration), so no detect fingerprint was added.
Put this countdown in your README
Building on Codeberg? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/codeberg-pages-v2-shutdown)Spot an error or a changed date? Tell us and it’s corrected the same night.