GenAIWiki
Search
beginner

Use ChatGPT Sites from a Prompt

Turn a ChatGPT prompt or local project into a hosted website with Sites: @Sites, save vs deploy, sharing, D1/R2, and public-beta limits.
chatgptsiteshostedopenaicodex

10 min read

FeaturedUpdated todayVerified recentlyInformation score 92

Key insights

Concrete technical or product signals.

  • Sites is a hosted ChatGPT artifact, not a git-native coding agent.
  • Save a version without deploying if you need a review candidate.
  • No data residency at launch; keep PHI and card data off Sites.

Use cases

Where this shines in production.

  • Publishing an internal dashboard from a prompt
  • Turning a compatible local project into a ChatGPT URL
  • Deciding when to stay in Codex instead

Limitations & trade-offs

What to watch for.

  • Public beta limits and plan availability change.
  • There is no standalone Sites CLI.
  • This is not a token-pricing guide.

ChatGPT Sites is OpenAI's public-beta product that creates, hosts, refines, and shares websites, web apps, and games from ChatGPT. Official docs say you start from a prompt or a compatible local project, then manage the Site at chatgpt.com/sites or in the ChatGPT desktop app.

This is not OpenAI Codex and not a public API. Use Sites when the output should be a ChatGPT-hosted URL. Use Codex when the work should stay in a repository you host yourself.

1. Confirm you can use Sites

Official docs list Plus, Pro, Business, Enterprise, and Edu. Free and Go are excluded. Plan-specific usage limits apply during the beta. Reaching a limit can block creating a Site, adding storage, or keeping a high-usage Site public.

Workspace admins can still gate the feature. In Enterprise, public publishing is off by default.

2. Start the Sites workflow

In ChatGPT, include the word "website" in the prompt or mention @Sites.

  1. Describe the audience, purpose, required behavior, and data the Site should use.
  2. Review the generated content and behavior.
  3. Ask for edits. Attach files or screenshots when they help.
  4. Open Sites to manage sharing and the production URL.

On the web, select More > Sites or go to chatgpt.com/sites.

3. Save a version before you deploy

Sites publishing has two stages:

  1. Save a version. ChatGPT builds a deployable candidate. Use this when you want a reviewable build.
  2. Deploy a version. ChatGPT publishes a production URL.

Every deployed URL is production. If you need to review a build first, ask ChatGPT to save a version without deploying it.

Sites does not have a standalone Codex CLI or IDE manager. You can still use Codex CLI to edit and test a local project before publishing.

4. Choose storage only when the product needs it

Ask Sites for durable state when people expect the hosted app to remember something:

  • D1 for structured records (official limit: 10 GB).
  • R2 for uploaded files.
  • Both when you need searchable metadata plus file bytes.

Do not request durable storage for a theme toggle or a dismissed banner.

5. Share the narrowest audience

A new Site is limited to its owner and workspace admins until you change access. Visitor access is not editor access.

Before you share:

  • Review generated text, images, forms, and uploaded files.
  • Keep secrets out of prompts, attached files, and Site content.
  • If you add Sign in with ChatGPT, keep authorization in server-side code.

Official docs say Sites does not support data residency or inference residency at launch. Do not process Protected Health Information or payment-card data.

Official sources

Continue learning

Related models, implementation guides, comparisons, and concepts.