Frequently asked questions

Page view limits are applied per account, not per domain. All pricing in Webstudio is per account.

You don't need to delete the default .wstd.io domain. Think of it as a 'staging server' where you can deploy and test without your site going live and without being indexed by search engines. These domains will always exist, you don't need to publish to them, and they won't be indexed by search engines.

Yes, Webstudio can be self-hosted using Docker. However, the documentation for Docker setup is currently limited. You can find some guidance in the contributing docs for developers section. Note that some features like email sending are cloud-only, so you'll need to implement your own backend solutions for features like webhook forms when self-hosting.

Yes, you can use Cloudflare Workers with Webstudio-hosted sites. Set your main domain's CNAME to 'proxied' in Cloudflare to enable Workers, while keeping subdomain CNAMEs (like those pointing to Webstudio) as 'DNS only'. This allows you to reverse-proxy different subdomains or paths through your Worker without creating double-proxy issues.

Patterns:

1. Main domain proxied -> Worker routes traffic to a Webstudio project subdomain
2. Worker maps /blog or /app path segments to a Webstudio project
3. Avoid chaining (nesting) a proxied CNAME behind another proxied CNAME

Only the domain terminating at the Worker should be orange-cloud (proxied); project CNAMEs stay DNS-only.

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).

Currently, you cannot directly use .env variables from exported apps as resource variables in the Webstudio builder. The builder and exported app environments are separate. However, this type of functionality for handling different environments (development, staging, production) with different API endpoints is being considered for future development.

Yes, the Animation Engine works when self-hosted—use the latest version and reinstall deps. If they fail only on Docker: update images, run install, clear caches, ensure no CSP blocks animation scripts. If none run at all, verify OS/browser reduced-motion isn’t forcing a skip (see separate reduced-motion FAQ).

Webhook forms have limitations when self-hosting. Email sending is a cloud-only feature, so for self-hosting you need to implement your own backend or use services like n8n or Make.com. Currently, only JSON format is supported for webhook forms in self-hosted setups - URL-encoded format is not yet supported.

Yes. Webstudio uses the IPX optimizer to serve optimal formats (AVIF, WebP, or optimized JPEG) based on browser support. Cloud hosting works out of the box. For self-hosted Docker setups ensure:

1. You pulled the latest container image
2. Dependencies are installed (pnpm install / npm install)
3. No proxy strips Accept headers (required for content negotiation)
4. Caching layer (CDN/reverse proxy) isn’t serving stale JPEG variants

If you only see optimized JPEGs, typically the Accept header is lost or optimization config is blocked.

No built-in dashboard yet. Use external analytics (Plausible, Umami, PostHog, GA). Page view limits are per account. Extra views purchasable on pricing page. Internal tracking UI is planned (issues 5286, 5239).

To update the Animation Engine on self-hosted Webstudio, you need to use the latest Webstudio version and run npm install to update all packages. The Animation Engine works fine on Webstudio-hosted sites and in the builder, but self-hosted containers may need updates to ensure animations work properly on the live site.

