# How to delete a ChatGPT Site, and whether it frees up usage · Stacktree Source: https://stacktr.ee/blog/delete-chatgpt-site-free-usage [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 · how-to · 11 September 2026 # Delete a ChatGPT Site. Then check whether it helped. The usage warnings started arriving in August, and the first thing most people try is deleting Sites. That works as a deletion: four clicks, permanent, no undo. As a way to get unblocked it is less certain, and OpenAI's docs never promise it. Here are the exact steps, what deletion does and does not free, why the weekly reset does not touch hosting usage, and the levers that reduce it without losing work. [ Get started free ](https://app.stacktr.ee/?join=1&from=seo_blog_delete_chatgpt_site_free_usage) install npx stacktree-install Copy No card · 3 pages free · about a minute ## How do you delete a ChatGPT Site? Open Sites from the ChatGPT sidebar, select the Site, choose Delete site, type the Site slug to confirm, and select Permanently delete. Deletion cannot be undone and there is no documented export, so save anything you need first. Deleting removes the Site and its storage from your account's beta usage, but OpenAI does not document how quickly a block lifts afterwards. ## On this page - 01 [ The steps, from the help center ](#steps) - 02 [ Does deleting free up usage? ](#frees) - 03 [ Why usage does not reset weekly ](#reset) - 04 [ What you cannot delete ](#cannot) - 05 [ Three levers that reduce usage ](#levers) - 06 [ Before you delete a page someone has the link to ](#before) ## The steps, from the help center - In ChatGPT on the web or in the desktop app, open Sites from the sidebar and select the Site. - Copy out anything you want to keep. Export is not documented, so the conversation that built the Site is your source of record: ask ChatGPT for the files or content you need before you go further. - Select Delete site and follow the prompt. - Type the Site slug in the dialog, then select Permanently delete. The help center's warning is worth quoting in full: "Deleting a site permanently removes it, and you cannot restore deleted sites." It also notes a gentler option in the same section: if what you want is the Site gone from an audience rather than gone entirely, use Share settings to restrict access to a select set of people, or to yourself. That is the "take down" path, and it matters for the usage question below. ## Does deleting free up usage? Partly, and not on a documented schedule. The help center says that when you reach a beta limit you may be unable to create a Site, add storage, or keep a busy Site public "until usage is reduced". Usage, per the notice OpenAI sends when you approach the cap, is "a combination of number of sites, storage, and site visits". Deleting a Site reduces the first two directly. Nothing in the docs says how quickly the account's meter reflects that, or what happens to the visits component, which is a history rather than a quantity you can delete. One report from 4 September suggests the meter does not move the way people expect: "I deleted a bunch of sites after getting email warnings of Sites usage almost full, thinking it would free up space but now I'm totally blocked? I used to have almost 20 sites but now only 8." Another, from mid-August, got the 50% email, "chatted with them a few times about the issue, but it didn't get resolved so I gave up." So the honest advice is: delete what you genuinely do not need, then open the Sites experience and read the limits it shows for your plan. If it still reports you at the cap, do not keep deleting. OpenAI staff in the 11 September announcement replies pointed people to the in-product /feedback command so the team can debug an account; that is the route for a stuck meter. ## Why usage does not reset weekly Two different allowances get called "usage", and the replies to every Sites announcement mix them up. - Build usage resets. Building and editing a Site runs through Codex, so it spends your plan's agentic allowance, the five-hour and weekly limits you can see under Usage and limits in the app. "I ran out of usage 24 hours after the last reset" is this meter. Waiting fixes it. - Hosting usage does not. The Sites cap is a running total across all Sites on the account: how many, how much they store, how much traffic they serve. It has no reset day. It goes down only when you remove things, and the docs say it "may change during the public beta". "You've now used 50% of your allocated ChatGPT Sites usage" is this meter. Waiting does nothing. People are asking for the two to be shown side by side ("could we add a way to see the GPT sites usage limit as well within that same usage limits section in the iOS app?"). Until they are, the tell is the wording: agentic limits talk about resets, Sites limits talk about allocation. ## What you cannot delete - Individual versions. Every save adds a version; the docs describe listing and inspecting them but not removing them. Users report versions "take up all the space for nothing". Deleting the Site is the only version-level cleanup. - Anything from the CLI or an agent. Sites can be created from a Codex session but the docs are clear that management lives in ChatGPT web or the desktop app. "You can make claude artifacts and chatgpt sites from cli but cannot delete them using the same," as one developer put it. Another wanted Sites off entirely and found "agents can create the sites but not delete them, that can only be done in the UI". - A Site whose settings are stuck. One user with a broken custom domain reported being unable to delete or change it for days. If Delete site fails, that is a support case, not a retry. ## Three levers that reduce usage - Delete the Sites you do not need. The steps above. Permanent, so start with the throwaways: the experiments Codex published on its own, the duplicates from a workspace hiccup, the demo you already showed. - Take busy Sites private. If a public Site is drawing traffic you do not need, switching "Who has access" to "Only you" or an invited list stops the visits that count toward the cap, without deleting anything. The help center describes this as the way to restrict access; a high-usage public Site is also the one thing a limit can take offline on its own. - Stop new usage arriving. Most surprise Sites are Codex publishing local work; [one line in AGENTS.md stops that](/blog/stop-codex-publishing-to-chatgpt-sites). And a finished static page (a report, a proposal, a one-pager) does not need a database, a server, and a stack of versions. Hosting it on Sites spends the same account-level quota as an app. Hosting it on [Stacktree](/private-html-hosting) spends none, and the caps there are page counts and storage you can read on the pricing page. [The usage limits post](/blog/chatgpt-sites-usage-limits) has the full breakdown. ## Before you delete a page someone has the link to Deletion is instant and the URL dies with it. If a client, a colleague or a reader has that link, republish first and delete second. For a static page that is one step: publish the same HTML to Stacktree and send the new private link. The client opens it with no ChatGPT account, you can add a passcode or an expiry, and revisions replace the page at the same address rather than stacking versions. Deletion works differently there, and it is worth saying because it is the opposite of the ChatGPT model. Taking a Stacktree page down kills the link immediately for everyone holding it, but the content is kept for 30 days and a single call restores it at the same URL, with the same id, slug and read history. You can delete without losing the option to change your mind. On ChatGPT Sites, the slug you type into that dialog is the last time you will see the Site. 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 A host where delete is not the end Publish the page to a private link that costs none of your Sites quota. Take it down whenever you like; it stays restorable at the same URL for 30 days. Three pages free, no card. [ Publish a page free → ](https://app.stacktr.ee/?from=blog_cta_delete_chatgpt_site_free_usage&join=1) Free to try: 3 pages, each live for 7 days. Own domain from $19/mo. FAQ ## Frequent questions How do I delete a ChatGPT Site? + Open Sites from the sidebar in ChatGPT on the web or the desktop app, select the Site, choose Delete site, type the Site slug in the dialog, and select Permanently delete. OpenAI's help center warns that "deleting a site permanently removes it, and you cannot restore deleted sites", so copy out anything you want to keep first. Does deleting a ChatGPT Site free up usage? + It removes that Site and its storage from your account, and the help center says limits lift "until usage is reduced". It does not say deletion clears a block right away, and at least one user reported the opposite: after deleting roughly twelve Sites on a usage warning, they were "totally blocked". Check the limits shown in the Sites experience after deleting; if you are still blocked, report it through ChatGPT. Can I undo deleting a ChatGPT Site? + No. The help center is unambiguous: "you cannot restore deleted sites". The confirmation dialog asks you to type the Site slug for that reason. If anyone holds the link, it goes dead at that moment, and there is no documented export to fall back on, so save the source from the conversation before you confirm. Does ChatGPT Sites usage reset every week? + The build side does, the hosting side does not. Building a Site runs through Codex and spends your plan's weekly or five-hour agentic allowance, which resets on a schedule. Hosting counts against a separate beta cap that combines number of Sites, storage and visits, applies across the account, and only goes down when you delete things. "Ran out 24 hours after the last reset" is the first meter; "you've used 50% of your allocated Sites usage" is the second. Can I delete a ChatGPT Site from Codex CLI or from an agent? + Not as documented. The docs say Sites has no standalone CLI management view and that you manage Sites in ChatGPT web or the desktop app. Users have noticed the asymmetry: "you can make claude artifacts and chatgpt sites from cli but cannot delete them using the same." An agent can create a Site by accident and cannot clean it up. Can I delete old versions of a ChatGPT Site to free storage? + No documented way. The docs describe saving and inspecting versions but not removing them, and a reply to OpenAI's 11 September announcement asked for exactly this: "there is no way to do this currently, and after many changes the versions take up all the space for nothing." Until that lands, the only version-level cleanup is deleting the whole Site. How do I reduce ChatGPT Sites usage without deleting anything? + Two levers. Restrict a busy Site's access to "Only you" or an invited list, which stops public visits counting against the cap. And stop new Sites appearing: add a rule to AGENTS.md so Codex does not publish local experiments, and put finished static pages (reports, one-pagers) on a host that does not spend Sites quota, such as Stacktree. Keep reading ## Related guides - [ ChatGPT Sites usage limits What counts toward the cap, what happens at the limit, what people report. ](/blog/chatgpt-sites-usage-limits) - [ Stop Codex publishing to ChatGPT Sites The AGENTS.md line that prevents the Sites you will otherwise be deleting. ](/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 Taking a Site private, and who can still open it. ](/blog/chatgpt-sites-private-sharing) - [ Stacktree pricing Page counts and storage per plan, no meter to guess at. ](/pricing) References ## Sources and further reading - [ OpenAI Help Center: Creating and managing ChatGPT Sites ↗ The "Take down a Site" steps, "you cannot restore deleted sites", and the Public Beta Limits section. ](https://help.openai.com/en/articles/20001339-creating-and-managing-chatgpt-sites) - [ ChatGPT Sites documentation ↗ Saved versions, and the note that Sites has no standalone CLI management view. ](https://learn.chatgpt.com/docs/sites) - [ Deleted Sites, still blocked (user report, 4 September 2026) ↗ "I deleted a bunch of sites after getting email warnings of Sites usage almost full, thinking it would free up space but now I'm totally blocked?" ](https://x.com/k_kohlbrenner/status/2095977931264639130) - [ Create from CLI, cannot delete from CLI (user report, 27 August 2026) ↗ The management asymmetry: Sites can be created from a Codex session but only deleted in the ChatGPT UI. ](https://x.com/akshen121/status/2093003549689192775) - [ ChatGPT Sites update: 5M sites (@ChatGPT) ↗ The 11 September 2026 announcement whose replies include the version-pruning request and the /feedback pointer from OpenAI staff. ](https://x.com/ChatGPT/status/2098457920291946894) ## Spend the quota on apps, not pages Static pages on a private link with caps you can read. Delete freely: restorable at the same URL for 30 days. [ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_blog_delete_chatgpt_site_free_usage) 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