What Is ChatGPT Sites? A Plain English Guide

OpenAI's website builder, explained: what it makes, who can actually use it, where it is unavailable, and whether it replaces a proper site builder.

The short answer

ChatGPT Sites is a website builder that lives inside ChatGPT. You describe the site you want in ordinary English, it builds the pages out of HTML, CSS and JavaScript, and it hosts the result on OpenAI's own infrastructure, so there is no hosting company to go and find afterwards. You can preview it, publish it and share the address.

Two things decide whether any of that is relevant to you, and neither has anything to do with your ability. It needs a paid ChatGPT plan, and it is not available in the United Kingdom, the European Economic Area or Switzerland.

Sites launched on 9 July 2026 as a public beta, which in software years is roughly yesterday. What it can do, who can get at it and which plans include it will all move. Check OpenAI's own help pages before you pay for anything or promise anyone a website.

Who cannot use it, said plainly

Let us get the disappointing part out of the way first, because everything else in this article is academic if it applies to you.

ChatGPT Sites is unavailable in the UK, the EEA and Switzerland. Not slower, not limited, not coming next week as far as anyone has said. Unavailable. If you are reading this from Manchester, Dublin, Lisbon or Zurich, no plan you buy will change that.

It also requires a paid plan. The Free plan does not include it, and neither does the Go plan. So there are two gates, and people tend to discover the second one about ten minutes after clearing the first.

If either gate rules you out, the honest advice is to stop reading about Sites and go and use something else. Our free course on building with Lovable covers a standalone builder with no regional restriction and a free tier you can start on this afternoon. Same idea, describe a site and watch it appear, without the geography lesson.

What does it actually build?

The mental model that helps most: you already know the ChatGPT message box. Sites is what happens when that box is pointed at a whole website rather than a paragraph.

You ask for a site, in the same tone you would use asking a colleague for one, and it produces something you can look at. If you would rather be explicit about which capability you want rather than leaving it to interpretation, you can name Sites directly in your request. Then you iterate the way you already iterate on a paragraph: too busy, make the introduction shorter, move the contact details to the bottom, that green is a crime.

What comes out is a static website or a lightweight web app. OpenAI's own suggested uses are a good tell about where this thing is aimed: dashboards, project trackers, launch calendars, prototypes, internal portals, reports. Notice the family resemblance. Every one of those is something a person looks at, not something a person logs into.

What does static mean, and what does it rule out?

This single word decides most of what you can build, so it is worth thirty seconds of your attention.

Static means the pages are the same for every visitor and the site has no memory. It does not know who you are. It does not recognise you when you come back tomorrow. It does not keep hold of anything anyone types into it.

What a static site cannot do for you

NO ACCOUNTS      nobody signs up, nobody logs in, nobody has a profile
NO PAYMENTS      no checkout, no subscriptions, no taking money
NO MEMORY        nothing typed in is stored anywhere for later
NO PERSONALISING different visitors see exactly the same pages

That reads like a wall of limitations, and it is. But the useful reframe is that most of the sites people actually need are static and always were. A portfolio is static. A menu is static. A one page explanation of what your business does and how to reach you is static. A launch calendar the team checks on a Monday is static. The moment you want people to have accounts, or to pay you on the page, or to have the site remember what they did last time, you have quietly asked for a different kind of product and you were always going to need different tooling.

In plain English

Static site:: A site whose pages are identical for every visitor and change only when you change them.
Web app:: A page that does something interactive rather than just sitting there, like a calculator or a tracker.
Hosting:: Somebody keeping your site switched on so other people can open it. Sites handles this part.
DNS:: The settings at your domain provider that decide where a web address points.
Public beta:: Released and usable, but still visibly under construction. Expect things to move.

Can you use your own web address?

Yes, with one condition worth understanding before you get excited. Custom domains are supported if you already own the domain and can edit its DNS settings.

Read that twice, because it contains a small trap. Owning a domain and being able to edit its DNS are not always the same thing. If a web designer bought it for you in 2019, or it came bundled with an old hosting package, or it sits in an account belonging to someone who has since left, you may technically own something you cannot administer. Find out where the domain actually lives before you build the site rather than after.

Is it a replacement for a proper website builder?

Sometimes, and the honest comparison is about shape rather than quality.

Convenience is the pitch. Sites is inside an app you already have open, with an account you already have. No new tool, no new tab, no new password. That is genuinely most of the value, and it is not a small thing.

Portability is the question to ask. A standalone builder typically hands you a real codebase that belongs to you and can be taken somewhere else when you outgrow the tool. Sites hosts the result for you. Before you build anything you would be upset to lose, find out exactly what you can take with you, and get that answer from OpenAI rather than from an article, this one included.

Scope is decided in advance. A standalone builder can usually grow a backend when you eventually need logins and stored data. Static closes that door by design. Narrower on purpose, not by oversight.

None of that makes either one better. It makes them different tools for different afternoons. If your idea is something people read, Sites is the shorter path. If your idea is something people log into, you are in the wrong shop.

Who does it actually suit?

It suits you if you are on a paid plan, outside the excluded regions, and the thing in your head is a page rather than a product. Internal dashboards nobody will ever pay for. A prototype you need in front of three colleagues by Thursday. A one page explanation you have been meaning to write for two years. The report that currently lives in a spreadsheet attachment and deserves a link instead.

It does not suit you if you need a shop, a members area, or anything that remembers a visitor. It also does not suit you if the site matters commercially and you have not yet worked out what happens to it if the tool changes shape, which on a product this new is a real question rather than a paranoid one.

And it suits you least of all if you are in the UK or the EEA, in which case the correct next step is a builder that will actually let you in.

If you want the practical version, with prompting for layout, publishing, domains and a clear-eyed lesson on the edges, our free ChatGPT Sites course walks through it properly. If the availability rules shut you out, build with Lovable instead. And if you are not sure which of those you even want, have a look at all our free courses or just start here.