Most guides to this feature are still describing the version from mid-2026, where ChatGPT wrote the code and you had to drag the file into Netlify yourself. That’s not how it works anymore for accounts with Sites enabled.

This guide covers the current build-and-publish flow, what it actually costs across every ChatGPT plan, five prompts you can copy today, and the operational limits nobody puts in the headline — no CMS, no native e-commerce, and forms that need a third-party endpoint before they’ll actually send you anything.

How I Evaluated This

I didn’t run a paid Sites session for this specific piece, so I’m not going to pretend I clicked Publish on a live URL for you. What I did instead: read OpenAI’s own Help Center article on creating and managing Sites line by line, cross-referenced it against the Codex Sites developer guide for the technical limits (supported protocols, secrets handling, deletion rules), and checked current plan pricing across several independently-verified trackers rather than trusting a single source. Where those sources disagreed — and on ChatGPT pricing in 2026, they disagree a lot — I’m flagging it rather than picking whichever number sounded cleanest.

I also went back and forth with a recent piece we ran after actually put ChatGPT 5.6 through its paces on a web design task, which is worth reading alongside this one if you want a sense of output quality rather than just the publishing mechanics.

What “Work Mode” Actually Means Now

Work Mode is OpenAI’s umbrella term for ChatGPT’s agentic tool set inside the web app and desktop client — the mode where it can run code, browse, create files, and hold a preview open instead of just answering in text. Building a website is one thing that toolset does, and it’s triggered specifically by Sites, a distinct feature you reach from Work on the web, or from Work or Codex in the desktop app.

You don’t have to remember a special toggle. Just include the word “website” in your prompt, or tag @Sites directly, and ChatGPT routes the request into the Sites builder on its own.

ChatGPT Sites vs. the Old Copy-and-Deploy Method

If you’ve read older guides to this topic, they walk you through generating the code in a canvas, then manually dragging the exported HTML file into Netlify Drop or pushing it to GitHub Pages. That workflow still works and it’s still free, but for accounts with Sites enabled, it’s now the slower path rather than the only one.

The practical takeaway: if you’re in a supported region and on a paid plan, publishing through Sites is faster and gives you real access controls. If you’re in the EEA, UK, or Switzerland, or you’re on Free or Go, exporting the code to a free static host is still your route in — and it’s not a bad one.

What ChatGPT Work Mode Costs in 2026

Pricing pages for ChatGPT have moved around more than once this year, so treat the table below as accurate at the time of writing and double-check the live pricing page before you commit a client to a plan.

A couple of things worth knowing before you pick a plan just for this feature. Sites is still in public beta, which means OpenAI applies usage limits that scale by plan — hit yours and you can keep editing existing Sites, but you can’t spin up a new one or add storage until usage drops. And no, OpenAI doesn’t publish a parameter count for any GPT-5-class model, and these are closed, proprietary systems governed by OpenAI’s own Terms of Use and Usage Policies — not open-weight models with a public license file, so if a “license terms” comparison chart claims otherwise, it’s guessing. If your budget question is really “is the $200 tier worth it,” we already broke down whether ChatGPT Pro is worth $200 a month for small business use specifically.

Step-by-Step: Building and Publishing a Site

Step 1: Open Work and start a fresh conversation

On web, select Work. In the desktop app, choose ChatGPT and then Work, or use Codex if you’re building from a local project. Start a new chat rather than reusing an old one — a clean context window keeps the first draft from inheriting instructions meant for something else.

Step 2: Write a spec-first prompt, not a vibe

Include the word “website” or tag @Sites, then hand it everything it needs in one message: who the site is for, the exact sections you want, your real copy (not filler), your color palette, and anything it should never do. The framework I use for this is below — it produces fewer surprise rewrites than a one-line request.

Step 3: Review the private preview like a visitor, not a developer

ChatGPT generates a preview only you (and workspace admins) can see. Check it the way a stranger landing on the page would: is the call to action obvious in the first five seconds, does anything wrap oddly on a phone-width window, does the copy sound like a person wrote it?

Step 4: Iterate with one change at a time

Stacking five requests into one follow-up (“make the header sticky, change the font, add a testimonials carousel, fix the mobile nav, and make the CTA orange”) reliably produces partial fixes. Ask for one thing, confirm it landed, then ask for the next.

