Sites

Sites lets ChatGPT create, host, refine, and share websites, web apps, and games. Use Sites when you want to turn a prompt or compatible existing project into a hosted experience without setting up a separate deployment workflow.

Get started with Sites

In ChatGPT, include the word “website” in your prompt or mention @Sites to start the Sites workflow explicitly.

Prompt Sites for common tasks

For a new website, dashboard, or internal tool, include the audience, core experience, and required information:

When a site needs durable application data or uploaded files, say so in the request:

Review Site analytics

Sites records traffic automatically, so you can see how people use a deployed Site without adding an analytics SDK. The analytics view shows total unique visitors and page views, plus both metrics over time. Change the date range or granularity to inspect a different period.

Add Sign in with ChatGPT

Public Sites can remain open to everyone while offering optional Sign in with ChatGPT for identity-aware features, such as saved progress, personalized views, or records that belong to a specific person. Workspace-restricted Sites already use ChatGPT identity to enforce their sharing settings.

Ask Sites to add the sign-in experience:

<a href="/signin-with-chatgpt">Sign in with ChatGPT</a>
<a href="/signout-with-chatgpt">Sign out</a>

Bring user data to your Site with plugins

Use plugins in Sites to build a Site that loads data from each Site viewer’s own connected apps. For example, an issue dashboard can show your assigned issues to you and your teammate’s assigned issues to them. Each visitor signs in with ChatGPT and chooses which connected accounts and access to allow.

Build a Site with connected data

For example:

You can also build a document finder that links to original documents or a project overview that combines tickets and messages.

Data loading

On page load, Sites reads connected data using the visitor’s connection and permissions. Sites manages caching and reloading; ask ChatGPT Work or Codex to add a manual refresh action if needed.

By default, Sites uses a Load more action to fetch another page when the connector returns a cursor.

Sites uses getContext() to find a plugin’s actions. It returns cached tool names, descriptions, and schemas; it doesn’t refresh discovery.

Write to an app

If your Site needs to write to an app, ask for write access. Write actions must be enabled and configured, and require visitor consent and an explicit user action.

Let visitors choose their connections

To use connected features, a visitor signs in with ChatGPT, reviews the app access the Site requests, chooses the connected account and access to allow, and returns to the Site. Sharing the Site doesn’t grant access to your connected accounts. The Site receives data from the apps each visitor allows.

Visitors can continue without granting app access, but features that need it won’t work. If an app is unavailable, check that it’s connected in the right workspace and allowed by workspace settings.

Understand projects, versions, and deployments

A Site is a persistent hosted output that you can reopen, refine, configure, and share from Sites in ChatGPT.

{
  "project_id": "<project-id>",
  "d1": "DB",
  "r2": null
}

Choose a supported site shape

For new projects, the Sites workflow can start with its recommended Site starter. For an existing project, ask ChatGPT to confirm that the project can produce compatible deployment artifacts before you request a deployment.

Tell ChatGPT about the product behavior you need so it can select the appropriate site shape:

Don’t request durable storage for temporary presentation state, such as a theme choice or a dismissed banner. Do request it for product data that people expect the hosted site to remember.

Control access and secrets

A new Site is limited to its owner and workspace admins until you change its access. Keep access limited while you review the content, data handling, and expected audience.

Depending on your account and workspace settings, sharing options can include:

• Owner and workspace admins
• Selected active users or groups, where supported
• Invited external viewers, when external invitations are available
• Anyone in the workspace, where supported
• Anyone on the internet, only when public publishing is enabled

Visitor access lets people open the Site; it doesn’t give them editing access. In Enterprise workspaces, public publishing is off by default and must be enabled by an admin.

For limited sharing, invited visitors must sign in with the account that received access. A public Site is available without ChatGPT workspace access. A Site’s audience setting and any sign-in feature built into the Site are separate controls.

For example:

Invite people outside your workspace

External invitations let you give named people access to a Site without making it public. You can invite viewers outside your workspace, or share a private Site from a personal account. The feature is rolling out to Sites users on Plus, Pro, Business, and Enterprise plans.

External viewers can open and use the Site. They don’t become workspace members or Site editors, and can’t edit or publish the Site. The invitation grants access to this Site; review its content and connected data before sharing.

In Enterprise, admins manage Allow members to invite external visitors to sites under Workspace settings > Permissions & roles. This permission is separate from permission to publish Sites publicly. Business workspaces don’t have a separate external-invitation permission toggle; Sites must be enabled, and the feature must be available to the account. If the invitation option is missing, check the selected account, Site ownership, workspace permissions, and rollout availability.

To remove a viewer, open the Site’s sharing controls and remove their access. Also check the remaining audience settings: removing one invitation doesn’t remove access the person has through public, workspace, or group sharing.

Collaborate on a Site

Site collaboration requires a workspace. When the feature is available, a Site owner can invite active members of the same workspace as editors.

Editors can read the Site’s live database data. Invite only people you trust with the Site’s code and data.

The Site owner manages editor access and can promote an existing visitor to editor, change an editor to Can view, or remove their access. Co-editing doesn’t add a separate workspace permission toggle.

Editors can’t change the Site’s audience, invite or remove other people, manage settings or analytics, restore an earlier version, or transfer ownership. An editor also can’t perform the Site’s first publish; the owner must publish the Site before editors can publish later updates.

Editor access is separate from visitor access. The steps above first add the person as a visitor, then grant editing access. Promoting a visitor to editor doesn’t change the Site’s audience setting.

Configure runtime environment values

Open Sites, then open the Site’s settings to add, update, or remove hosted environment variables and secrets. Keep secret values out of prompts, attached files, and Site content.

Change a Site URL

Where URL editing is available, Site owners can change the ChatGPT-hosted URL for an existing Site without creating another deployment.

1. Open Sites, find the Site, and open its settings.
2. Find the Site URL and select Change URL.
3. Enter an available name. It must contain at least five characters, start with a lowercase letter, and use only lowercase letters, numbers, and single hyphens. It can’t end with a hyphen or contain consecutive hyphens.
4. Confirm the change and wait while Sites updates the address.

The URL change doesn’t create another deployment. The previous address redirects to the new one, including routes and query parameters.

Changing the ChatGPT-hosted URL doesn’t add, remove, or change a custom domain. Custom domains are a separate, existing feature; use the custom-domain settings when that feature is available.

Connect a custom domain

Where custom domains are available, you can connect an apex domain or subdomain that you already own. Sites doesn’t register domains for you, so you must be able to change the domain’s DNS records. Custom domains aren’t available in Enterprise workspaces at launch.

To connect a domain:

1. Open the Site’s settings and select Add domain.
2. Enter the apex domain or subdomain you want to use.
3. Copy the DNS records and values Sites provides, then add them through your domain provider.
4. Wait a few minutes, then return to the Site’s settings and refresh the domain status.

You can also ask ChatGPT to help point the domain at your Site. If browsing or computer use is enabled, ChatGPT can help you navigate your domain provider after you sign in.

Review before you share

Before you share a Site:

• Review its content, generated text and images, links, uploaded files, forms, and interactive behavior.
• Confirm that it doesn’t expose confidential or sensitive information, secret values, or third-party content you don’t have the right to share.
• Test the Site from the intended visitor experience, including its access and sign-in behavior.
• Review features that collect personal information or other visitor content. Decide whether the Site should collect, share, or publish that information.
• If the Site uses Sign in with ChatGPT, explain what visitor information it receives and how it uses that information.
• If the Site collects or processes personal data, comply with applicable privacy and data-protection laws.
• Choose the narrowest sharing option that fits the intended audience.
• Open the shared Site and confirm that the intended audience can visit it.

Take down or delete a Site

To remove access without deleting a Site, open its sharing settings and restrict access to yourself or selected people. Confirm that the previous audience can no longer open it.

To permanently delete a Site:

1. Open Sites and locate the Site.
2. Select Delete site and follow the instructions in the prompt.
3. Enter the Site slug, then select Permanently delete.

Deleting a Site permanently removes it. You can’t restore a deleted Site.

Understand limits and unsupported uses

Sites hosts web experiences that run in the supported Sites runtime. Some frameworks, private networks, databases, background services, and hosting patterns aren’t supported.

HTTP, HTTPS, and WebSockets are supported. Raw inbound and outbound TCP connections aren’t.

Each Site has these storage limits:

Sites doesn’t support data residency or inference residency at launch. This includes deployed Sites, Site code, D1 and R2 data and file storage, generated artifacts, and logs.

Don’t use Sites to process Protected Health Information or payment-card data; target children under 13 or the applicable age of digital consent; enable financial transactions; distribute malware; enable phishing; impersonate people or organizations; or otherwise violate OpenAI policies. See Creating and managing ChatGPT Sites for the current limits and policy links.

Related documentation