How to build with ChatGPT Sites
Plan the request, create the site, inspect the private preview, refine observed problems, and publish only when the experience is ready.
What ChatGPT Sites is
ChatGPT Sites is a public-beta capability for creating, previewing, publishing, and sharing interactive websites and lightweight apps from ChatGPT Work on the web, or Work or Codex in the desktop app.
Create a Site
Describe the site and include its audience, job, content, files, routes, interactions, constraints, and boundaries. Mention a website or use @Sites so the request enters the website-building workflow.
Write an effective prompt
Specify the product before the appearance. Give routes distinct jobs, define interactions and states, provide real content and proof, state what must not be fabricated, and require mobile and keyboard testing.
Edit an existing Site
Name the route, observed problem, desired result, and what must stay. Ask for evidence of function, not just visual rearrangement. Continue in the same project so source and decisions remain attached.
Preview, save, publish, and deploy
Review the private result and request changes before publication. A saved version and a deployed version are different states. Publishing and access can depend on workspace permissions and product availability.
Connect a custom domain
Current official documentation describes custom-domain support. Use the records supplied in the domain flow, preserve unrelated email records, and test root, www, HTTPS, and redirects.
Good use cases
OpenAI highlights dashboards, trackers, calendars, prototypes, internal portals, reports, and interactive tools. Public editorial and marketing experiences can also fit when the managed workflow matches long-term needs.
Current limitations
Sites is in public beta. Plan-specific usage limits apply across Sites and may change. Official documentation does not state a user-controlled D1 point-in-time restore, chosen data residency, regional-failover promise, throughput commitment, or Sites-specific availability SLA. Saved versions protect application releases, not live database contents.
Fast creation and production readiness are different jobs.
Use the Sites-versus-Azure operating guide to decide where customer data, APIs, queues, backups, monitoring, and support controls should live before wide distribution.
Open the production guide →