Step 5: Save a version before you deploy it live

Every deployment URL in Sites is a production URL — there’s no staging environment by default. If you want to review a build without pushing it to whoever already has the link, ask ChatGPT to save a version first instead of deploying immediately.

Step 6: Set sharing before you publish

A new Site is limited to you and your workspace admins by default. Before you hit Publish, choose who should see it: owner and admins only, named people, anyone in the workspace, or anyone on the internet. Public publishing has to be turned on by an admin in Enterprise workspaces, so if you’re building for a company account and the option is missing, that’s why.

Step 7: Point a custom domain at it (optional)

Open the Site’s settings, select Add domain, enter the apex domain or subdomain you already own, then copy the DNS records into your registrar. Sites doesn’t register a domain for you — you need to already own it — and this option isn’t available in Enterprise workspaces at launch. If you exported to Netlify or Vercel instead, custom domains work the same way they always have on those platforms.

The Spec-First Prompt Framework

Forget the sandwich metaphors. Four things, in this order, and ChatGPT stops guessing:

• Who it’s for: the business, the audience, the tone it needs to hit.
• What it needs to contain: every section, in the order you want them to appear.
• Your real content: actual headlines, actual service names, actual contact details — never “insert tagline here.”
• What’s off-limits: colors to avoid, effects you don’t want, anything that reads as a template default.

Three full examples you can copy and adapt:

Prompt 1: Freelance photographer portfolio

Build me a website with @Sites for a freelance wedding photographer named Dara Kensington. Audience: engaged couples in their late 20s to mid-30s planning a destination or outdoor wedding. Tone: warm, editorial, not corporate. Sections in this order: a full-bleed hero with the name and the tagline “Real light. Real moments.” — a horizontal gallery strip of six image placeholders labeled by shoot type (Ceremony, Reception, Details, Portraits, Golden Hour, Candid) — an about section with this bio: [paste real bio] — a simple three-package pricing list (Elopement, Half Day, Full Day) with placeholder prices — a contact form with name, wedding date, and message fields. Palette: cream background, deep terracotta accent, no blue anywhere. Font: an elegant serif for headings, clean sans for body. Do not use stock photo placeholders that say “Your Image Here” — use soft color blocks instead. No pop-ups, no auto-playing anything.

Prompt 2: SaaS pre-launch waitlist page

Build a website with @Sites for a pre-launch waitlist page for a tool called Ledgerly, a small-business invoicing app. Audience: solo founders and freelancers tired of spreadsheet invoicing. Tone: confident, plain-spoken, zero jargon. Sections: hero with headline “Invoices that chase themselves” and an email capture field with a “Join the waitlist” button — a three-item feature grid (Auto-reminders, One-click recurring invoices, Real bank sync) with a one-sentence description each — a founder note section with this text: [paste real note] — a simple FAQ with three questions I’ll provide. Palette: near-black background, single lime-green accent, no other colors. Include a working countdown-style “spots remaining” counter using placeholder logic in JavaScript. Make the layout fully responsive with the feature grid stacking to one column on mobile and the nav collapsing to a hamburger menu. Include a proper head section with title tag, meta description, and Open Graph tags.

Prompt 3: One-day pop-up event page

Build a website with @Sites for a one-day pop-up market called The Sunday Table, happening at [venue, date, time]. Audience: locals scrolling on their phones who need the details fast, not a brand story. Sections, in this order: hero with the event name, date, and a single “Get Directions” button — a vendor grid with eight placeholder cards (name, one-line description) — an accordion FAQ covering parking, entry fee, and pet policy — a footer with the venue address and an embedded map placeholder. Palette: warm cream and forest green, nothing else. This page will only be live for two weeks, so prioritize load speed over animation. No video backgrounds, no scroll-triggered effects. Make sure the hero and the “Get Directions” button are the first things visible on a phone screen without scrolling.

Two more worth trying on your own: a personal resume/portfolio page built around a single downloadable PDF link, and a local bakery landing page built around a weekly rotating menu section you can ask ChatGPT to update every Sunday.

Pros and Cons

Where It Still Falls Short

