ChatGPT can now build and host your website. Should your startup use it?
By Bilal Haider, Founder, Theepa Studio · · 5 min read
Short answer
ChatGPT Sites lets Plus, Pro, Business and Enterprise users build, host and publish a website or small app from a conversation, and on 15 October 2026 OpenAI removed the fixed limit on how many Sites Plus and Pro users can create. OpenAI positions it for focused websites and lightweight apps. Our advice: use it for internal tools, prototypes and one-off pages, and keep your main marketing site on a stack you control.
What is ChatGPT Sites?
ChatGPT Sites is OpenAI's tool for building websites inside ChatGPT. You describe what you want, review a preview, ask for changes in plain language and publish. OpenAI's help centre says it lets you "create, preview, publish, and share interactive websites and lightweight apps", with hosting, access controls, a database and file storage included.
The timeline so far:
- 2 June 2026: OpenAI Academy published a guide to building Sites from Codex, aimed at internal tools such as launch trackers, weekly dashboards and onboarding pages.
- 9 July 2026: Sites entered public beta. Business and Enterprise customers could publish publicly by URL, and the beta expanded to Pro, Pro Lite and Edu, with Plus following. It is not available on Free or Go plans.
- 15 October 2026: OpenAI removed the fixed limit on the number of Sites Plus and Pro users can create. Usage and storage limits still apply.
One detail matters for founders outside the US. At the July launch, OpenAI said public publishing was "not available in the EEA, Switzerland, or the United Kingdom". We have not found a later release note that changes this, so UK and European teams should check before planning around it.
What can it actually do?
According to OpenAI's help article, a Site can:
- Publish to a ChatGPT-hosted URL, or use a domain you already own once you add DNS records. Sites does not register domains for you.
- Store data in a database of up to 10 GB per Site, plus uploaded files.
- Be shared with named people, your workspace, or the public where that is allowed.
- Be edited by chatting, with a preview before each deploy. OpenAI notes that "Every deployment URL is a production URL".
- Take payments, but only through a third-party payment processor that you set up and maintain.
Tom's Guide tested it in August and had a live site "in under five minutes" from one prompt. The reviewer also found the first design did not match what she had in mind, and it took several rounds of changes to get closer.
What does it leave out?
OpenAI is clear about the scope. Its Academy guide says Sites "is intended for focused websites and lightweight apps" and that some projects need a different tool or a bigger engineering effort. The help article adds that some frameworks, databases, background services and hosting patterns "may not be supported", and that Sites must not process sensitive data such as health records or card details.
Just as important is what the help article does not cover: search indexing and crawl controls, analytics, and exporting your code. For an internal dashboard, none of that matters. For the website that has to win customers from Google and from AI answers, it is most of the job.
ChatGPT Sites or a site you control: which fits?
| Use | ChatGPT Sites | A site you own and control |
|---|---|---|
| Internal dashboard or tracker | Strong fit, this is what it was built for | Usually more than you need |
| Prototype to test an idea | Fast way to get something clickable | Better once the idea is proven |
| Event page or one-off campaign | Works if the brand details are right | Better if it must rank in search |
| Main marketing website | No documented SEO, analytics or code export | Full control of structure, speed and search |
| Anything holding customer data | Check OpenAI's data rules first | Built around your own compliance needs |
How should a startup use it?
Our advice, in order:
- 1Start with internal tools. A launch tracker, an investor update hub or an onboarding page is the sweet spot, and the risk is low.
- 2Prototype, then rebuild what works. A clickable version helps you test messaging with real people. Once it works, rebuild it properly rather than stretching the prototype.
- 3Give it your brand, not a vibe. Upload your colours, fonts and real copy. Without them you get a generic look, which is the opposite of what a brand is for.
- 4Keep your main domain on a stack you control. Your homepage, service pages and blog need clean structure, fast pages, analytics and structured data that search engines and AI assistants can read.
- 5Check your plan and region before you promise anything. Public publishing, sharing and admin controls depend on your plan, your workspace settings and your country.
- 6Read it before you deploy. Every deploy goes live, so someone should check the copy, links and forms first.
Does this change what a website is for?
Not really. Tools like Sites make a working page cheap and quick to produce, which is good news for small teams. What they don't do is decide what your site should say, who it is for, or how people find it. That is still strategy, design and search work.
If an AI-built prototype is ready to become a real product, our AI MVP cleanup service turns prototypes into products ready for real users. If you want to see how visible your current site is to AI assistants, run it through the AEO score tool.
Sources
- Creating and using ChatGPT Sites (OpenAI Help Center, accessed 20 October 2026)
- ChatGPT release notes: Sites public beta, 9 July 2026, and Sites limits, 15 October 2026 (OpenAI Help Center, 16 October 2026)
- ChatGPT sites (OpenAI Academy, 2 June 2026)
- I built a website without leaving ChatGPT, and it only took one prompt (Tom's Guide, 5 August 2026)
Bilal Haider
Founder, Theepa Studio
Bilal founded Theepa Studio in 2016. The studio has delivered more than 10,000 brand identities for companies in the US, UK and the GCC.
