ChatGPT Sites vs Playcode: Which Should You Use in 2026?

ChatGPT Sites, in public beta inside ChatGPT Work since July 9, 2026, builds internal tools and dashboards for teams on paid ChatGPT plans - with hard limits: no commerce, no Node.js backend, and no availability in the EU. Playcode builds public business websites and full-stack apps, with commerce allowed, a real backend, and worldwide availability.

Both tools turn a plain-English prompt into a working, hosted website. That is where the overlap ends. They are built for different jobs, and picking the wrong one costs you either a rebuild or a terms-of-service problem. This comparison lays out exactly where each one wins, based on OpenAI's own documentation and Playcode's published plans, as of July 2026.

ChatGPT Sites vs Playcode: Quick Comparison Table

Here is the side-by-side snapshot across the dimensions that decide the choice.

Neither column wins every row. If your team already runs on ChatGPT Work and you need an internal dashboard by lunch, Sites is genuinely the shorter path. If you are building anything public, commercial, or European, it is disqualified before you write the first prompt. Let us unpack both.

What Is ChatGPT Sites?

ChatGPT Sites is OpenAI's website and web-app hosting feature, launched in public beta on July 9, 2026 as part of ChatGPT Work. You describe what you want in a chat (or mention @Sites in your prompt), and ChatGPT generates, previews, hosts, and publishes the result at a URL. OpenAI's own examples are telling: dashboards, project trackers, launch calendars, prototypes, internal portals, and interactive reports.

Under the hood, as of July 2026:

• Runtime: Sites runs on a Cloudflare Workers runtime with D1 (a SQLite-based relational database) for structured data and R2 object storage for files
• Access control: a new Site is visible only to its owner and workspace admins until you widen access - to selected users, the whole workspace, or the public internet where publishing is enabled
• Identity: internal Sites can require sign-in with the visitor's ChatGPT workspace account, which makes team-only tools trivially easy to secure
• Custom domains: supported where available - you bring a domain you already own and point DNS records at your Site (not available in Enterprise workspaces at launch)
• Publishing: every deployment URL is a production URL; you save a version first if you want to review before going live

Availability is the first real filter. Sites requires a paid ChatGPT plan - it is excluded from the Free and Go tiers - and it is not available in the EEA, Switzerland, or the United Kingdom at launch. In Enterprise workspaces, public publishing is off by default until an admin enables it. Usage is metered: the beta includes plan-specific limits, and heavier work consumes more of your allowance, following the same usage structure as Codex.

What Can't ChatGPT Sites Do?

The limits fall into three groups: contractual bans, technical constraints, and regional gaps. All of these are current as of July 2026 and may change as the beta evolves.

Contractual bans

• No commerce. The Sites terms prohibit enabling financial transactions, and Sites must not process payment-card data. No store, no checkout, no paid bookings.
• No health data. Sites must not process Protected Health Information.
• No sites targeting children under 13 or the applicable age of digital consent.

Technical constraints

• No Node.js servers. The Workers runtime does not run traditional server processes. If your app needs Express, NestJS, or any long-running server, it does not fit.
• No Postgres or external databases. Durable data lives in D1 (SQLite) and files in R2. OpenAI's docs note that some frameworks, private networks, databases, background services, and hosting patterns are unsupported.
• No background services. Anything that needs a worker process, a queue consumer, or a persistent WebSocket server is out of scope.
• No data residency. Sites does not support data residency or inference residency at launch - deployed Sites, code, D1/R2 data, and logs included.

Regional and account gaps

• Not available in the EEA, UK, or Switzerland at launch.
• Not available on Free or Go plans, and rollout is staged even on paid ones.
• Admin gates. In Business and Enterprise workspaces, admins control who can create and publish Sites, and OpenAI can remove Sites that risk violating its policies.

When Is ChatGPT Sites the Right Choice?

Honest answer: for a real set of jobs, Sites is not just adequate - it is the best tool available. If these describe you, use it.

• Your team already runs on ChatGPT Work. No new vendor, no new billing, no procurement conversation. The tool is already inside the workspace your company approved.
• You need internal tools, fast. Dashboards, project trackers, launch calendars, internal portals, interactive reports - the exact use cases OpenAI designed Sites around. ChatGPT can even keep them updated as the underlying data changes.
• Workspace sign-in matters more than public reach. Requiring visitors to authenticate with their workspace account is built in. Replicating that elsewhere means wiring up SSO yourself.
• The audience is your coworkers, not your customers. Admin-gated sharing, default-private access, and Compliance API visibility are features, not friction, for internal software.

A revenue-ops lead who wants a live pipeline dashboard pulling from the team's existing ChatGPT context should not sign up for an AI website builder. Sites wins that job outright.

When Is an AI Website Builder the Right Choice?

Flip every assumption above and you get the jobs where an AI website builder like Playcode wins.