Sites runs on a supported hosting runtime, not a general-purpose server. It supports HTTP, HTTPS, and WebSockets — raw inbound or outbound TCP connections aren’t supported, so anything that needs a custom socket protocol is off the table. There’s no data residency or inference residency option at launch, which matters if you’re building for a regulated client in a jurisdiction that requires it.

Contact forms are markup only until you wire them to something — a webhook, Formspree, or your own endpoint. There’s no built-in traffic analytics; you have to ask ChatGPT to embed a snippet before you publish, or you’ll have a live page and no idea whether anyone found it. And deletion is permanent and typed-confirmation-gated: you have to type the Site’s slug to confirm before it’s gone, and OpenAI is explicit that a deleted Site cannot be restored.

If what you actually need is a full application with a real database, user accounts, and payment logic rather than a static or lightly-interactive page, this isn’t the right layer — you’re better off pairing it with a proper backend, or looking at what an AI app builder like Base44 charges for that heavier lift, or reading how a dedicated AI site builder like Macaly handles it end to end.

Where Most Guides to This Get It Wrong

The most-cited guide for this exact search still frames ChatGPT’s publishing option as something only “eligible accounts” get access to, and treats exporting to Netlify or GitHub Pages as the default path with built-in hosting as a bonus if you’re lucky. That was accurate when it was written. It’s backwards now: for any Plus, Pro, or Business/Enterprise account with Sites enabled, native publishing is the primary flow, and exporting to a third-party host is the fallback for people on Free, Go, or in a region where Sites hasn’t launched.

The same guide also doesn’t mention the region restriction at all — Sites isn’t available in the EEA, Switzerland, or the UK at launch, which is a fairly significant gap for anyone reading from Europe and wondering why they can’t find the feature in their account.

FAQ

Does ChatGPT Work Mode actually host the website, or just generate the code?

Both, depending on your plan and region. For eligible accounts, ChatGPT generates the code and publishes it directly to a live URL on its own Sites runtime. For everyone else, it still generates a complete, working HTML file — you deploy it yourself to a free host like Netlify or GitHub Pages, which takes about two minutes.

How long does it actually take to get a site live?

A single-page site with a clear spec-first prompt can be generated and published inside ten minutes. A multi-section site with your real copy and a couple of rounds of feedback usually lands in the 15–30 minute range.

Can I use my own domain name?

Yes, if you already own the domain. Add it in the Site’s settings and update the DNS records Sites provides at your registrar. This isn’t available in Enterprise workspaces at launch, and if you exported to Netlify or Vercel instead, custom domains work through their own dashboards.

Do I need to know how to code?

No. You describe the site in plain language and ChatGPT writes the code. Being able to read basic HTML helps you spot issues faster in the preview, but it’s not required.

Will my contact form actually send me messages?

Not by default. The form markup renders correctly but doesn’t connect to anything until you point it at a webhook, a service like Formspree, or an endpoint of your own. Ask ChatGPT to wire it up once you’ve picked one.

Is a ChatGPT-built site good enough for a real business?

For a landing page, portfolio, event page, or lead-capture site, yes. For anything that needs logged-in users, a real database, or checkout, you’ll want to pair it with a proper backend rather than trying to bolt one onto a static page.

Why can’t I find Sites in my account?

Confirm you’re on a paid plan other than Go, that you’re not in the EEA, Switzerland, or the UK, and that you’re signed into the right workspace. In Enterprise accounts, an admin has to enable Sites and, separately, enable public publishing before you can share one outside your workspace.

Conclusion

ChatGPT Work Mode is a genuinely fast way to get a real URL in front of someone — a landing page, a portfolio, a one-day event page. Write a spec-first prompt instead of a vague one, review the preview like a visitor, and iterate one change at a time. It is not a CMS, not a checkout, and not a database, and it won’t pretend otherwise if you push it there. Know that ceiling going in, pick the plan and region availability that actually matches your account, and it earns its place in the toolkit. If you’re weighing this against handing the build to something with more moving parts, our notes on whether an agentic tool like Claude Cowork is safe to hand real tasks to and on what Claude Code can do that Cursor can’t are worth a read before you decide where the line sits for your own project. We’ve also watched an AI agent build a landing page for us inside Framer, and compared how Claude Projects stacks up against ChatGPT’s GPTs and Bluehost’s own AI website builder, if you want more angles before you pick a tool.