What the source published

OpenAI's Sites feature in ChatGPT covers the whole path from idea to published site inside the conversation. You start by asking ChatGPT to build a website, or by mentioning @Sites, then describe what you want to make and what you want to do with it. You can add files or visual references, or start from an existing Codex project.

The use cases named are work, business and personal projects — team dashboards, client portals and portfolios are the examples shown. When it is ready you publish and share it, and you can return anytime to make changes. When you create a site for the first time, only you and your workspace admins have access to it; wider sharing is your decision afterwards.

A Site can be more than a static page. You control who can access it and can invite teammates to edit and publish updates. You can add Sign in with ChatGPT so visitors save their work and pick up where they left off, and built-in storage can save information and uploaded files, including documents and images. In eligible workspaces, people using your Site can approve read-only access to their own connected tools, and the Site only sees information they already have permission to access.

Sources: [1] [2]

Try it: six steps from idea to live link

  1. Describe the job in one breath: who the site is for and what it must do — for example, a portal where clients check project progress — then let ChatGPT build the first version, or invoke @Sites directly.
  2. Bring your references: attach the documents, data or page screenshots you like, or start from an existing Codex project, so the first draft lands close to the target.
  3. Refine in conversation, one thing at a time: layout, wording, sections and behaviour in separate requests, checking each round before asking for the next change.
  4. Set access before you publish: selected people, your whole workspace, or fully public — and invite any teammates who should be able to edit and publish updates.
  5. Decide on sign-in and storage: if visitors return to forms or work in progress, enable Sign in with ChatGPT and built-in storage so they can resume where they stopped.
  6. Finish with the address: rename the ChatGPT-hosted URL — the old one redirects automatically — or connect a custom domain you own, then share the link.

Sources: [1]

The full picture: permissions and data boundaries first

Access is layered: share with selected people, with your workspace, or make the Site public. Sites shared within a workspace use ChatGPT sign-in to control access, and public Sites can optionally offer Sign in with ChatGPT for personalized experiences. Invited teammates can edit alongside you and publish updates, which suits small teams maintaining a lightweight site together.

Two data points deserve a decision before you launch. First, storage: information visitors enter and files they upload, including documents and images, are saved by the Site, so any form that collects data needs a clear answer for what you collect and how long you keep it. Second, tool connections: only in eligible workspaces can visitors approve read-only access to their own connected tools, and the Site sees only what those visitors already have permission to access — the boundary never exceeds the visitor's own.

Sources: [1]

How to read this

Sites is aimed squarely at a specific gap: not professional web platforms or commerce systems, but the page you would otherwise hack together in a document, a spreadsheet or a quick outsourced job. Dashboards, portals, event pages and portfolios are low-complexity and change often, and that is exactly where maintaining them by conversation wins — one sentence and the site is updated, with no separate deployment step.

The limits are equally clear: permissions, storage and tool access all live inside ChatGPT's system, so deep customization, complex transactions and strict compliance needs belong elsewhere. The practical rule: if the site will be revised again in three days, build it in Sites now; if it must carry payments and customer data, plan a real web stack instead.

Sources: [1]

Key takeaways

  • Sites puts building, editing and publishing inside the ChatGPT conversation: describe the idea or mention @Sites, or continue from an existing Codex project.
  • It fits lightweight sites that change often — dashboards, client portals, portfolios — where editing by chat beats a deployment pipeline.
  • Access comes in three levels (selected people, workspace, public) and defaults to just you and workspace admins until you choose otherwise.
  • Visitors can sign in with ChatGPT to save progress, and built-in storage keeps their entries and uploads — decide your data boundaries before collecting anything.
  • You can rename the hosted address or connect a custom domain; renamed URLs redirect automatically, so shared links keep working.

Sources: [1]