A website used to mean picking a builder, paying for hosting, and dragging boxes around all weekend. ChatGPT Sites skips most of that: you type what you want, ChatGPT builds it, and you hit publish when it looks right. The trick is knowing which levers matter before your first site goes live.
What ChatGPT Sites actually is
Sites is a new public beta feature that lets ChatGPT create, host, refine, and share full websites, web apps, and even small games. You describe what you want in plain English. ChatGPT builds it, shows you a live preview, and keeps editing until you’re happy. Then you publish it on a real URL that anyone can visit.
There’s no template gallery and no drag-and-drop editor. The conversation is the editor. You ask for a landing page with pricing and a contact form, it appears. Then you say the hero section feels cramped, and it gets fixed. It’s closer to briefing a developer than using Canva.
Every site gets hosted by OpenAI on a chatgpt.site address. You can rename that address whenever you like, and the old one redirects automatically. Got your own domain? You can connect that too.
Who can use it (and where)
Here’s where a lot of people will hit a wall, so let’s get this out of the way.
Sites is available on ChatGPT Plus, Pro, Business, Enterprise, and Edu plans. Free accounts and the cheaper Go plan don’t get it, at least during the beta. The feature is also not available in the EEA, Switzerland, or the UK at launch, which OpenAI says is about regional rollout rather than a permanent ban. If you’re on Plus and don’t see it yet, it’s still spreading to accounts over the coming days.
Usage limits apply across all your Sites during the beta, and they vary by plan. Hit the ceiling and you won’t be able to create new Sites or add storage. Editing existing ones keeps working.
One more wrinkle for companies: in Enterprise workspaces, public publishing is switched off by default. An admin has to enable it before anyone can put a Site on the open internet.
Build your first site in ChatGPT, step by step
Enough theory. Here’s the actual flow.
1. Open ChatGPT on the web (the Work tab) or in the desktop app (Work or Codex).
2. Describe the site you want. Include the word “website” in your prompt, or just type @Sites to trigger the builder directly. The more specific you are about pages, content, and style, the better the first draft.
3. Attach anything useful: files, links, visual references, or an existing Codex project if you have one.
4. Watch the preview. It opens in an in-app browser while the site is being built, so you can click around before anything is public.
5. Refine by asking. Change the layout, swap content, add features. Repeat until it feels done.
6. Publish and pick your audience.
Step 6 matters more than people expect, so let’s slow down there.
Preview before you publish
A brand-new Site is private by default. Only you and your workspace admins can see it. That’s a relief if you’ve ever worried about a half-finished page leaking onto Google.
Pick who gets to see it
When you publish, you choose: keep it to yourself, invite specific people by account, share with your whole workspace, or make it fully public. Public Sites can optionally offer “Sign in with ChatGPT”, which lets visitors log in and get a personalized experience.
And here’s the part that’s genuinely new: in eligible workspaces, visitors can approve read-only access to their own connected tools. Picture an issue dashboard where every teammate sees their own assigned tickets the moment they log in. You didn’t write any backend code for that. The Site just reads what each visitor already has permission to see. As a result, small teams can ship internal tools that used to need a developer.
The version gotcha that bites new users
This one’s important, and the help docs bury it.
Sites has two separate actions: saving a version and deploying a version. Every deployment URL is a production URL. In other words, the moment you deploy, real visitors see the change. There’s no staging site hiding behind the scenes.
So if you want to review something before it goes live, ask ChatGPT to save a version instead. That gives you a deployable candidate you can inspect. Deploy only when you actually want people to see it. It takes two minutes to learn and saves you from updating a live client page by accident.
Editing after publish day
Published ChatGPT Sites aren’t frozen, either. Come back anytime, ask for changes, and push updates to the same address. You can invite teammates from your workspace to edit alongside you, and after the owner publishes the first version, editors can ship later ones to the same URL. There’s even basic analytics included, so you can see whether anyone actually visited the thing you built on a Tuesday night.
What you can build with it
OpenAI’s own showcase gives you the range: portfolio-style sites, interactive experiences, listening rooms, field guides, small games. But the practical list for most readers looks more like this:
- A freelancer portfolio with project galleries and a contact form
- A client portal that shows status, files, and next steps
- Simple internal tools: budget trackers, launch calendars, reports
- Event pages and quick landing pages for tests
- Lightweight dashboards fed by your team’s connected apps
To make the difference concrete, look at how the old workflow compares:
| Need | Typical old way | With ChatGPT Sites |
|---|---|---|
| Portfolio site | Builder subscription plus hosting setup | One prompt, included with your plan |
| Client portal | Custom development or duct-taped tools | Prompt with Sign in with ChatGPT |
| Team dashboard | A BI tool seat per person | Prompt plus connected tools |
| Event page | Template hunting for an afternoon | Prompt, preview, publish |
Is it good enough to replace your current setup?
Honest answer: for quick business sites, prototypes, and internal tools, yes. This is now the fastest path from idea to live URL that I’ve seen, and the private-by-default preview removes most of the fear. We’re tracking similar moves across the industry, like the shared workspace in Claude Docs and Slides, because every major assistant wants to host your output, not just chat about it.
For a serious content site with search ambitions, though, I wouldn’t switch yet. You give up fine-grained control over technical SEO, and anyone running a blog for traffic (the way this site does) still wants a real CMS underneath. If your goal is a resume-style personal page, comparing it with dedicated options in our AI resume builders roundup is worthwhile too, since those add templates Sites doesn’t have.
The smart move this week: pick one small, real project. Build it, publish it privately, send the link to one person for feedback, then decide. And if you’re curious how other assistant platforms handle this same job, our walkthrough of x.ai’s Grok agent platform is a useful contrast. The full feature details live on OpenAI’s ChatGPT Sites page and the official help center guide if you want the source material.
