If you update an event page a few times a month, requests and retained data may dominate the budget. If you revise forms for three teams every day, building can hit a limit even with the same visitor traffic. When choosing a plan for ChatGPT Sites, keep separate records for editing a Site and keeping it online for a month. Compare plans against the limit you actually encounter.
From preview to billing, what each date means
OpenAI recorded a preview of Sites in the Codex app on June 2, 2026. The July 9 desktop update added custom domains for published Sites. As of November 11, OpenAI's training still describes Sites as a public beta. Eligible users can create, review and manage Sites in ChatGPT on the web or desktop. Check the intended account, region, rollout and workspace settings for the options you need.
OpenAI changelog · OpenAI Sites guide · OpenAI Work and Codex pricing · OpenAI create a Site · OpenAI shareable Site walkthrough
The current documentation describes feature access, build usage, hosting measurement and billing separately. OpenAI plans to show each Site's traffic and storage usage from December 1, with comparison across Sites for workspace admins. Hosting stays free through December 31. From January 1, 2027, Plus, Pro and Business customers are scheduled to pay above their monthly hosting allowance. The published rates are approximate proposals. Enterprise follows its agreement. Confirm the billing details and available measurements before committing an annual budget.
During the free hosting period, record which measurements you can already see and which actions you completed. Existing analytics can show visitors and page views. The upcoming hosting reports cover requests and storage. Check the source of each figure before using it for a month-end estimate. A page view can generate many requests, and a scheduled interface change may still be pending on the day you test.
What to check for Plus, Pro and Business
| Account plan | Listed monthly hosting allowance | Check before buying |
|---|---|---|
| Free / Go | Unlisted in the Sites hosting table | Check whether the intended account shows Sites and the required actions |
| Plus | 125 credits | Pilot one Site and check Work / Codex usage during building |
| Pro | 375 credits | Check the specific Pro tier for build usage. The hosting table gives one Pro row |
| Business | 125 credits / seat | Confirm the workspace, owner, editors and admin settings |
| Enterprise / Edu | Check the contracted pool for credit-based Enterprise | Confirm feature availability and billing for the agreement and role |
OpenAI Sites guide · OpenAI Work and Codex pricing · OpenAI Sites administration
OpenAI lists Plus and Pro 100, 200 and 500. For a personal account with Sites access, ask how often you will revise the Site and how often your current Work and Codex usage reaches a limit. OpenAI currently lists no five-hour Work or Codex limit for Pro, and the account dashboard shows the applicable usage windows. Ultrafast on Pro 500 is tied to supported models and surfaces. The Sites hosting table publishes a single Pro row, so the listed hosting allowance gives no basis for comparing the three Pro tiers.
OpenAI Sites guide · OpenAI Work and Codex pricing · OpenAI speed modes
Business usually enters the decision when several people need to manage a Site or when data access requires workspace controls. Visitors and editors have separate permissions. OpenAI says the owner publishes a Site for the first time. Eligible editors in the same workspace can publish later updates. Record the owner, maintainer, reviewer and intended audience together, then check that you can assign those roles in the actual workspace.
Record usage against the action that caused it
| Action or symptom | Where to look | What it tells you |
|---|---|---|
| Create or edit a Site | ChatGPT Work / Codex usage and reset | Whether a build spike is the constraint |
| Requests and storage after launch | Sites traffic and storage report | Total the Sites under the account or workspace |
| Missing invite, first-publish or edit control | Account, workspace role and rollout | Verify access before comparing offers |
| Future hosting overage | Current Sites rates and billing terms | Confirm the charge and applicable balances separately |
OpenAI Sites guide · OpenAI Work and Codex pricing · OpenAI publish and share · OpenAI Sites administration
ChatGPT Work and Codex share usage. Building and editing Sites count toward Codex usage. If you revise a form while running code reviews or other Work tasks, a change in the dashboard may come from several workflows. For a small Site trial, hold the starting conditions and speed mode steady, run the Site task in a defined window and count how many reviewable versions you save.
Record both consumption and outcome. Where Fast is available, OpenAI lists 2.5 times Standard for included usage and twice the Standard rate for purchased credits. The corresponding Ultrafast figures are 8 and 6. Check the supported model and plan. Each multiplier applies to a different usage source. Compare elapsed time, accepted versions and repeated work to see whether the extra speed helps your task.
Save a minimal version and keep the review record
Start with a static Site and fictional data. The example event page gives visitors three things to find. The first pass covers the start time, location and requirements without collecting contact details or connecting a service. Check that you can save a candidate, complete the same reading task on mobile and verify the page against its source.
OpenAI create a Site · OpenAI manage a Site · OpenAI shareable Site walkthrough
Build a ChatGPT Site for the fictional event DEMO-01.
Event: Saturday creative workshop
Time: 2026-12-05 14:00, UTC+08:00
Location: Qinghe Center, Room B
Requirements: bring paper and a pen, and check in 10 minutes early.
Show the time, location and requirements on the home page. Use the fictional inputs to check the mobile view.
Save a version for my review and list completed and pending checks.
Wait for my explicit approval before deploying, expanding access, enabling storage or connecting a service.A saved version gives you a candidate to review. Deployment makes the selected version available to its audience. Record the candidate identifier or timestamp and the acceptance result. On the next pass, reuse the inputs and make one scoped change, such as correcting the location. It becomes easier to tell a verified revision from repeated rework. After approval and deployment, check the published link as an authorized visitor.
date,workspace,site_id,version,stage,mode,usage_before,usage_after,reset_at,result,blocker
2026-11-11,personal,DEMO,01,save,Standard,record,record,record,pending,unknown
2026-11-11,personal,DEMO,02,review,Standard,record,record,record,pending,unknownTest two visitor identities before adding a form
If the workflow requires saved records, write down who submits, who reads and who maintains them before choosing storage. Verify workspace policy, the Site audience and access to individual records. A visitor who can open a form may still lack access to a particular submission. Enforce private-record rules on the server and check them with two ordinary test identities.
Add a fictional booking form to the DEMO-01 candidate.
Test identity A submits DEMO-A and identity B submits DEMO-B. Store only the event identifier and status.
A and B can read and change only their own records. The admin role can review aggregates.
Block cross-account reads and unauthenticated access to private records. Check direct navigation and refresh.
List results for the three access cases and identify checks that still require the corresponding test identities.
Save a reviewable version. Wait for approval before deploying, inviting anyone, importing real data or connecting an external system.| Identity | Expected observation | Record |
|---|---|---|
| Owner | Can save a version and inspect first-publish controls | Version identifier and current audience |
| Authorized visitor | Can open the intended page and submit and read their own record | Identity, record identifier and result |
| Unauthorized identity | Access is restricted or another visitor's records remain unavailable | Expected denial and actual result |
OpenAI's sharing guide says named external invitations are rolling out to Sites users on Plus, Pro, Business and Enterprise. Check the controls on the intended account. An external visitor has a different role from an editor. Public publishing starts off in Enterprise. If the project requires cross-organization access, test with an eligible identity before including it in the purchasing requirements.
Turn the trial into a purchasing decision
- Check Sites access and roles in the intended account and workspace
- Save and review a version with synthetic data
- Record build usage, speed mode and reset window
- Total requests, storage and domains across Sites
- Compare both usage categories and any future overage
- Check the delivery account and current order terms
Estimate hosting for three example Sites
Use the current proposed rates for a full-month illustration. OpenAI lists approximately 16 credits per 100,000 requests, 25 per month for a Site with storage, 150 per full-month GiB of database records, 3.75 per full-month GiB of files and 25 per custom domain per month. Domain registration costs extra. Even an empty database has the 25-credit base charge. The input volumes, request counts and domain counts below are synthetic.
| Site | Monthly requests | Database / files | Domains | Approximate usage |
|---|---|---|---|---|
| static event page | 100,000 | Off | 0 | 16.00 |
| intake booking Site | 250,000 | 0.25 / 2 GiB | 1 | 135.00 |
| busy Site | 2,000,000 | 1 / 5 GiB | 1 | 538.75 |
from decimal import Decimal
D = Decimal
# Illustrative inputs. Rates are OpenAI's proposed 2027-01-01 rates.
# name, monthly requests, storage enabled, DB GiB, file GiB, custom domains
sites = [
('static', 100_000, False, '0', '0', 0),
('intake', 250_000, True, '0.25', '2', 1),
('busy', 2_000_000, True, '1', '5', 1),
]
def estimate(row):
_, requests, storage, db_gib, file_gib, domains = row
return (
D(requests) / D(100_000) * 16
+ (25 if storage else 0)
+ D(db_gib) * 150
+ D(file_gib) * D('3.75')
+ D(domains) * 25
)
estimates = {row[0]: estimate(row) for row in sites}
for name, credits in estimates.items():
print(f'{name}: {credits:.2f} credits')
for name, total in {
'static_plus_intake': estimates['static'] + estimates['intake'],
'busy_only': estimates['busy'],
}.items():
print(f'{name}: {total:.2f} credits')
for plan, allowance in {'Plus': D(125), 'Pro': D(375)}.items():
excess = max(D(0), total - allowance)
print(f' {plan} excess: {excess:.2f} credits')
static: 16.00 credits
intake: 135.00 credits
busy: 538.75 credits
static_plus_intake: 151.00 credits
Plus excess: 26.00 credits
Pro excess: 0.00 credits
busy_only: 538.75 credits
Plus excess: 413.75 credits
Pro excess: 163.75 creditsRunning only static and intake gives a total of 151 credits. With the full allowances available, this is 26 above Plus and 224 below Pro. The busy Site alone exceeds both by 413.75 and 163.75 respectively. Each comparison assumes no other Sites draw from the allowance and storage stays constant for the month. Private connections and domain registration are excluded. Total all Sites on the account and substitute actual charges when the rates are finalized.
Identify the main cost before comparing an upgrade with overage
The 135 credits for intake include 40 for traffic, 25 for the storage base fee, 37.50 for records, 7.50 for files and 25 for the domain. If the default domain meets the need, subtract 25 to get 110. Intake alone would fit under Plus's 125. Intake plus static still reaches 126, one credit over. Decide what must persist, for how long and which Sites still need to be online before comparing plans.
Use page views to understand traffic trends and request counts as the cost input. Opening one page can request scripts, images and endpoints. Record database and file storage separately in GiB-months because their rates differ. If you start with a short sample, log its dates, any unusual event traffic and requests your sample could miss. Recalculate when the hosting measurements are visible.
Two higher-usage scenarios make a better planning check than a single average. Double intake's monthly requests from 250,000 to 500,000 while holding other inputs fixed to add 40 credits. Restore the original requests and raise the database from 0.25 to 0.50 GiB for the full month to add 37.50 credits. Keep both sets of inputs and update them when you have report data. If both grow together, combine the changes to see what deserves closer monitoring.
When Plus has enough build usage and only a small hosting overage remains, compare the confirmed overage price with the subscription difference. If repeated reset windows block project delivery, estimate the time spent waiting or rebuilding, then compare Pro with the workflow's needs. The two scenarios can point to different choices. Until the overage settlement price is confirmed, compare credits with the allowance and leave the cash estimate open.
Match the workflow to the current store options
| Confirmed requirement | Option to review | Confirm before paying |
|---|---|---|
| Keep the current Site owner and account | Plus or Pro on your own account | Account identity, supported order status and delivery terms |
| Run an independent pilot | Ready-made Plus or Pro account | The separate account's available features and ongoing control |
| Maintain a Site as a team | ChatGPT Business seats | Workspace, admin, owner and editor permissions |
| Occasional build usage overage | Codex credit pack | Eligible account, covered usage and terms |
The Chinese subscription and international pricing pages list Plus and Pro 100, 200 and 500 as own-account subscriptions or separate ready-made accounts. They also list Business seats and Codex credits. For an existing Site, confirm that delivery targets the current owner's account. Treat a separate account as a separate trial environment. Check current product procedures for handing off Sites, versions, domains or team data.
OpenAI publish and share · OpenAI manage a Site · ClaudeMax Chinese subscriptions · ClaudeMax English pricing
ClaudeMax operates as an independent store. Use the live catalog to check pricing, availability, order precheck and delivery terms. Verify Sites access, audience controls and usage in the OpenAI product. The store describes Codex packs as usage for eligible accounts. Check future Sites billing terms to see what balances can pay hosting overage. This estimate does not apply a Codex pack to hosting.
OpenAI Sites guide · ClaudeMax Chinese subscriptions · ClaudeMax English pricing
- See ChatGPT Plus for your own account — Check precheck and delivery terms for the current account.
- See ChatGPT Pro 200 for your own account — Compare your recurring build limits and confirm purchase conditions.
- See ChatGPT Business seats — Check the workspace, seats and administration rights.
- See the Codex credit pack — Check eligible accounts and covered usage.
Use the pilot to decide whether to stay, upgrade or change the Site
For a personal event page, document index or showcase without data collection, try a small version on an eligible account you already use. Plus is a reasonable starting point to verify when you make few revisions and have hosting headroom. If you see a usage warning, record when it appeared, the mode, available balance and what finished. On the next pass, reduce inputs and repeated revisions while keeping the acceptance criteria steady. See whether the limit still interrupts the work.
OpenAI Sites guide · OpenAI Work and Codex pricing · OpenAI create a Site
For team maintenance, verify the workspace, first publication, role checks and ongoing owner before purchasing. For high traffic or long retention, measure requests and data volume and confirm when proposed rates take effect. If you lack credible hosting data at month end, wait for the reports before making a billing decision. Your notes should show whether a purchase addresses a build window, a team permission requirement or hosting headroom.
OpenAI Sites guide · OpenAI publish and share · OpenAI Sites administration
Confirm the intended account and keep one reviewable version plus a full-month estimate. The order record should identify the current constraint, the metric the plan should improve and the evidence you will use to check next month.
OpenAI Sites guide · OpenAI Work and Codex pricing · ClaudeMax Chinese subscriptions · ClaudeMax English pricing