Can you make a Codex Site public? Yes, since the July 9 GA.

The short answer

Updated 18 July 2026: yes. Sites went GA as ChatGPT Sites on 9 July 2026, and public publishing is a documented sharing option: anyone on the internet, when enabled, with Enterprise admins controlling the toggle. Custom domains are documented too, where available. The full arc from workspace-only beta to public GA is in our Codex Sites explainer.

What you still cannot do is gate a non-public site for someone without an account. The private modes require a signed-in, invited viewer; there is no password mode, no email gate, no expiring link, and no API or MCP surface for publishing from an agent outside the chat. Availability is also regional: the EEA, Switzerland, and the UK were excluded at launch.

The sections below preserve the beta-era record, written when the answer was no. We keep them because the question is still asked in that form, and because the history explains what changed and when.

The three beta access modes, and why there was no public toggle

Beta-era record, written June 6, 2026. Superseded by the GA release above; the GA docs replaced these three modes with four sharing options, including public publishing.

Codex Sites controlled who could view a deployment at the workspace level. OpenAI documented three modes:

• admins_only, visible to the site owner and workspace administrators.
• workspace_all, visible to all active users in the workspace.
• custom, visible to specific active users or workspace groups you choose.

The common boundary was the important part. Every documented mode required the viewer to be an active member of your OpenAI workspace. The custom mode looked like it might be the escape hatch, but it was not: the specific people you named still had to be active users or groups inside your workspace. So there was no documented setting that turned a Site into something an anonymous visitor, a client, or anyone without a workspace seat could open. That is why the answer to "make it public" was "no documented public option" rather than "use this option."

It was a coherent design for what the beta was built for. The feature was positioned around internal team tools, and for an internal tool "only people in our workspace can see this" is the right default. The friction showed up only when the thing you built needed to reach someone outside the company, which is a different job, and the GA release later split the difference by adding a fully public mode.

Which plans have Codex Sites today

Beta-era record, written June 6, 2026. Superseded: since 9 July 2026, ChatGPT Sites is available on every paid plan except Free and Go, outside the EEA, Switzerland, and the UK.

Sites in Codex was in preview, available to ChatGPT Business and Enterprise workspaces only, with OpenAI describing more plans as rolling out later. The docs named only those two plans and listed no specific plans for the rollout. Here is the documented state as of June 6, 2026.

To be precise about the "not documented" row as it stood then: OpenAI had not named any other plan as supported, only that more plans were rolling out later. The rollout arrived on 9 July 2026, five weeks after this table was written.

What "non-team plans ASAP" means, and does not

OpenAI has signaled wider availability, but only in roadmap terms, and not in the documentation. The launch landed on June 2, 2026; the roadmap post followed on June 4. On that date, Rohan Varma of OpenAI's Codex team posted on X that Sites is "live in Codex for teams," that improvements will ship constantly over the coming weeks, and that the team is "working hard to launch it to non-team plans ASAP."

Two things matter about how to read that. First, it comes from an X post, not the docs, so it is intent rather than a committed feature. We attribute it to the post for exactly that reason. Second, "ASAP" is not a date. It tells you non-team plans are on the roadmap; it does not tell you when, and it does not tell you that a public-viewer mode is part of the plan at all. The plan-availability question and the public-link question are separate, and the X statement speaks to the first, not the second.

The demand for the second is on record too. In the June 4 announcement thread, one user replied that they would love public links without authentication and said they could not find a way to make a site public yet. We note that as one user in the announcement thread, not as a commitment from OpenAI. It is useful signal that the public-link gap is felt, nothing more.

Postscript, 18 July 2026: both questions resolved on 9 July. The plan side widened to all paid plans except Free and Go, and public publishing shipped as a documented sharing option. "ASAP" turned out to mean five weeks.

Where an open publish primitive still fits

Full disclosure: this section describes Stacktree, which is our product, so read it as us explaining where we fit rather than as neutral advice. When this post first ran, this section was the only way to get a public link for agent output; a paid ChatGPT subscriber outside the excluded regions can now get one from Sites directly. What the GA did not cover is the case in between public and invited-accounts, and the case where the publisher is an agent rather than a chat.

The pattern is not to extract or export a Codex Site. There is no documented way to do that, and Stacktree does not do it. Instead, you have the agent render a static HTML view of what you want to show, then publish that HTML to an open host. Codex can do this directly: it can generate the HTML and call a publish tool over MCP, without leaving the session.

Stacktree is the open host in that pattern. It is an MCP-native publish primitive, so it works from Claude Code, Cursor, Codex, and Claude.ai rather than inside one agent. A site is private by default, and the unguessable URL is the credential, so the viewer needs no account and no workspace seat to open it. You can add a shared password, an email-domain gate verified by magic link, an expiry, or end-to-end encryption if you want more than the URL; that is the pattern for sharing a page with a client without a login and without making it public. Custom domains are available on the Pro plan via Cloudflare for SaaS, update_site replaces the content in place at one stable URL, and it is source-available and self-hostable on your own Cloudflare account (Workers, R2, and D1). Pricing is a flat $0, $8, or $19 per month, never per seat, and the free tier plus an anonymous 24-hour first publish lets you try it with no account. It also works from the UK and EEA, where Sites is not available at launch.

The trade is real and you should weigh it. Stacktree hosts static HTML only. There is no server logic, no application database, and no in-browser editor. So if what you need is a full app with persistence, the kind Sites is built to deploy with D1 and R2 behind it, Stacktree is not that, and Sites is the right tool. Stacktree fits the narrower case: a page anyone you choose can open by link, gated or not, with no login, on your own domain if you want, that you can take with you. The two are not substitutes; they answer different questions.

What would change this answer

This is a living status post, refreshed whenever OpenAI ships a change. The original watch-list from June 6 is now mostly resolved; here is the scorecard as of 18 July 2026:

1. A public or link-only viewing mode. Resolved, 9 July 2026. Public publishing is documented: anyone on the internet, when enabled; off by default in Enterprise workspaces.
2. An anonymous or password-only share option. Still open. This is now the sharpest remaining gap: no password, no email gate, no expiring link, so a non-public site still requires an invited, signed-in viewer.
3. Availability on more plans. Resolved, 9 July 2026. Every paid plan except Free and Go. The open half is regional: the EEA, Switzerland, and the UK were excluded at launch with no timeline.
4. Custom domain support. Resolved in the GA docs. Connect an apex domain or subdomain you own via DNS records, where available; not in Enterprise workspaces at launch.
5. Export or self-hosting. Still open. Community reports at GA described a Wrangler project export; the docs do not document one.

As the remaining items are documented, we will update this post and note the date. Until then, the answers above reflect the documented state and are dated accordingly.