This is a limitation with the current router used for Docker deployments. Assets in _image/** routes can be incorrectly handled by root dynamic pages like :slug. As a workaround, use more specific paths like /blog/:slug instead of just :slug for your dynamic pages. This issue is recognized and may be addressed in future releases.

The default .wstd.io domains are not indexed by search engines as they're meant to be development domains. If you want extra protection, you can check 'exclude from search' in all page settings. For additional security, you can add robots.txt file or meta tags like <meta name="robots" content="noindex,nofollow,noarchive">. If using Cloudflare, you can also add password protection. You don't need to delete the project - think of the .wstd.io domain as a staging server where you can test without affecting your live site.

To migrate a self-hosted Webstudio instance:

1. Run 'pnpm migrations migrate' to update the database schema
2. Ensure your Docker volumes are properly mapped to preserve data
3. Check that the old volumes are still in use with 'docker cli' commands rather than relying on GUI interfaces

Always verify your volume mappings before and after updates to prevent data loss.

To migrate or update a self-hosted Webstudio instance, run the migrations command: pnpm migrations migrate. This should handle database migrations and updates when moving to a new version. When updating Docker containers, the system should continue using existing volumes and data.

If you encounter issues where it appears that old volumes aren't being used, check with Docker CLI commands rather than relying on GUI tools, as the command line often provides more accurate information about volume usage. Always backup your data before performing migrations, and test the migration process in a development environment first.

For self-hosted builder migrations, run 'pnpm migrations migrate' to update the database schema. Docker volumes should persist between updates, so your data should remain intact when updating to newer versions.

The default .wstd.io domains are not indexed by search engines as they're meant to be development domains. If you want extra protection, you can check 'exclude from search' in all page settings. For additional security, you can add robots.txt file or meta tags like <meta name="robots" content="noindex,nofollow,noarchive">. If using Cloudflare, you can also add password protection.

When setting up Webstudio locally, if you encounter issues with TRPC tokens needed for the publishing flow and static build export, you can bypass this by using the Webstudio CLI directly instead of going through the internal publishing flow. The CLI provides a more straightforward way to export your projects without dealing with internal authentication tokens.

Webstudio requires CNAME records for custom domains. If your DNS provider converts CNAME to ALIAS for root domains (like Hostinger), this won't work because Webstudio only supports CNAME.

Solutions:

1. Use 'www' subdomain with CNAME pointing to Webstudio
2. Move to a DNS provider that supports CNAME flattening (like Cloudflare)
3. For unsupported TLDs (.de domains), register a .com equivalent on Cloudflare and redirect

The 'www' approach is recommended if CNAME flattening isn't available.

When setting up headless WordPress with Webstudio, you may encounter issues where data displays in the builder but not on the published site. This is often because WordPress hosting providers (like SiteGround) block Cloudflare Workers requests, treating them as bots. Contact your hosting provider to whitelist Cloudflare Worker IP addresses. SiteGround specifically requires adding Cloudflare IPs to their whitelist.

If animations aren't working, try these troubleshooting steps:

1. Check if you're using the latest animation engine - older JavaScript-based animations may not work properly
2. For self-hosted Docker containers, ensure you've updated to the latest Webstudio version and run 'npm install' to update all packages
3. Verify your animations work in the Webstudio builder first
4. Check if Safe Mode is enabled, which disables animations
5. Make sure your trigger conditions are properly set up

For privacy-focused web analytics, consider these open-source alternatives:

1. Umami - Simple, privacy-focused analytics that maintains visitor privacy and data ownership
2. Plausible - Lightweight, privacy-friendly analytics
3. PostHog - More comprehensive product analytics with web analytics features and heatmaps
4. Jitsu - Open-source alternative to Segment for aggregating events across multiple services without performance issues

These tools typically don't require cookie banners and provide better user experience.

If Webstudio appears to be down or you can't open projects, first try refreshing the page. If the issue persists, it may be due to a deployment issue which the team typically resolves quickly. You can check the Discord community for status updates or report the issue. Webstudio has fast response times for service interruptions.

Rybbit (rybbit.io) is an open-source, privacy-friendly analytics platform that's been recommended by the Webstudio community. It combines features from Umami, Google Analytics, PostHog, and Clarity, offering one of the best analytics UI experiences. It's positioned as a modern Google Analytics replacement that's next-gen, lightweight, and cookieless for web and product analytics.

Instead of implementing cookie consent banners, consider using GDPR-compliant analytics alternatives that don't require cookies. This avoids the need for cookie banners entirely and provides a better user experience. Cookie banners are considered a 'plague' by many developers, so privacy-focused analytics tools are often preferred.

While you can use any domain registrar, Cloudflare is recommended for DNS management because it supports CNAME flattening, which allows you to use root domains (without www) properly. Other registrars like Namecheap have limitations that can break email services and other domain-connected features.

Currently, there's no built-in dashboard feature to view page view usage directly in Webstudio. The recommended approach is to use external analytics tools (privacy-friendly options are available or Google Analytics). Page view limits are per account, not per domain. You can purchase additional page views through the pricing page. There are GitHub issues (5286 and 5239) tracking requests for adding internal page view tracking, which would provide more accurate data than analytics that can be affected by cookie consent and tracking opt-outs.

Some email providers may block emails from Webstudio's form service. If you're not receiving form submissions to your custom domain email (but Gmail works fine), try whitelisting Webstudio's email service with your email provider. This is common with providers like Strato and other regional email services that have strict spam filtering.

In Docker deployments, dynamic routes like ':slug' can intercept image asset requests (like '_image/**' routes), causing 404/302 errors when the slug is connected to a CMS. This is a limitation of the current router used for deployment. The workaround is to use more specific paths like '/blog/:slug' instead of root-level dynamic routes.

Webstudio's marketplace was launched recently compared to platforms like Webflow (which has had years to build their template library). Webstudio focuses on empowering the community to build and share templates rather than creating them internally. The roadmap includes importing Webflow and Tailwind templates, and community members can submit templates to the marketplace for review and approval.

Webstudio's marketplace was launched recently compared to platforms like Webflow (which has had years to build their template library). Webstudio focuses on empowering the community to build and share templates rather than creating them internally. The roadmap includes importing Webflow and Tailwind templates, and community members can submit templates to the marketplace for review and approval.

Webstudio's marketplace was launched recently compared to platforms like Webflow (which has had years to build their template library). Webstudio focuses on empowering the community to build and share templates rather than creating them internally. The roadmap includes importing Webflow and Tailwind templates, and community members can submit templates to the marketplace for review and approval.

Webstudio's marketplace was launched recently compared to platforms like Webflow (which has had years to build their template library). Webstudio focuses on empowering the community to build and share templates rather than creating them internally. The roadmap includes importing Webflow and Tailwind templates, and community members can submit templates to the marketplace for review and approval.

Middle-click support for dashboard navigation is a requested UX improvement. Currently, to open projects in new tabs, you need to either copy the project link and open manually, or go to dashboard and middle-click the project directly. This feature request has been noted by the team for future dashboard improvements.

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.

Currently, there's no built-in way to track page view usage directly from the Webstudio dashboard.

For now:

1. Use external analytics like Google Analytics or privacy-friendly alternatives mentioned in the analytics channel.
2. You can purchase additional page views through the pricing page at webstudio.is/pricing.

All pricing and page view limits are per account, not per domain. There are GitHub issues (5286 and 5239) tracking the addition of built-in usage analytics to the dashboard.