Frequently asked questions

Currently, Webstudio's CLI export generates compiled output that isn't easily readable or editable due to lack of component separation. While you can export static sites and publish them outside of Webstudio Cloud, the code isn't optimized for manual editing. For AI-powered website generation and editing, Webstudio is developing a separate tool called Inception (webstudio.is/inception) for design exploration, while maintaining Webstudio as a precision tool for professional development.

When you export static code from Webstudio, direct edits to the HTML may not appear in the browser due to the /assets/entries scripts that handle the styling and functionality. If you need to convert to PHP or integrate with a CMS like Drupal, consider using Webstudio's Content Blocks for editable areas instead. For complex integrations, using the CMS as a headless solution (via API) with Webstudio is recommended rather than rewriting the exported HTML.

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.

Unfortunately, you cannot use the Webstudio CLI without publishing first. The build is created when you publish and is needed to get synced via CLI. If you want privacy for your wstd.io domain, consider self-hosting the Webstudio builder (not just the site) to use Pro features without cloud publishing requirements.

Export timeouts can occur even with simple sites. If your export consistently fails, try reducing the complexity of your site temporarily or contact Webstudio support. The issue may be related to server resources or specific elements on your page that are causing the export process to hang.

Intermittent server-side issue or heavy assets. Steps:

1. Retry later (could be transient load)
2. Optimize large media / reduce oversized assets
3. Temporarily remove unusually large collections or heavy embeds
4. Check browser console & network panel for failing requests
5. Contact support with project ID if a minimal single-text page still times out

Known export pipeline issue affecting some MP4s. Keep original sources; after export replace /assets/*.mp4 with originals. Report cases so the build pipeline can be patched. Cloud-hosted playback is unaffected.

Video file corruption during export is a known issue where MP4 files may become corrupted during the build process. As a workaround, manually replace the corrupted video files in your exported /assets folder with the original files from your local machine. This issue specifically affects the export process and doesn't impact videos when using Webstudio cloud hosting.

Export timeouts can occur even for simple sites with basic text and images. This is typically a server-side processing issue rather than a problem with your site content. If you're experiencing consistent export failures, try again later or contact support, as this usually indicates a temporary server issue rather than something wrong with your site structure.

Export timeouts can occur due to various factors including large assets, complex pages, or temporary server issues. Try reducing image sizes, optimizing assets, or breaking complex pages into smaller components before exporting. If the issue persists with a simple page containing just text and a few images, it may be a server-side issue that should be reported to support.

Export timeouts can happen with larger projects or those with many assets. If you have a simple site with just text and a few images that's timing out, this may be a temporary server issue. Try again later or contact support if the problem persists.