Can ChatGPT Build and Host a Website? What It Can Actually Do

Yes — ChatGPT can build and host a website directly, through a public-beta feature called ChatGPT Sites, or it can generate portable HTML and CSS as a code block that you deploy yourself. These are two different, separately documented routes. OpenAI's help center describes Sites plainly: "ChatGPT Sites lets you create, preview, publish, and share interactive websites and lightweight apps" (OpenAI Help Center, "Creating and managing ChatGPT Sites", checked September 2026). This guide covers what Sites actually does, who can use it, its documented limits, and when the older code-block-and-deploy-elsewhere route is still the right one.

What is ChatGPT Sites, and how do I start one?

To trigger it, "simply ask ChatGPT to build you a website with a description of what you want the website to do. You can also use @Sites in your prompt to specifically trigger building a website" (same source). ChatGPT generates the site, gives you a private preview to review, and refines it based on follow-up prompts — the same conversational loop as any other ChatGPT request, just producing a live web project instead of text.

Availability is limited by plan and region. "ChatGPT Sites is available in public beta for ChatGPT workspaces, Plus, and Pro accounts," and it's explicitly not everywhere: "Sites is not available on Free or Go, or in the EEA, Switzerland, or the United Kingdom at launch" (same source). Inside a Business workspace, Sites is on by default; inside Enterprise, an admin controls it through role-based access, and "public publishing is off by default and must be enabled by an admin before eligible members can publish publicly" (same source). Because it's a public beta, capacity is capped too: "Sites usage is included up to plan-specific limits," and hitting one can mean "you may be unable to create a new Site, add storage, or keep a high-usage Site publicly available until usage is reduced" (same source) — though you can still edit and manage what you've already built.

How do publishing and sharing actually work?

Building a Site and making it live are separate steps. "When you deploy, ChatGPT generates a Site URL. Every deployment URL is a production URL," and OpenAI recommends reviewing before you commit: "save a version first and deploy only after you have reviewed it" (same source). Access is a deliberate choice at publish time, not a default: your options are "Owner and workspace admins," "Selected active users or groups, and named external viewers," "Anyone in the workspace, where supported," or "Anyone on the internet, only when public publishing is enabled" (same source) — and OpenAI flags that last one directly: "If you choose Anyone on the Internet, the Site will be publicly accessible. Carefully review your Site before proceeding" (same source). Once public, "A public Site is available without ChatGPT workspace access" (same source) — a visitor doesn't need a ChatGPT account to open it.

You can also invite a named person outside your workspace as a view-only visitor without making the whole Site public, and a workspace member can get Can edit access: "After the owner publishes the Site for the first time, an editor can publish later versions to the same Site URL" (same source). Only the owner controls "who has access, change the Site name or URL, transfer ownership, or configure owner-only settings such as secrets and custom domains" (same source). Taking a Site down is either a visibility change or permanent: "Deleting a site permanently removes it, and you cannot restore deleted sites" (same source).

Can I connect a custom domain or take payments?

A custom domain is documented, with real limits. "Where custom domains are available, Sites does not register a domain for you. You must already own the domain and be able to change its DNS records," and the feature isn't universal: "Custom domains are not available in Enterprise workspaces at launch" (same source). Connecting one is a standard DNS flow: open the Site's settings, select Add domain, then "Copy the DNS records and values Sites provides, and add them through your domain provider" (same source).

Payments are possible but entirely on you to run: "If you want to sell goods or services or collect payments through your ChatGPT Site, you can do so by using a third-party payment processor," and OpenAI is explicit that responsibility stays with you — "you are responsible for connecting, configuring, and maintaining any third-party payment processors you choose to use," including "fulfillment, delivery, refunds, customer support" and any related taxes (same source). Sites also can't process certain data at all: it "must not process sensitive data such as Protected Health Information or payment-card data (unless solely through a third-party payment processor)" (same source).

What are the documented limits?

Sites runs on a specific hosting runtime, not an open framework choice: "Sites is designed for web experiences that can be hosted through the supported Sites runtime," and "Some frameworks, private networks, databases, background services, and hosting patterns may not be supported" (same source). It also doesn't yet support data residency controls: "ChatGPT Sites does not support data residency or inference residency at launch. This includes deployed Sites, Site code, D1/R2 data and file storage, artifacts, and logs" (same source) — relevant if your organization has a compliance requirement around where data lives. And it isn't available everywhere in the app: "Sites is not available in the ChatGPT Classic app" (same source).

What if I just want portable HTML files instead?

Sites isn't the only documented route, and it isn't always the right one — Free and Go accounts don't get it at all, and a Site's hosting runtime has real constraints on frameworks and backends. OpenAI's separate documentation for writing blocks and code blocks covers the alternative: "Writing and coding functionality is available directly in chat responses through writing blocks and code blocks" (OpenAI Help Center, "Working with writing blocks and code blocks in ChatGPT", checked September 2026). A code block can preview supported content directly in ChatGPT — "Switch between Code and Preview for supported previews," with "HTML pages" listed among the supported preview types — and, separately, "Share a read-only link for supported code blocks, when sharing is available" (same source). That's a read-only view of the code and its preview, not a hosted, publishable website with its own domain and access controls the way a Site is.

If your goal is a plain index.html and styles.css you review and deploy to a host of your choice, that's exactly the workflow our ChatGPT static landing page guide and static website publishing guide walk through — written before ChatGPT Sites existed as a documented feature, but still the right path when you specifically want portable files rather than a ChatGPT-hosted URL. One older ChatGPT capability worth a note: OpenAI's Capabilities Overview page still links to a "Canvas" help article as a co-writing and code-editing workspace, but that linked article no longer resolves when opened directly — the current, live documentation for working with code and drafts in chat is the writing/code blocks article above, not Canvas.

A quick reference

Is Figment a fit if I want a Site built this way?

Not for the same job. ChatGPT Sites builds and hosts an interactive website or lightweight app from a prompt, with its own generated code and runtime. Figment publishes a website from a design you build in Figma through its Figma plugin; it doesn't generate a site from a text prompt, and its AI editor is public now, working on a separate static copy of a site — still not a public product. If you already have (or want to design) a Figma file rather than describe a site in chat, that's the case where Figment, not ChatGPT, is the right tool.

Bottom line: ChatGPT can genuinely build and host a website today, through ChatGPT Sites — a public-beta feature with real plan gates, a supported-runtime limit, and documented controls for sharing, custom domains, and takedown. That's separate from the older, still-useful route of asking ChatGPT for a plain HTML/CSS code block and deploying it yourself, which remains the better fit outside Sites' plans, regions, or framework support. Check OpenAI's own help center before relying on either, since Sites is a beta and its limits are described as subject to change.