ChatGPT Sites.

On 9 July 2026, OpenAI launched ChatGPT Work — an agent inside ChatGPT that turns a goal into finished materials like sheets, slides, docs, and web apps. Tucked into that launch was Sites, now in public beta: you describe a website or lightweight app in plain English, ChatGPT builds it, hosts it, and hands you a URL you can share with your team or the whole internet.

The hosting is the point. Tools that generate a web page from a prompt have existed for a while — but they usually leave you holding a folder of code and a deployment problem. With Sites, creating, previewing, publishing, and updating all happen in the same conversation. Hosting, access controls, storage, and database support are included; there is no separate deploy step to learn.

A Site is useful when a piece of work needs a place to live: a launch tracker your team opens every Monday, a dashboard for a weekly review, a calculator for comparing options, an onboarding page for a new project. Things too alive to be a document, too small to be a software project.

Sites is part of the redesigned ChatGPT desktop app for Mac and Windows — the one that merged with the Codex app in July 2026. The sidebar now has four modes: Chat for conversation, Work for agentic tasks, Codex for coding, and Sites — the home for every site you've created, where you manage, edit, and share them.

You create a Site from Work (or Codex) by simply asking for a website in your prompt. The desktop app goes further than the web version: ChatGPT can pull in your local files and folders as source material, test the site in the app's built-in browser, and start a site from a compatible local project you already have on disk.

Sites also works in ChatGPT on the web — select More > Sites or go to chatgpt.com/sites — and a Site outlives the chat that created it. It stays in your Sites list, ready to reopen and refine, long after the conversation ends.

The best first Site solves one clear problem for a defined group of people. OpenAI's own examples cluster around exactly that shape:

• A launch tracker — milestones, owners, links, and risks for a project, replacing the ritual of digging through five documents before every standup.
• A dashboard — the numbers your team reviews each week, in one consistent format, at one URL.
• A calculator — inputs, assumptions, and a clear result, for pricing scenarios or comparing options.
• An onboarding page — background, key documents, team directory, and a first-week checklist for anyone joining a project.
• Prototypes and interactive reports — a clickable idea you can put in front of people, or analysis someone can explore instead of scroll past.

Sites can also build games and public pages — but the sweet spot is the internal tool: smaller than a product, more alive than a document, made for one team, one project, or one recurring workflow.

• The ChatGPT desktop app — free to download for Mac and Windows from chatgpt.com/download. Sites also works in Work on ChatGPT web.
• A paid ChatGPT plan— Sites is in public beta for Plus, Pro, Business, Enterprise, and Edu. It's not available on the Free or Go tiers, and at launch it's not available in the EEA, Switzerland, or the UK.
• Admin approval, if you're in an Enterprise workspace — admins control whether Sites is enabled at all, and public publishing is off by default until an admin switches it on.
• A real problem — a site your team would actually open twice beats a demo every time.

Open Work in the desktop app and describe what you want. Including the word "website" in your prompt — or mentioning @Sites directly — triggers the Sites workflow. Here's a starter in the shape OpenAI recommends:

Why this prompt works — habits worth stealing:

• It names the audience."Ten people, in a weekly review meeting" shapes everything — layout, density, what goes above the fold.
• It asks for persistence explicitly. "Keep everything saved between visits" tells ChatGPT this needs a database behind it, not just a static page. Say this whenever people will enter data.
• It attaches the real material. Add the files, data, links, and constraints ChatGPT should build from — on desktop, that includes files straight off your machine.
• It invites questions first."Propose a structure and ask me anything" catches misunderstandings before the build, not after.

ChatGPT builds the site and shows you a private preview — only you can see it at this point. Open it and test it the way a teammate would on first visit: click through the main flow, try the forms, check the labels and any calculations.

To change something, select Edit in the preview and describe what you want — copy, layout, data, styles, links, forms, interactive behaviour. Attach a screenshot or extra files when they'd help ChatGPT see what you mean. One change per message, review, repeat: the same iterate-by-taste loop that makes every AI building tool click.

One thing to internalise before you ship anything: every deployment URL is a production URL. Sites separates saving a version (a reviewable build candidate) from deploying it (live to your chosen audience). For anything with an audience, ask ChatGPT to save a version first, review it, and only then deploy.

A new Site starts private — visible only to you and your workspace admins. When it's ready, select Share and choose who has access. Depending on your plan and workspace settings, the ladder runs:

• Owner and workspace admins— the default, and the right setting while you're still reviewing.
• Selected people or groups — invited visitors sign in with the account that received access.
• Anyone in the workspace — the classic internal-tool setting.
• Anyone on the internet — a fully public URL, no ChatGPT account needed to visit.

Select Publish, then use Visit to open the live site or Copy link to share it. Sharing lets people visit the Site — it never lets them edit it. And you can walk it back any time: restrict access from the share settings, or delete the Site entirely from the Sites view.

Once the basic loop feels natural, Sites has more headroom than the first prompt suggests:

• Durable data and uploads. Ask for saved records, scores, or file uploads and Sites provisions real storage behind the scenes — a relational database (D1) for structured data, object storage (R2) for files.
• Sign in with ChatGPT. A public Site can offer optional sign-in for personalised views, saved progress, or per-person records — ask ChatGPT to add it.
• Built-in analytics. Every Site records unique visitors and page views automatically — open More actions > Analytics from the Sites list, no tracking snippet required.
• Custom domains. Where available, connect a domain you already own from the Site's settings — Sites gives you the DNS records to add at your provider.
• Keep it fresh on a schedule. Pair a Site with a Scheduled Task — OpenAI's own example prompt: "Create an automation that monitors for new account activity and updates this site every day at 8am."

Know the edges, too: Sites runs on its own hosted runtime, so some frameworks and hosting patterns aren't supported, and it must not process sensitive data like health or payment-card information. A full product with real infrastructure needs is still an engineering project — Sites is for everything smaller that never got built because deploying was too much ceremony.