Important
As of January 13, 2026, you can’t publish to a custom domain that
points to Webflow’s legacy DNS records.
Sites published to custom domains on our legacy hosting infrastructure
will remain live, but you can’t publish changes. To re-enable publishing,
update
your custom domain’s DNS settings.
If your domain shows an “error” in the Publishing tab of your site settings,
don’t manually update your DNS records. Instead, follow the steps in
What should I do if my domain shows an “error” in the Publishing tab?
to troubleshoot the issue.
Webflow is upgrading its hosting infrastructure to improve performance, reliability, and security. As part of this enhancement, we’re migrating secure network connections to Cloudflare, which offers superior DDoS mitigation and faster global response times.
If your site was created before April 21, 2025, you must update your custom domain’s DNS settings to point to Webflow's new DNS records. As of January 13, 2026, you can’t publish to a custom domain that points to Webflow’s legacy hosting infrastructure.
Learn more about what happens if you don’t update your DNS settings by the deadline.
Note
Webflow only blocks publishing for domains
that still point to our legacy DNS records. If you use a reverse proxy,
you may still see “Update needed” in Site settings >
Publishing > Production even after
you’ve updated your proxy origin to Webflow’s new DNS records. In this
situation, you can ignore this message and continue publishing.
What to expect
- Admins of affected Workspaces have received emails, in-app notifications, and Dashboard badges
- These updates direct you to the specific sites that still need action
- You’ll also see tools in the Dashboard to help you complete the migration
If you don’t see migration prompts in the Dashboard, go to Site settings > Publishing > Production to find the correct DNS records for your custom domain(s).
How to update your DNS
You can update your DNS settings in one of two ways: