# Sites > For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL. Sites is in public beta and is available with ChatGPT Plus, Pro, Business, Enterprise and Edu plans. Plan-specific usage limits apply across all Sites during the beta. ChatGPT shows the current limits and notifies you as you approach one. Reaching a limit can prevent you from creating a Site, adding storage, or keeping a high-usage Site public, but you can still edit and manage existing 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. Open **Sites** in the ChatGPT desktop app. You can start a site from a prompt or from a compatible local project, then return to the Sites view to manage it. Use Sites in ChatGPT on the web to create and manage hosted sites. Select **More** > **Sites**, or go directly to [chatgpt.com/sites](https://chatgpt.com/sites), to find Sites you've created. Sites doesn't have a standalone Codex CLI management view. Use ChatGPT web or the desktop app to create, save, deploy, and manage a Sites project. You can still use Codex CLI to edit and test a local project before publishing it. Sites doesn't have a standalone IDE extension management view. Use ChatGPT web or the desktop app for Sites operations, and use the IDE extension to edit and test the local source project. Every Sites deployment URL is a production deployment. If you want to review a build before it becomes live, ask ChatGPT to save a version without deploying it. ## Get started with Sites In ChatGPT, include the word "website" in your prompt or mention `@Sites` to start the Sites workflow explicitly. 1. Describe the Site Describe the audience, purpose, required behavior, and information the Site should use. 2. Review the Site Review the generated content and behavior. Check that the Site uses the intended information and handles data as expected. 3. Refine the Site Describe the changes you want. Add relevant files or visual context when they will help ChatGPT make the change. 4. Manage and share the Site Return to **Sites** to reopen or refine the Site. When it's ready, choose who can visit it and share the resulting link. In the preview, select **Edit**. Under **Describe website edits**, describe the changes you want. Use **Screenshot** or **Add files and more** when additional context would help. ## Prompt Sites for common tasks For a new website, dashboard, or internal tool, include the audience, core experience, and required information: ```text Build a project request dashboard for my operations team. Let team members submit requests, see who owns each one, update the status, and filter the list. Require people to sign in with their workspace account, and keep the request data saved between visits. ``` For an existing project, ask Sites to prepare and publish the current app: ```text Deploy this project with Sites. Check whether it is compatible, make any required changes, and give me the deployment URL. ``` When a site needs durable application data or uploaded files, say so in the request: ```text Add player scores and avatar uploads to this game. Keep the scores and uploaded avatars between visits. ``` Browse the [Sites showcase](https://developers.openai.com/showcase) for deployed internal apps and the full prompts used to create them. ## 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. Open **Sites**, find the Site, then select **More actions** > **Analytics**. Go to [chatgpt.com/sites](https://chatgpt.com/sites), find the Site, then select **More actions** > **Analytics**. Sites doesn't have a standalone analytics view in the CLI or IDE extension. Open the Site in ChatGPT on the web or in the desktop app to review its analytics. > Illustration: Interactive Sites analytics dashboard showing unique visitors and page views over seven days. Analytics is currently available for Sites that aren't owned by an Enterprise workspace. ## 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: ```text Add Sign in with ChatGPT to this public Site. Keep the Site available to signed-out visitors. Show a Sign in with ChatGPT action when someone is signed out. After they sign in, greet them with their full name when available, or their email address otherwise. Add a Sign out action, and keep authorization decisions in server-side code. ``` Sites handles the sign-in and sign-out flows through platform-provided paths, then returns the visitor to your Site: ```html Sign in with ChatGPT Sign out ``` After a visitor signs in, Sites forwards their identity to the server through these request headers: - `oai-authenticated-user-email` contains the authenticated email address. - `oai-authenticated-user-full-name` may contain a non-empty profile name. Treat it as optional and fall back to the email address. Keep authorization decisions in server-side code, and don't depend on name-split headers. ## Understand projects, versions, and deployments A Site is a persistent hosted output that you can reopen, refine, configure, and share from **Sites** in ChatGPT. A Sites project links a local source project to hosting managed through Sites. Sites stores that linkage and optional storage binding names in `.openai/hosting.json`. A newly created local starter can begin without a `project_id`; Sites adds one after it provisions the hosted project. For example, a provisioned site that uses a relational database binding and no file storage can contain: ```json { "project_id": "", "d1": "DB", "r2": null } ``` A Site appears in your Sites list even after the ChatGPT Work chat that created it ends. You don't need a local project or manifest to start a Site on the web. A Site is separate from a ChatGPT Project. Sites publishing has two separate stages: 1. **Save a version.** ChatGPT builds a deployable version. For a local source project, ChatGPT associates the version with the Git commit used for the build. Use this stage when you want a reviewable deployment candidate. 2. **Deploy a version.** ChatGPT publishes a saved version and reports the production URL when deployment succeeds. Use this only when you intend for the selected audience to access the site. Ask ChatGPT to list or inspect saved versions when you need to identify a previous deployment candidate. ## 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: | Site need | What to ask Sites for | | -------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Content-led website or landing page | A Site with no persistent application state unless the experience requires it | | Saved records, user progress, or game scores | D1, a relational database for durable structured data | | Images, documents, audio, video, or other uploads | R2, object storage for files | | Uploaded files with searchable metadata | D1 for metadata and R2 for file contents | | Internal site that needs the current workspace user's identity | Workspace-authenticated user identity | | Public sign-in or an external identity provider | An authentication-enabled Site | 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: ```text Change this Site's access to everyone in my workspace after showing me the current Site and confirming its URL. ``` ### 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. 1. Open a Site you own and select **Share**. 2. To keep the Site private, set **Who has access** to **Only those invited**. 3. Enter the viewer's email address under **Search for people or groups**, or **Enter an email address** for a personal Site, then select the recipient. 4. Review the audience and the recipient's **Viewer** access, then select **Invite**. 5. Confirm that the viewer appears in the saved access list. Share the Site's link and ask them to sign in with the account that received access. 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. 1. Open the Site and select **Share**. 2. Under **Add people or groups**, find and select a workspace member. They are added as a visitor. 3. Open **Can view** next to that person and choose **Can edit**. Access saves automatically. The Site appears under **Shared with you** in the member's Sites view. 4. The editor can open the Site, make changes, save versions, and publish updates after the owner has published the Site for the first time. 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. Go to [chatgpt.com/sites](https://chatgpt.com/sites), find the Site, then select **More actions** > **Settings**. Don't store these values in `.openai/hosting.json`. Keep local `.env` and `.env.example` files aligned with the keys needed for local development, and don't commit secret values. When you add, update, or remove hosted environment values, ask ChatGPT to redeploy the approved saved version so the next deployment uses the updated configuration. ## 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](https://help.openai.com/en/articles/20001340). - Choose the narrowest sharing option that fits the intended audience. - Open the shared Site and confirm that the intended audience can visit it. For a Site built from a local project, also review the source changes and any database migrations in the Codex [review pane](https://learn.chatgpt.com/docs/code-review?surface=app). ## 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: | Resource | Limit | | ------------------- | ---------------------- | | D1 database storage | 10 GB | | R2 object storage | No fixed storage limit | 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](https://help.openai.com/en/articles/20001339) for the current limits and policy links. ## Related documentation - [ChatGPT desktop app](https://learn.chatgpt.com/docs/app) introduces app navigation, projects, and chats. - [Review and ship changes](https://learn.chatgpt.com/docs/code-review?surface=app) explains how to inspect source changes before publishing them. - [Projects and chats](https://learn.chatgpt.com/docs/projects) explains how folder and workspace context carries across chats. - [Review and ship changes](https://learn.chatgpt.com/docs/code-review) explains the review workflow for each Codex client. - [Sandboxing](https://learn.chatgpt.com/docs/sandboxing) explains the local execution boundary. - [Open Sites in ChatGPT](https://chatgpt.com/sites) to return to Sites you've created. - [Projects and chats](https://learn.chatgpt.com/docs/projects?surface=web) explains how to keep related chats and source files together. - [Work with files](https://learn.chatgpt.com/docs/artifacts-viewer?surface=web) explains how to review generated files in ChatGPT web.