• You are building a public business website. A site for a bakery, a law firm, a SaaS launch, or a portfolio exists to be found by strangers on Google. Playcode is built around that: public hosting with a global CDN, custom domains with auto SSL, and pages designed to rank.
• You need to sell something. Stores, checkout flows, and payment integration are supported on Playcode. On ChatGPT Sites they are contractually banned.
• You or your customers are in Europe. Playcode works in the EEA, the UK, and Switzerland today. ChatGPT Sites does not, as of July 2026.
• Your app needs a real backend. Playcode Cloud runs each full-stack app on its own dedicated machine with a backend, a persistent database, background jobs, WebSockets, per-project git, and one-click rollback of code and data together. A Pro plan includes three of these apps.
• You want to edit visually. Beyond the AI chat, Playcode's visual editor lets you click any element and change text, colors, and images directly - no prompt round-trip for a typo fix.
• You want predictable pricing. Playcode Pro is $25/month, or $250/year (about $21/month billed annually), with AI credits included that roll over when unused. Sites meters usage against plan-specific beta limits that OpenAI says may change during the beta.
• You want the code. Playcode lets you download your project's code anytime. There is no lock-in if you outgrow the platform.

How to Move a ChatGPT-Generated Site to Playcode

Built something in ChatGPT - with Sites, or just as generated code in a conversation - and hit one of the walls above? Moving it to Playcode is a short job.

1. Get the source out of ChatGPT. Ask ChatGPT to show or export the full source code of your site. For a Sites project built from a local folder, you already have the code on disk. For a chat-generated site, ask for every file, complete and unabridged.
2. Start a Playcode project. Open playcode.io and create a new project. Paste the code in, or take the faster path: give Playcode AI your deployed site's URL and ask it to rebuild the design and content. It reads the live page and recreates it.
3. Rebuild the data layer if you had one. D1 data does not transfer automatically. Export your records (ask ChatGPT to dump the tables as CSV or JSON), then ask Playcode AI to create the equivalent tables and import the data into your Playcode Cloud database.
4. Add what Sites could not do. This is usually why you are moving: add the checkout, the booking flow with payments, the public marketing pages, or the background job that Sites' runtime does not support.
5. Connect your domain and publish. Point your custom domain at Playcode (SSL is automatic), review, and publish. If the domain was previously attached to your ChatGPT Site, remove it there first, then add it in Playcode.

For a typical landing page or small app, the whole migration takes under an hour, and most of that is reviewing the result.

FAQ

What is the difference between ChatGPT Sites and Playcode?

ChatGPT Sites (public beta since July 9, 2026) creates internal tools, dashboards, and lightweight web apps inside ChatGPT Work, hosted on a Cloudflare Workers runtime with D1 (SQLite) and R2 storage. Playcode is an AI website builder for public business websites and full-stack apps, with a visual editor, commerce support, custom domains with auto SSL, and a real backend with a persistent database on Playcode Cloud.

Can ChatGPT Sites sell products or take payments?

No. As of July 2026, the ChatGPT Sites terms prohibit enabling financial transactions, and Sites must not process payment-card data. If you want to sell products, take bookings with deposits, or run any checkout, you need a different platform. Playcode supports commerce, including stores with payment integration.

Is ChatGPT Sites available in Europe?

Not at launch. As of July 2026, ChatGPT Sites is not available in the EEA, Switzerland, or the United Kingdom. Playcode is available worldwide, including all of Europe.

Can ChatGPT Sites run a Node.js server or a Postgres database?

No. ChatGPT Sites runs on a Cloudflare Workers runtime with D1 (a SQLite-based relational database) and R2 object storage. Node.js servers, Postgres, private networks, and background services are not supported. Playcode Cloud gives each app a dedicated machine with a backend, persistent database, background jobs, and WebSockets.

How much does ChatGPT Sites cost compared to Playcode?

ChatGPT Sites requires a paid ChatGPT plan (it is excluded from Free and Go), and usage is metered with plan-specific beta limits, similar to Codex usage. Playcode uses a flat subscription: Pro is $25/month, or $250/year (about $21/month billed annually), with AI credits included that roll over when unused. See Playcode pricing for the full breakdown.

How do I move a ChatGPT-generated site to Playcode?

Ask ChatGPT to export or show the full source code of your site, copy the code or content into a new Playcode project (or paste the deployed URL and ask Playcode AI to rebuild it), then refine it with the visual editor and AI chat, connect your custom domain, and publish. Most sites move over in under an hour.

The Verdict

This is not a case of one tool being better - it is two tools aimed at different rooms of the same building. ChatGPT Sites is internal software for teams that already live in ChatGPT Work: dashboards, trackers, and portals with workspace sign-in, shipped without leaving the chat. Playcode is the front door: the public website, the store, the full-stack app your customers actually visit.

Choose ChatGPT Sites if: your company runs on ChatGPT Work, the audience is your coworkers, and the job is a dashboard, tracker, or internal portal.

Choose Playcode if: the site is public, sells something, needs a real backend, needs visual editing, or needs to work in Europe.

If you are weighing the broader field, our AI website builder comparison covers the full landscape, and ChatGPT Sites alternatives goes deeper on the options when Sites cannot do what you need.