You cannot directly host a Webflow project in a subfolder (e.g., example.com/project
) on another domain using Webflow hosting. Webflow only supports hosting projects at root domains (e.g., example.com
) or subdomains (e.g., project.example.com
).
1. Webflow Hosting Restriction
- Webflow’s built-in hosting only supports root domains and subdomains.
- It does not support subfolder hosting (e.g.,
example.com/webflow-site
) because each Webflow project is sandboxed in its own isolated hosting environment. - You cannot deploy a Webflow project to a subfolder on the same Webflow-hosted domain.
2. Workaround: Export and Self-Host
To achieve subfolder placement, you’ll need to export your Webflow project and host it manually.
- Go to your Webflow project, and under the Designer, click on the Export Code icon (arrow pointing up).
- This will download your HTML, CSS, JS, and assets.
- You can then upload this to your server in the desired subfolder (e.g.,
example.com/project
). - Note: CMS features, forms, and interactions relying on Webflow’s infrastructure will not work unless replaced with custom solutions.
3. Alternative: Use Redirects
If you want to keep Webflow hosting and still have users access example.com/project
, consider this:
- Host your Webflow project at a subdomain, like
project.example.com
. - On your main site (hosted elsewhere), create a 301 redirect or reverse proxy to make
example.com/project
appear to serve Webflow content. - Requires server-side configuration (e.g., NGINX or Apache proxy rules), which is not possible using Webflow hosting alone.
Summary
Webflow does not support hosting sites in subfolders; to do this, you must export the code and self-host or use custom server-side redirects or proxies. Otherwise, use subdomains, which are fully supported.