Frequently asked questions

Yes, you can create photography portfolios that automatically generate album pages based on Google Drive folders. Use the Google Drive API (REST API v3) to fetch photos from specific folders and display them as sliders or slideshows in Webstudio. You'll need to set up API authentication and create resources in Webstudio that connect to your Google Drive folders. This allows for automatic updates when you add new photos to your Drive folders.

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.

Currently, to update an image used on multiple pages, you need to upload a new image, manually update all pages that use it, and delete the old image. For reusing elements/layout on different pages, you can use Slots. For single pieces of data like image URLs, you can use Data Variables. A feature for automatic image replacement across all instances (GitHub issue 3268) is planned for the future.

If CMS images appear broken in the builder but work when accessing the URL directly, it's likely a permissions issue with your CMS setup. For Directus, check that the assets have proper public access permissions. The image URL should be accessible without authentication. Directus has many permission settings that can affect asset access.