Add a Custom Domain to Webflow for Free — No Upgrade Needed
Webflow requires a paid plan for custom domains. This guide shows how to use Edgely reverse proxy to host your Webflow site on your own domain at zero cost.
TL;DR — Quick Answer
By pointing a CNAME record at Edgely and entering your Webflow.io URL as the target, you can serve your Webflow site on any custom domain — for free, with edge caching and SSL included.
Why Webflow Requires a Paid Plan for Custom Domains
Webflow's free plan gives you a *.webflow.io subdomain. Publishing to a custom domain requires a "Basic" site plan or higher — starting at $14/month. [1] For developers who simply want their domain pointing at a Webflow project without paying Webflow monthly, a reverse proxy is the answer.
The Reverse Proxy Approach
Instead of telling Webflow about your custom domain, you tell your DNS registrar to point your domain at Edgely. Edgely then fetches your Webflow site on every request and returns it to your visitors. Webflow never needs to know your domain exists. [2]
Step-by-Step Setup
1. Publish your Webflow site
In Webflow, go to Designer → Publish. Make sure your site is published to the *.webflow.io subdomain. Note the URL — you'll need it.
2. Add the domain in Edgely
Sign up at xedgely.com (free), then click Add Domain:
- Custom Domain:
www.yourdomain.com - Target URL:
https://yoursite.webflow.io
3. Add a CNAME record at your registrar
Add a CNAME pointing www → proxy.xedgely.com. Save the record.
4. Wait for DNS & SSL
Edgely polls for the CNAME to resolve, then provisions a free SSL certificate. Your Webflow site goes live on your custom domain. [3]
Caching Static Webflow Pages
Webflow pages are rendered server-side but usually don't change between visits. Enable Edgely's Cache option to store the HTML at the edge for 5 minutes — dramatically reducing load times for geographically distributed visitors. [4]
Limitations to Know
- Webflow eCommerce: cart and checkout flows rely on cookies. These pass through Edgely transparently, but test thoroughly.
- Webflow CMS: dynamic collection pages work normally since Edgely fetches a fresh response from Webflow on cache miss.
- Form submissions: Webflow forms submit to Webflow's own backend and continue to work through the proxy.
Edgely is the fastest way to proxy your Webflow project to a custom domain. It provisions a free SSL certificate, syncs routing to Vercel Edge Config for sub-millisecond lookups, and optionally caches responses at the edge — all for free on the starter plan.
Key Takeaways
- Webflow's custom domain requires a paid site plan — Edgely proxies your webflow.io URL to your domain for free.
- Edge caching improves TTFB for Webflow static and CMS pages.
- Forms, Webflow CMS, and most dynamic features work transparently through the proxy.
Frequently Asked Questions
Can I proxy a Webflow eCommerce store?
The proxy passes cookies and headers through, so cart sessions work. However, Webflow eCommerce checkout requires your domain to be verified in Webflow for payment processing. Test thoroughly in staging before going live.
Does Webflow SEO work through a reverse proxy?
Yes — the HTML, meta tags, canonical URLs, and sitemaps that Webflow generates are forwarded as-is. If you use Edgely's caching, make sure your TTL doesn't cache stale content after a CMS publish.
Is there a bandwidth limit on Edgely's free plan?
The free plan is suitable for personal projects and moderate traffic. Check the Edgely pricing page for current limits.
Sources & Citations
- [1]Webflow Pricing— webflow.com
- [2]Reverse Proxy Architecture— nginx.org
- [3]Let's Encrypt Documentation— letsencrypt.org
- [4]Web Caching Basics (MDN)— developer.mozilla.org
Ready to add your custom domain?
Set up your reverse proxy in under 5 minutes — free, with SSL and edge caching included.