By · Founder, Stacktree · Last updated
blog · living status post · launch day

ChatGPT Sites is live for every paid subscriber.

The roadmap signal from June finally fired: Sites left its Codex beta and shipped to paid ChatGPT plans on July 9, with public publishing, hosted on Cloudflare. Here is what launched, what we verified within hours, what the docs have added since (custom domains, analytics), and what is still undocumented.

Get started free

What is ChatGPT Sites?

ChatGPT Sites (launched 9 July 2026, alongside ChatGPT Work and GPT-5.6) lets a paid ChatGPT subscriber ask for a live, hosted web app or page (dashboards, trackers, prototypes, portals, interactive reports) and get it running at {name}.openai.chatgpt.site, or on a custom domain where available. Sites can be published to anyone on the internet (we fetched the launch example: HTTP 200, no login), and the platform underneath is Cloudflare. It is the GA successor to Codex Sites.

What launched, verified

From the launch announcement and thread: Sites is available now to paid subscribers as part of the ChatGPT Work release; the announcement's own example site (a map visualization built "last night") lives at an openai.chatgpt.site subdomain. We fetched it within hours of launch: it serves publicly, HTTP 200, no ChatGPT account required to view. Rollout is staged: some Plus users reported not seeing the feature on day one, the docs hedge that availability "can depend on your plan, region, and workspace settings", and OpenAI's help center is explicit that Sites is not available in the EEA, Switzerland, or the UK at launch. The team calls this "still only just the start". The docs also settle update semantics: you save versions and deploy them, updates keep the same URL, and "every Sites deployment URL is a production deployment". Genuine replace-in-place.

Since launch day, the docs have filled in two early unknowns. Custom domains are documented: connect an apex domain or subdomain you already own by updating DNS records, where the feature is available, though not in Enterprise workspaces at launch. And built-in analytics is documented: total unique visitors and page views, plus both over time, though not for sites owned by an Enterprise workspace.

What changed from Codex Sites

Two things, both big. Availability: Codex Sites was a beta for team plans; the June signal that individual plans were coming "ASAP" took five weeks to land. Visibility: Codex Sites could not be viewed outside your authenticated workspace, which was its defining limitation. ChatGPT Sites flips that: with public publishing enabled, a site is on the open web. If you found our "can you make a Codex site public?" status post before today, the answer there was no; for ChatGPT Sites it is yes, and that post now says so.

The Cloudflare underneath

The launch thread confirmed Sites is "a collaboration between OpenAI and Cloudflare", and community digging identified Cloudflare Workers with SQLite and Durable Objects. Notably, Sites can reportedly export a Wrangler project of your site for hosting on your own Cloudflare account: a real portability story if it holds, though still absent from the docs. It is also a second consecutive datapoint (after Cloudflare Drop, launched the day before) that the biggest players are converging on the same shape: AI makes HTML, it needs a URL instantly, and Cloudflare is becoming the substrate either way.

What is still unknown

  • Gates without accounts. The private modes (invitation and workspace scoped) require signed-in viewers; no password or email-domain gate exists for account-free recipients, and no expiry is documented.
  • API or agent access. Created and managed in ChatGPT; the docs note there is no standalone CLI management view, and no public API or MCP surface exists for programmatic publishing.
  • Regional timeline. The EEA, Switzerland, and the UK are excluded at launch, and OpenAI has given no timeline for them.
  • Limits, indexing, export. Exact site counts and sizes ("plan-specific usage limits apply", unspecified), search-engine indexing behavior, and the community-reported Wrangler export: none documented yet.

Sites or a publish primitive

For a paid ChatGPT subscriber who wants a live app from a conversation, Sites is now the shortest path there has ever been, and public publishing removes its old dealbreaker. The choice that remains is sharper than it was at launch, because custom domains no longer separate the two. What does: who the viewer is, and who the publisher is. Sites viewers are either the whole internet or invited accounts; there is no gate a client can pass without one. And the publisher is a chat session, not an API. If the thing you are publishing is a deliverable to share with a client without a login, needs an expiry or a password, or gets published and revised by an agent over an API rather than a conversation, that is the other half of the category: pages as deliverables, private by default, with a read on how they landed. Both halves just got very real.

FAQ

Frequent questions

What is ChatGPT Sites? +
A feature launched 9 July 2026 for all paid ChatGPT subscribers, announced alongside ChatGPT Work and GPT-5.6: ChatGPT builds and hosts live web apps and pages (dashboards, trackers, prototypes, internal portals, interactive reports) at a hosted URL of the form {name}.openai.chatgpt.site. It is the general-availability successor to Codex Sites.
Are ChatGPT Sites public? +
They can be. The docs list four sharing options: owner and workspace admins, selected active users or groups, anyone in the workspace, and "anyone on the internet, only when public publishing is enabled" (we verified the launch example serves publicly with no login). That last option is the big change from Codex Sites, which had no way to show a site to anyone outside your authenticated workspace. In Enterprise workspaces, public publishing is off by default and must be enabled by an admin.
Who can create ChatGPT Sites? +
Paid subscribers on every plan except Free and Go, per OpenAI's help center, with Pro, Enterprise, and Edu first in the rollout order and Plus and Business following. Region matters too: Sites is not available in the EEA, Switzerland, or the UK at launch, with no timeline given. Free-plan availability also has no timeline.
What infrastructure do ChatGPT Sites run on? +
Cloudflare, per the launch team ("a collaboration between OpenAI and Cloudflare"). The docs confirm D1 (relational database) and R2 (object storage) as configurable options via .openai/hosting.json. Community reports at launch also described receiving a Wrangler project of a site for self-hosting on your own Cloudflare account, a notable portability story, though export is not in the docs yet.
Can you put a ChatGPT Site on a custom domain, or make it private? +
Custom domain, yes, since the docs landed: you can connect an apex domain or subdomain you already own by updating DNS records, where the feature is available (not in Enterprise workspaces at launch). Private, partly: the invitation and workspace modes require the viewer to be a signed-in, invited account. There is no password or email gate a client can pass without an account, and no documented expiry. Those are the gaps if the deliverable needs gated, account-free viewers.
Is ChatGPT Sites the same as Codex Sites? +
It is the same lineage gone GA: the launch framed Codex and ChatGPT Work as unified, and Sites moved from a Codex beta for teams into ChatGPT for all paid subscribers, with public viewing. Our Codex Sites explainer covers the original; this post tracks the GA product.
Can an agent or API publish to ChatGPT Sites? +
Not that is documented: Sites is a ChatGPT product surface, created in conversation. There is no public API, MCP surface, or CLI for it at launch. If your publisher is an agent pipeline rather than a chat session, that is a different product shape: API/MCP-native publishing.
Keep reading

Related guides

References

Sources and further reading

Private version of the same magic?

An agent publishes over MCP or API, the link is unguessable by default, gates and expiry are one call, and revisions keep the same URL.

Sign up free →