What Is ChatGPT Sites? Plans, Limits, and Who Can Open One

The short answer

ChatGPT Sites turns a ChatGPT conversation into a hosted web page or application at a URL. You describe what you want. ChatGPT writes the code, hosts it, and gives you an address. You can refine it in the same conversation, save versions, and choose who can open it.

OpenAI introduced the feature in early June 2026 as Codex Sites, inside the Codex app. On 9 July 2026 it renamed the feature ChatGPT Sites. It also added Sites to ChatGPT Work on the web and to the combined ChatGPT desktop app. Search results and older guides still say Codex Sites. They describe the same product.

What a Site is

A Site is a hosted web application, not a file. OpenAI runs it on a managed runtime that supports HTTP, HTTPS, and WebSockets. Each Site can use a D1 relational database, with a 10 GB limit, and R2 object storage, with no fixed limit. D1 and R2 are Cloudflare's database and storage products. A Site can also hold runtime environment variables and secrets.

This shape matters when you decide what to build with it. A dashboard with saved state, a tracker, a portal, or a game fits the container. A one-page report also fits, but the container is larger than the page needs.

You can start a Site from a prompt, or you can link a compatible local project. A local project stores its link in a .openai/hosting.json file. That file holds the provisioned project ID and any database or storage bindings.

Which plans include it, and what it costs

Sites is in public beta on Plus, Pro, Business, Enterprise, and Edu. It is not on the Free or Go tiers. The rollout was staged. Pro, Pro Lite, Enterprise, and Edu received it first. Plus and Business followed over the days after launch.

There is no separate price. OpenAI includes Sites in the plan up to plan-specific limits. Those limits are not on the pricing page. ChatGPT shows them inside the product, for your plan or workspace.

The 9 July launch excluded the EEA, Switzerland, and the United Kingdom. The current developer guide lists no regional exclusion. Check the Sites view in your own account before you plan a rollout for a European team.

What the beta limits do

Every Site on your account shares one set of limits. The limits combine the number of Sites, storage, and traffic. ChatGPT notifies you when you approach a limit.

When you reach a limit, three things can happen. You may be unable to create a new Site. You may be unable to add storage. A high-usage public Site may lose its public availability until usage drops. You can still open, edit, and manage the Sites you already have.

The third consequence is the one to plan for. A public Site that receives real traffic is the Site most likely to reach the traffic limit. The limit then removes public access from the Site that most needed it. OpenAI says the limits can change during the beta.

Who can open a Site

Access is the part of Sites that people most often misread. A new Site does not start public. It starts locked to its owner and the workspace admins. The owner then widens the audience in steps.

Three rules sit under this table.

Every non-public viewer needs a ChatGPT account. An invited outside person must sign in with the account that received the invitation. There is no company-email gate, no password on a link, and no expiry setting between the locked options and the public one.

Public is public. A public Site opens for anyone who has the address, with no sign-in. On Enterprise, public publishing is off by default. An admin must enable it and give the member permission to publish.

Sign in with ChatGPT is identity, not access. A public Site can add Sign in with ChatGPT so the app knows who the visitor is. That gives the app saved progress or personal views. It does not close the Site to the public.

Named outside invitations arrived in September 2026. They are rolling out on Plus, Pro, Business, and Enterprise. Enterprise admins control whether members may invite people outside the workspace.

Editing, versions, and publishing

Since August 2026, a Site owner can give edit access to other people. An editor must be an active member of the same workspace. Editors can change and save a Site. After the owner publishes the Site for the first time, editors can publish later versions to the same address.

Publishing has two stages. First you save a version. That creates a candidate you can review. Then you deploy a version. That puts the selected version at the production address. The two stages let you review before the change reaches viewers.

Only the owner can change who has access, rename the Site, or change its address. Only the owner can transfer ownership or manage owner-only settings such as secrets and custom domains. Editors can read live database data. Deleting a Site cannot be undone. OpenAI says a deleted Site cannot be restored.

Custom domains

You can connect an apex domain or a subdomain that you already own. Sites does not register a domain for you. You change the DNS records at your registrar, and the Site answers at your address.

Custom domains are not available in Enterprise workspaces at launch. That is the plan most likely to need one. If your team is on Enterprise, plan for the ChatGPT-hosted address for now.

What Sites does not do

Five gaps matter for teams. OpenAI documents each of them.

1. No management from the command line or the IDE. Sites has no standalone Codex CLI management view and no IDE extension view. You can edit a local project in the CLI. Saving, deploying, sharing, and configuring a Site return you to ChatGPT on the web or desktop.
2. No API, CLI, or MCP publish path for other agents. OpenAI documents no way for Claude Code, Cursor, a CI job, or a local model to create or update a Site. A Site is made and managed inside ChatGPT.
3. No data or inference residency at launch. This covers deployed code, database and storage contents, artifacts, and logs. Regulated buyers should read this line twice.
4. No traffic analytics for Enterprise-owned Sites. Other plans see unique visitors and page views over time.
5. Restricted uses. A Site cannot process protected health information or payment-card data. It cannot enable financial transactions. It cannot target children under 13 or the applicable digital-consent age.

One more number sets expectations. In September 2026 an OpenAI Sites team member said the product passed 5 million hosted Sites. OpenAI does not define that count. It may include every Site ever created. Treat it as a scale signal, not an active-use figure.

When the page needs to live somewhere else

A Site is the right container when ChatGPT is building an application and the people who open it have ChatGPT accounts. Many of the things people build are not applications. They are pages. A report, a dashboard export, a prototype, a specification.

Those pages meet three limits in Sites. The colleague who reviews the report may not have a ChatGPT account. The same report may come from Claude Code or Cursor next week, and Sites has no path for those agents. And the audit question, who opened this and when, has no answer for an Enterprise-owned Site.

display.dev hosts the page instead of the application. Your agent publishes an HTML or Markdown file from the command line, from MCP, or from a browser upload. The file gets its own URL. You choose the audience for that URL.

• Public, for anyone.
• Company, for everyone at your organization. On the Pro plan they sign in with the Google or Microsoft account they already use. On every plan, they can sign in with a one-time password sent to their email address.
• Private, for you and the people you invite by email. An invited person outside your organization enters the one-time password sent to that address. They create no account.

An update keeps the same URL. Paid plans keep earlier versions, up to 50 on Pro. Reviewers comment on the page, and the next agent reads the comments through MCP. A reviewer with edit permission can correct a line in the page in the browser. The Pro plan records who opened each artifact and keeps 90 days of audit logs.

Two honest limits. display.dev hosts a file, not an app runtime with a database. And publishing to display.dev from inside ChatGPT needs the ChatGPT connector, which requires ChatGPT Business or Enterprise. On Plus or Pro, save the HTML from your project and run dsp publish ./report.html from the terminal, or drop the file on the dashboard.

Publish your first page free – 3 gated artifacts on the Free plan, unlimited viewers, no card required.

We checked every plan, limit, and sharing claim against OpenAI's Sites developer guide and help center on 22 September 2026. Sites is in beta. Check the Sites view in your own account for the limits that apply to you.

Sources and further reading

• Sites developer guide – OpenAI Learn
• Creating and managing ChatGPT Sites – OpenAI Help Center
• Managing ChatGPT Sites for your workspace – OpenAI Help Center
• What's new – OpenAI Learn
• Sharing OpenAI Codex output externally: what Codex Sites does and does not do
• What is gated publishing?