You can create a portfolio site with multiple example sites using subdomains in Webflow, but each subdomain (e.g., project1.yourdomain.com
, project2.yourdomain.com
) would require its own Website Site Plan. Alternatively, you can export some example sites and host them elsewhere to reduce costs.
1. Using Subdomains in Webflow
- Webflow allows you to add custom domains and subdomains, but each published subdomain requires its own Website Site Plan.
- A single Website Site Plan applies only to one root domain (e.g.,
yourdomain.com
) or a specific subdomain (e.g., portfolio.yourdomain.com
). - If you want multiple example sites under the same root domain using subdirectories (e.g.,
yourdomain.com/project1
), you can achieve this within one Webflow project using folders or CMS collections.
2. Site Plans for Subdomains
- If you want to publish each example site as a separate subdomain (
example1.yourdomain.com
, example2.yourdomain.com
), each subdomain requires a separate Webflow project and a separate Site Plan. - There is no way to publish multiple Webflow projects under a single Site Plan unless they are contained within one project as pages or folders.
3. Exporting Sites for External Hosting
- Webflow’s code export feature allows you to download static HTML, CSS, and JS for external hosting.
- CMS and dynamic functionalities won’t work when exported since Webflow’s CMS only functions within its hosting environment.
- You can export simple static example sites to reduce Webflow hosting costs and host them on platforms like Netlify, Vercel, or regular web hosts.
Summary
- To use subdomains for different example sites, each subdomain requires a separate Webflow project and its own Site Plan.
- If budget is a concern, consider keeping all example sites within a single Webflow project using subdirectories instead of subdomains.
- You can export static example sites and host them externally to avoid multiple Webflow Site Plans, but CMS features won’t work outside Webflow.