OpenAIReleases

Illustration: a grey wire-o desk tent calendar with blank week columns, three-quarter view on black.
Illustration

ChatGPT Sites drops the fixed creation cap for Plus and Pro

Plus and Pro can create Sites without a fixed count limit. Codex usage and storage limits still apply, including 10 GB per Site database.

If you build internal tools or lightweight apps in ChatGPT Sites on Plus or Pro, you are no longer blocked by a fixed count of Sites you can create. Usage and storage limits still apply, and building or editing a Site still counts toward Codex usage.

What changed#

ChatGPT release notes, in a section titled "Site limits (Plus and Pro)," now say: "There is no longer a fixed limit on the number of Sites you can create. Usage and storage limits continue to apply."

The Sites help article matches that for Plus and Pro: "If you use ChatGPT Plus or Pro, there's no fixed limit on the number of Sites you can create. Usage and storage limits still apply across your Sites." The FAQ adds: "Sites hosting is currently included with ChatGPT Plus and Pro." Each Site's database can store up to 10 GB. File storage has no fixed storage limit per Site.

Before vs after. Before this note, Plus and Pro sat under a fixed creation count (the prior numeric cap is not restated in the new wording). After: no fixed creation count; shared usage and storage limits still gate how many Sites you can keep productive.

Why it matters#

Our read: Sites is how many teams turn a recurring workflow into a shareable dashboard, resource hub, or small app without leaving ChatGPT. A fixed creation cap forced cleanup or consolidation when you wanted one Site per project or client. Removing the count limit matters most for people who already pay for Plus or Pro and hit the old ceiling while still having Codex and storage headroom. It does not mean unlimited build traffic: editing still burns Codex usage.

How to use it#

Create a Site (from the help center):

  1. On web, select Work. In the desktop app, select ChatGPT then Work, or select Codex. Sites is not available in ChatGPT Classic.
  2. In the chat, describe the website you want. Include the word "website" or mention @Sites.
  3. Add the content, files, data, links, and constraints ChatGPT should use. Use only material you have permission to share.
  4. Review the preview ChatGPT generates. Ask for changes until it is ready.
  5. When you deploy, ChatGPT generates a Site URL. Every deployment URL is a production URL. Save a version first if you want to review without updating the live Site.
  6. Use Share to set who can open it (owner and admins, selected people, workspace, or public when enabled), then Publish.

Copyable starter (from OpenAI's Sites help article resource-hub example):

Use @Sites to build a searchable resource hub from the materials I provide. Add filters and a short description of when to use each resource. Use only supplied materials, ask me about missing details, and show a clear message when nothing matches. Keep links to the original resources. Save a version for review before publishing.

Good to know#

  • Codex meter still runs. "Building or editing a Site counts toward your Codex usage." Running and hosting (traffic and storage) are separate.
  • Shared limits can still block a new Site. "If you reach a shared limit, you may be unable to create a new Site, even if it won't use storage."
  • 10 GB database per Site. File storage has no fixed per-Site storage limit.
  • Hosting included for now. FAQ: hosting "is currently included" with Plus and Pro.
  • Enterprise is different. Enterprise hosting charges are "currently waived," but building or editing still counts toward Codex usage. Public publishing in Enterprise is off by default.
  • Not on Free or Go. Sites requires Plus, Pro, or a supported Business or Enterprise workspace.

What to watch: whether OpenAI restates a soft guidance number for healthy Site counts, and when Enterprise hosting charges leave the waived period.

Sources#

Last checked: 2026-10-16

Sources

  1. help.openai.com
  2. help.openai.com

Something wrong? Tell the bot