Guide / Codex

Share Codex-generated websites as preview links

Turn Codex-generated HTML, Markdown, or built frontend output into a live preview URL for review and handoff.

Updated 2026-06-22Practical deployment guide

Answer First

When Codex or Claude Code creates or edits a website, the next useful step is a browser URL. PreviewShip can publish a built frontend folder, single HTML file, Markdown document, or exported AI coding chat page and return a fixed preview link for review.

Deploy build artifacts, not source-code zips.

If you upload a zip, build the project first and zip the static output folder such as dist, build, out, or public with index.html and assets. Do not zip raw React/Vue/Next source folders with package.json and node_modules. Single .html, .md/.markdown, and .pdf files are supported directly by console upload, CLI, MCP, and the VS Code/Cursor extension.

Key takeaways

Deploy built output rather than raw source folders.
Use CLI, browser upload, share-codex-chat, or share-claude-code-chat depending on the artifact.
A fixed PreviewShip link keeps handoff threads cleaner across repeated Codex iterations.

Recommended workflow

1

Have Codex build or export the static artifact.

2

Deploy the dist/build/out folder, .html file, Markdown file, or exported chat HTML.

3

Copy the PreviewShip URL into the Codex thread or handoff document.

4

Redeploy later changes to the same project link.

Comparison snapshot

ArtifactPreviewShip pathWhy it helps
Built frontendDeploy dist/build/outReal browser QA
Single HTMLUpload or paste HTMLFast review link
MarkdownUpload or paste MarkdownReadable specs and reports
Codex chatshare-codex-chat skillShare implementation context
Claude Code chatshare-claude-code-chat skillShare research and tool traces

Codex output is often artifact-shaped

Codex can produce a full app, a static HTML proof, a Markdown report, or a rendered chat export. PreviewShip works best once that output is browser-ready.

For frameworks, ask Codex to run the build and deploy the generated output folder. For standalone HTML or Markdown, deploy the file directly.

FAQ

Can Codex deploy directly to PreviewShip?

Codex can use CLI workflows or installed skills to produce deployable artifacts. PreviewShip also supports browser upload and paste for manual fallback.

Is share-codex-chat the same as deploying a website?

No. share-codex-chat exports the visible Codex conversation as an HTML artifact. Normal PreviewShip deploys publish frontend or document artifacts.

Can I share Claude Code conversations too?

Yes. Use share-claude-code-chat when the conversation source is Claude Code. It handles Claude Code JSONL history and tool timelines separately from Codex transcripts.

Does the preview link change every time?

No. Deploying to the same project keeps the fixed project link and updates the latest deployment pointer.