# ChatGPT Sites usage limits: what the 50% warning means · Stacktree Source: https://stacktr.ee/blog/chatgpt-sites-usage-limits [Skip to content](#main) [Stacktree](/)[Developers](/developers)[Agents](/agents)[Docs](/docs)[Use cases](/use-cases)[Pricing](/pricing)[Blog](/blog)[Dashboard](https://app.stacktr.ee)[Sign in →](https://app.stacktr.ee) By [ Steve Smith ](/about) · Founder, Stacktree · Last updated September 11, 2026 blog · 11 September 2026 # ChatGPT Sites usage limits, explained from the replies. OpenAI announced five million Sites and five new features on 11 September 2026. The most-liked reply was not about any of them. It was a Plus user with a 50% usage warning asking to pay for more, and a dozen others said the same thing in different words. Here is what the help center actually says the limit is, what happens when you reach it, what people are reporting, and how to stop spending quota on pages that do not need it. [ Get started free ](https://app.stacktr.ee/?join=1&from=seo_blog_chatgpt_sites_usage_limits) install npx stacktree-install Copy No card · 3 pages free · about a minute ## What is the ChatGPT Sites usage limit? A plan-specific cap, unpublished by OpenAI, on the combined hosting usage of all your Sites: how many you have, how much they store, and how much traffic they get. It applies during the public beta on Plus, Pro, Business, Enterprise and Edu. Reaching it blocks new Sites and added storage and can take a busy Site offline until usage drops. You cannot buy more yet. ## On this page - 01 [ What the help center says ](#rules) - 02 [ What counts toward it ](#what-counts) - 03 [ What people are reporting ](#reports) - 04 [ Two meters, not one ](#two-meters) - 05 [ How to reduce usage ](#reduce) - 06 [ What does not need to be a Site ](#static) ## What the help center says OpenAI's help center article on creating and managing ChatGPT Sites has a short section titled "Public Beta Limits". Quoted in full, because it is the only official text: "During the public beta, Sites usage is included up to plan-specific limits. ChatGPT will notify you as you approach a limit. If you reach a beta limit, you may be unable to create a new Site, add storage, or keep a high-usage Site publicly available until usage is reduced. You can still edit and manage existing Sites. Limits apply across all Sites on the account and may change during the public beta. Check the Sites experience for the limits currently shown for your plan or workspace. Enterprise and Edu limits may vary by workspace." Three things follow. The limit is per account, not per Site. It is not a fixed number, and the text reserves the right to change it. And the consequence is a freeze rather than a deletion: existing Sites keep working and stay editable, but you cannot add a new one, add storage, or (for a busy public Site) keep it public. ## What counts toward it The help center does not say. A user in the product lead's feedback thread posted the notice OpenAI sent when their account hit the cap, which does: "While ChatGPT Sites is in beta, the amount of hosting usage (a combination of number of sites, storage, and site visits) is limited. You can still edit existing sites, but you can't create new ones for now. Options to upgrade or purchase additional usage will be available after beta." So the meter has three inputs: how many Sites you have, how much they store, and how many visits they serve. That is why a single Site can show 50% used. A Plus user asked the obvious question under the announcement: "I have 1 site. Got a message saying you've used 50% of your usage. So I can have 2 sites?" Not necessarily. Two small quiet Sites might fit; one popular Site with a lot of images might not. The docs add one number: the D1 database is capped at 10 GB per Site, and R2 file storage has "no fixed storage limit". Both are per-Site technical ceilings, separate from the account-level beta cap, which can stop you adding storage long before you approach them. ## What people are reporting - Wanting to pay. The most-liked reply to the announcement: "Any plans to allow us to pay for more usage? Just got a 50% usage warning. If my site scales or I continue building, I'm happy to pay more. But doesn't seem to be an option." Another: "Please add optional upgrades of capacity. I am already using 100%." - Limits moving. From the feedback thread: "I get random emails changing my limit even when I don't do anything. I understand it's currently beta, but I can't really rely on Sites if I have no idea if or when I'll get cut off." - Versions eating space. "Please add a way to prune/delete prior versions of a Site. There is no way to do this currently, and after many changes the versions take up all the space for nothing." - Pricing clarity for serious use. "Love ChatGPT Sites, but we need to know what your future plans and pricing are for this feature before we can use it for any serious projects." And, from someone already hosting five or six Sites: "You need to be clear on usage for each plan." - Enterprise deletion. A separate reliability worry from an Enterprise admin: when an employee leaves, "all of their ChatGPT sites are automatically deleted, and we have no visibility on what those sites are." None of these are complaints about the product being bad. They are complaints about not being able to plan around it, which is the specific thing a beta cannot yet offer. ## Two meters, not one Building a Site and hosting a Site draw from different allowances, and the replies mix them up. Building runs through Codex, so it spends your plan's agentic or weekly usage: "I would have hosted it on chatgpt sites but I ran out of usage 24 hours after the last reset. Pro 20x here." That meter resets on a schedule. Hosting draws from the beta Sites cap described above, which does not reset; it only goes down when you delete things. A 50% Sites warning and a 0% weekly usage screen are two different problems, and the fixes are different. ## How to reduce usage - Delete Sites you do not need. Open Sites from the sidebar, choose Delete site, and type the slug to confirm. The help center is blunt: "you cannot restore deleted sites." Export anything you want to keep first, and note that export is not documented, so "keep" may mean copying the source out of the chat. One caveat before you delete in bulk: a user who removed a dozen Sites on a warning reported staying blocked, and the docs do not say how quickly the meter moves. [The deletion how-to](/blog/delete-chatgpt-site-free-usage) covers what deleting does and does not free. - Stop Codex publishing experiments. Several developers found Codex reaching for Sites whenever a task produced something viewable ("I had to add 'Never use ChatGPT Sites' to my AGENTS.md because Codex was putting every tiny local experience up on there"). Each stray publish is a Site with versions. [The AGENTS.md line that stops it](/blog/stop-codex-publishing-to-chatgpt-sites) is one sentence. - Move big files to R2. A community report describes a 256 MB per-Site ceiling and recommends storing images in R2 and referencing them from the database rather than bundling them into the Site. Unverified against the docs, but consistent with the "no fixed storage limit" line for R2. - Move finished static pages off Sites. This is the one most people miss, and it is the subject of the next section. ## What does not need to be a Site ChatGPT Sites scaffolds a full application behind every deployment: a framework, server logic, a database, a deployment pipeline, saved versions. That is the right shape for a game, a tracker, a dashboard with live data. It is the wrong shape for a finished document, and a lot of what gets published is a finished document: a report, a proposal, a one-pager, a prototype the client needs to look at once, a deck rendered as a page. Those are a single HTML file. Hosting one on Sites spends the same account-level quota as hosting an app, keeps accruing versions every time you tweak a heading, and puts the reader behind either a public URL or a ChatGPT sign-in. Publishing that file to [Stacktree](/private-html-hosting) costs none of your Sites allowance, and the caps there are the kind you can plan around: a number of pages and a storage size per page, printed on [the pricing page](/pricing) and returned by the API. Three pages free with a seven-day life, then 25 pages on Solo at $19 a month, unlimited on Studio. Visits are not metered against a quota, so a page does not go dark because it got popular. Each revision replaces the page in place on the same URL rather than stacking a version you cannot delete. And the link is private by default, opened by a client with no account, with a passcode or expiry when you want one. Keep the app on Sites. Put the document where documents belong. Fix it now You've read why the public link is a problem. Paste the artifact here and get a private one, no account, and a passcode if you want it. Paste HTMLDrop a fileno account · 24 h linkHTML to publishAdd a passwordPublish private link Spend Sites quota on apps, not on documents Reports, proposals and one-pagers are one HTML file. Publish them to a private link that costs none of your ChatGPT Sites allowance, with caps you can read on the pricing page. Three pages free, no card. [ Publish a page free → ](https://app.stacktr.ee/?from=blog_cta_chatgpt_sites_usage_limits&join=1) Free to try: 3 pages, each live for 7 days. Own domain from $19/mo. FAQ ## Frequent questions What are the ChatGPT Sites usage limits? + OpenAI does not publish numbers. The help center says "Sites usage is included up to plan-specific limits" during the public beta, that limits "apply across all Sites on the account and may change", and that ChatGPT shows the current limits in the Sites experience and notifies you as you approach one. A notice one user received describes the metered quantity as "a combination of number of sites, storage, and site visits". What happens when you hit the ChatGPT Sites limit? + From the help center: "you may be unable to create a new Site, add storage, or keep a high-usage Site publicly available until usage is reduced. You can still edit and manage existing Sites." So a limit does not delete anything, but it can stop new publishing and, for a busy Site, take it off the public internet until usage drops. Can you buy more ChatGPT Sites usage? + Not as of September 2026. The most-liked reply to OpenAI's 11 September announcement asked exactly this after a 50% warning ("I'm happy to pay more. But doesn't seem to be an option"), and OpenAI's own limit notice says options "to upgrade or purchase additional usage will be available after beta". Until then the only lever is reducing usage. Why did I get a 50% usage warning with only one site? + Because the meter is not a site count. It combines the number of Sites, their storage, and their traffic, and it is plan-specific. A Plus user in the announcement replies asked the same thing: one site, 50% used, "so I can have 2 sites?" A single Site with images, saved versions and steady visitors can use half a Plus allowance on its own. Do saved versions count against ChatGPT Sites storage? + Users believe so and the docs do not say otherwise. One reply to the announcement asked OpenAI to "add a way to prune/delete prior versions of a Site" because "after many changes the versions take up all the space for nothing". The docs describe saving and inspecting versions but no way to delete them. Treat every saved version as storage until OpenAI documents otherwise. Does a private ChatGPT Site count toward the limit? + Yes. Limits apply across all Sites on the account regardless of audience. A Site shared with invited viewers or your workspace still counts as a Site, stores its files, and records visits. The only audience-related effect of a limit is that a high-usage public Site may be taken off the open internet until usage falls. How do I reduce ChatGPT Sites usage? + Delete Sites you no longer need (deletion is permanent, there is no restore), stop Codex publishing local experiments to Sites by default, and move finished static pages off Sites entirely. A report, a one-pager or a prototype does not need a database and a server; hosting it on Stacktree costs none of your Sites quota and the caps there are page counts and storage, published on the pricing page. Keep reading ## Related guides - [ How to delete a ChatGPT Site The four steps, and whether deleting actually frees usage. ](/blog/delete-chatgpt-site-free-usage) - [ Stop Codex publishing to ChatGPT Sites The AGENTS.md line, and an explicit publish tool to give Codex instead. ](/blog/stop-codex-publishing-to-chatgpt-sites) - [ ChatGPT Sites explained The living status post: cost, access, domains, and what is still undocumented. ](/blog/what-is-chatgpt-sites) - [ ChatGPT Sites private sharing Who can open an invited Site, and why they still sign in. ](/blog/chatgpt-sites-private-sharing) - [ Stacktree pricing Page counts and storage per plan, in one table, no meter. ](/pricing) - [ Host AI-generated reports The document half of the category. ](/host-ai-reports) References ## Sources and further reading - [ OpenAI Help Center: Creating and managing ChatGPT Sites ↗ The "Public Beta Limits" section quoted above, and the permanent-deletion warning. ](https://help.openai.com/en/articles/20001339-creating-and-managing-chatgpt-sites) - [ ChatGPT Sites documentation ↗ Per-Site D1 (10 GB) and R2 ("no fixed storage limit") ceilings, saved versions, and the plan list. ](https://learn.chatgpt.com/docs/sites) - [ ChatGPT Sites update: 5M sites (@ChatGPT) ↗ The 11 September 2026 announcement whose replies supplied the usage quotes above. ](https://x.com/ChatGPT/status/2098457920291946894) - [ ChatGPT Sites feedback thread (Kath Korevec, OpenAI) ↗ Where the OpenAI limit notice was posted, along with the "random emails changing my limit" report. ](https://x.com/simpsoka/status/2098244223728505322) ## A cap you can read before you hit it Page counts and storage per plan, on the pricing page. Private links a client opens with no account. Revisions replace in place, no versions to prune. [ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_blog_chatgpt_sites_usage_limits) install npx stacktree-install Copy Private hosting for the HTML your agents make. [](https://betalist.com/startups/stacktree?utm_campaign=badge-stacktree&utm_medium=badge&utm_source=badge-featured)[Featured on](https://devhunt.org/tool/stacktree)[](https://buildlist.io)[Get started free](https://app.stacktr.ee/?join=1) ## Product - [Example deliverables](/examples) - [Custom domains](/custom-domains) - [Client feedback](/client-feedback-loop) - [One-time links](/one-time-view-links) - [See how pages get read](/page-engagement) - [Made with Stacktree](/made-with) - [Security](/security) - [Watch the demo](/demo) ## Agents - [All integrations](/agents) - [Claude Code](/claude-code) - [OpenAI Codex](/codex) - [Cursor](/cursor) - [Claude.ai connector](/claude-ai-connector) - [MCP server](/mcp-publish-html) - [Deploy from Claude Code](/deploy-html-from-claude-code) - [Skills](/skills) - [Slack app](/slack) - [n8n node](/n8n) - [Agent payments (x402)](/x402) ## Alternatives - [All comparisons](/alternatives) - [Head-to-head comparisons](/compare) - [Tiiny Host](/tiiny-host-alternative) - [GitHub Pages (private)](/github-pages-private-alternative) - [Vercel](/vercel-alternative-for-agents) - [ngrok](/ngrok-alternative-for-html) - [Display.dev](/display-dev-alternative) - [Static.app](/static-app-alternative) - [OpenAI Codex Sites](/openai-codex-sites-alternative) - [here.now](/here-now-alternative) - [Shippage](/shippage-ai-alternative) - [Best private hosting](/best-private-html-hosting) ## Use cases - [All use cases](/use-cases) - [Share with clients](/share-with-clients) - [Send a file to a client](/share-html-file-with-client) - [Share Claude artifacts](/share-claude-artifacts) - [Share Jupyter notebooks](/share-jupyter-notebook-html) - [Host Storybook privately](/host-storybook-privately) - [Architecture diagrams](/share-architecture-diagrams) - [AI-generated reports](/host-ai-reports) - [Internal HTML tools](/internal-tool-hosting) - [Private HTML hosting](/private-html-hosting) - [Vibe-coded page hosting](/vibe-coding-hosting) - [Leave a website builder](/website-builder-migration) ## Learn - [Blog](/blog) - [Glossary](/glossary) - [FAQ](/faq) - [Agent-loop hosting](/agent-loop-hosting) - [Why agents need a publish primitive](/blog/why-agents-need-a-publish-primitive) - [MCP servers explained](/blog/mcp-servers-explained-for-developers) - [What changed in the 2026-07 MCP spec](/blog/mcp-2026-spec-changes) - [Sites in Codex explained](/blog/sites-in-codex-explained) - [Private-by-default hosting](/blog/private-by-default-html-hosting) - [An agent paid us $1 (x402)](/blog/agent-paid-to-provision-itself) - [When a loop hits a paywall](/blog/loop-engineering-paywall) - [Pricing](/pricing) - [Self-host (new)](/self-host) - [Changelog](/changelog) - [Docs](https://stacktr.ee/docs) - [About](/about) © 2026 Stacktree · stacktr.ee [Privacy](/privacy)[Terms](/terms)[Security](/security)[Dashboard](https://app.stacktr.ee)[npm](https://www.npmjs.com/package/stacktree-mcp)[Sitemap](/sitemap.xml)[llms.txt](/llms.txt)[API spec](/openapi.json) --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt