Portable publishing vs an integrated site builder

temp.md vs ChatGPT Sites

ChatGPT Sites—also created from Codex in supported surfaces—is an integrated way to generate, preview, version, and deploy interactive sites. temp.md is not a competing site builder. It is the lightweight publishing layer an agent can call when finished files need a stable URL outside the build environment.

Reviewed against published product information · July 2026

Short answer

Choose ChatGPT Sites when you want ChatGPT or Codex to build and host a richer site as one managed workflow. Choose temp.md when you already have the artifact, need tool-neutral publishing, or want an anonymous external review link with deliberate lifecycle controls.

Choose temp.md for

  • Publishing finished files from any agent or automation
  • Anonymous, zero-setup external review links
  • Temporary work that should cool, expire, restore, or be claimed
  • Protocol access through MCP, A2A, CLI, and REST

Choose ChatGPT Sites for

  • Prompt-to-site creation with an integrated preview loop
  • Interactive websites and lightweight apps
  • Workspace-managed creation and publishing
  • Custom domains where the feature is available

Feature comparison

The practical differences.

Capability temp.md ChatGPT Sites
Primary product Artifact publishing and lifecycle AI site builder and managed hosting
Who can publish Anonymous users, agents, or accounts Eligible paid ChatGPT plans and enabled workspaces
Availability Open web endpoint Plan, region, rollout, and admin controls apply
Public sharing Public by default; password optional after claim Supported where public publishing is enabled
Bring your own files Core workflow Built through the Sites workflow
Custom domains Not currently offered Available in supported configurations
Lifecycle Activity-based expiry with restore and claim Managed deployments and versions
Live data and backend Static frontend; bring external services Lightweight apps, with platform capability limits

Based on each product's published capabilities as of July 2026. Availability and plan rules can change.

Where the choice matters

01

Sites owns the build-and-host workflow

ChatGPT Sites can take a prompt and source material through preview, revision, versioning, and deployment. That integration is valuable when the site itself is the deliverable and the creator wants the platform to manage the whole process.

02

temp.md begins after the build

An agent hands temp.md an HTML file, Markdown document, CSV, Mermaid diagram, or static bundle. The service returns a canonical public URL and a scoped token for later updates. The same contract works whether the files came from Codex, Claude, Cursor, a CI job, or a custom agent.

03

Governance and lifecycle solve different problems

Sites availability and public publishing can depend on paid-plan access, region, rollout, and workspace administration. temp.md is anonymous-create-first and intentionally temporary: updates extend activity, important work can be claimed, and inactive work eventually disappears.

FAQ

Common questions.

Is ChatGPT Sites the same as Codex Sites?

ChatGPT Sites is the current product name for sites created in supported ChatGPT Work and Codex experiences. Availability and controls depend on the plan, region, and workspace.

Can ChatGPT Sites publish publicly?

Public publishing is supported in eligible configurations, but administrators can control it and Enterprise public publishing is off by default at launch.

When should a Codex user choose temp.md instead?

Choose temp.md when Codex already produced the files and you want a quick, portable external link without creating a managed Site or requiring an account.

Try the difference

Give your agent a public handoff.

Publish anonymously, update the same URL, and claim the work only when it needs to stay.

ChatGPT Sites details are based on its own published documentation and were accurate as of July 2026. Capabilities and plan availability can change.