Frequently asked questions

Currently, 'Can clone' and 'Can copy' settings only work for View-only links, not Content edit links. This is a popular request and Webstudio is working on more granular permissions (GitHub issue 5187) to allow content editing while preventing cloning/copying. This would be useful for client work where you want to allow editing but protect your project structure.

No, you cannot use dynamic pages (PRO features) without a PRO subscription or lifetime license when using the cloud builder. To use PRO features for free, you would need to self-host the Webstudio builder (not just the site).

Yes, dynamic pages are a Pro feature. To use Pro features for free, you would need to self-host the Webstudio builder (not just the site). The cloud builder requires a Pro subscription or lifetime license to access Pro features like dynamic pages, even if you're deploying via CLI to external hosting.

If your domain shows as 'Active, but not published' and the publish button is grayed out, you likely need to add the required 'Built with Webstudio' badge to your site. On the free plan, you can use one custom domain but must include this badge on your website.

If your domain shows 'Active' but the publish button is greyed out, you likely need to add the required 'Built with Webstudio' badge to your site. For free accounts, this badge is mandatory when using custom domains. Add the badge component to your site, and the publish button should become available. Pro accounts can remove this badge requirement.

When your custom domain shows 'Active, but not published' with a grayed-out publish button, it's usually because you haven't added the required 'Built with Webstudio' badge to your website. In the free version, you can use one custom domain, but it must include the Webstudio badge. You need to manually add this badge component to your site before you can publish to a custom domain.

Team workspaces with access control are planned but no timeframe is confirmed. The concept involves one builder instance with teams that have access to specific projects (Team A sees Site A, Team B sees Site B). For self-hosted deployments, this will likely be an enterprise feature, not open source. In the cloud, Webstudio plans to offer a team plan for this functionality.