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.
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.
Frequent questions
What is ChatGPT Sites? +
Are ChatGPT Sites public? +
Who can create ChatGPT Sites? +
What infrastructure do ChatGPT Sites run on? +
Can you put a ChatGPT Site on a custom domain, or make it private? +
Is ChatGPT Sites the same as Codex Sites? +
Can an agent or API publish to ChatGPT Sites? +
Related guides
- Can you make a Codex site public? The status post this launch just answered: updated same day.
- Sites in Codex, explained The original beta, and how the GA product differs.
- The private alternative When the deliverable should not be public at all.
- Cloudflare Drop, tested at launch The other launch this week, on the same substrate.
Sources and further reading
- Launch announcement (Jon Abrams, OpenAI) ↗ ChatGPT Sites to all paid subscribers, the example site, the OpenAI-Cloudflare collaboration confirmation, and the rollout answers.
- Engadget: OpenAI releases ChatGPT Work ↗ The wider launch context: ChatGPT Work, GPT-5.6, and Sites for all paid users.
- ChatGPT Sites documentation ↗ The official docs: the four sharing options, public publishing, custom domains, analytics, save/deploy versioning, D1/R2 hosting config. The primary source for every claim above.
- OpenAI Help Center: Creating and managing ChatGPT Sites ↗ Plan availability (paid plans except Free and Go, rollout order) and the launch exclusion of the EEA, Switzerland, and the UK.
- Example site (fetched at launch) ↗ The launch example we verified serves publicly with no login.
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 →