Focused guides
PreviewShip Documentation
Start here if you want to deploy framework build output, HTML, Markdown, PDF, or an AI-generated page, then manage the fixed project URL, access mode, versions, and cleanup paths.
Codex Chat Sharing
This is a companion workflow for Codex users. It is useful for sharing debugging context, implementation records, or review discussions, but it is not required for normal PreviewShip deployments.
npx skills add blockdancez/PreviewShip --skill share-codex-chat -a codex -g --yes$share-codex-chat 分享当前 Codex 对话Claude Code Chat Sharing
This is a companion workflow for Claude Code users. It is useful for sharing research trails, implementation records, and review discussions while preserving tool activity as readable timeline details.
npx skills add blockdancez/PreviewShip --skill share-claude-code-chat -a codex -g --yes$share-claude-code-chat 分享 Claude Code 对话Quick Start
PreviewShip turns browser-ready frontend artifacts into fixed preview URLs. Choose the method that fits your workflow:
- 1Register a free account at previewship.com
- 2Create an API Key in the console (API Keys page)
- 3Deploy React/Vue/Vite/Next static output, a zip with index.html, a single HTML/Markdown/PDF file, pasted HTML, or agent-generated output via CLI, MCP, editor extension, or console upload
- 4Share the fixed preview URL, then manage access, versions, rollback, redeploy, or project cleanup when needed
Supported Inputs & Project Model
Use PreviewShip when the browser can already open the artifact you want to share. It is built for frontend review links, not source-code builds or backend hosting.
Built frontend output
Deploy React, Vue, Vite, Astro, Svelte, Angular, Next static export, or any static folder such as dist, build, out, public, or a zip that contains index.html and assets.
Single files and pasted HTML
Upload a standalone .html, .md, .markdown, or .pdf file, or paste a complete HTML document. PreviewShip packages it into a browser-ready preview.
Fixed project URL
A project keeps one stable preview URL. Rollback queues a new deployment from the retained version and switches the latest pointer only after success.
Public or password access
Projects are public by default. Pro projects can require a password, and switching back to public clears the stored password.
Version history and recovery
Free shows 3 retained versions, Pro Monthly shows 10, and Pro Yearly shows 40. Rollback queues a new deployment from the retained version; redeploy latest can restore an expired link when the artifact is retained.
Quota cleanup
Free includes 1 project. If it is full, delete an unused project or upgrade before deploying or claiming another preview. Deletion is permanent.
CLI
Deploy from the terminal with one command, then manage fixed project URLs, public/password access, versions, rollback, redeploy, and deletion. The CLI also supports JSON output for AI agents and CI.
Install
Use npx directly (no install needed) or install globally:
npm install -g previewshipnpx previewship deploy ./distSet API Key
Set your API Key for authentication:
previewship loginpreviewship login --key ps_live_your_key_hereOr set via environment variable:
PREVIEWSHIP_API_KEY=ps_live_... previewship deploy ./distDeploy
Deploy a built static directory or a single HTML, Markdown, or PDF document to get a preview link:
previewship deploy ./distpreviewship deploy ./report.html -n ai-reportpreviewship deploy ./README.md -n docs-previewpreviewship deploy ./dist -n my-project --exclude "*.map"JSON Output for Agents
Use --json flag for structured output, ideal for AI agents and CI pipelines:
previewship deploy ./dist --jsonProject management commands
Use these commands when you need to inspect projects, change access, restore an expired link, roll back the fixed URL, or delete an unused Free project slot.
previewship deployments list --json
previewship projects list --json
previewship projects access 42 --password "review-pass"
previewship projects access 42 --public
previewship projects versions 42
previewship projects rollback 42 105 --confirm my-project
previewship projects redeploy 42
previewship projects delete 42 --confirm my-projectMCP Server
The MCP server lets AI coding agents deploy previews and manage projects as native tool calls. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client.
Configuration
For Claude Code, add to ~/.claude/settings.json:
{
"mcpServers": {
"previewship": {
"command": "npx",
"args": ["-y", "previewship-mcp"],
"env": {
"PREVIEWSHIP_API_KEY": "ps_live_your_key_here"
}
}
}
}For Cursor, create .cursor/mcp.json in your project root:
{
"mcpServers": {
"previewship": {
"command": "npx",
"args": ["-y", "previewship-mcp"],
"env": {
"PREVIEWSHIP_API_KEY": "ps_live_your_key_here"
}
}
}
}For Windsurf, add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"previewship": {
"command": "npx",
"args": ["-y", "previewship-mcp"],
"env": {
"PREVIEWSHIP_API_KEY": "ps_live_your_key_here"
}
}
}
}Available Tools
- deploy_preview — Deploy a build-output directory or a single HTML, Markdown, or PDF document and get a fixed preview URL
- check_deployment — Check deployment status by ID
- show_usage — Show remaining deployment quota
- list_projects / get_project — Inspect fixed URLs, project status, access mode, and redeploy availability
- get_project_access / set_project_access — Switch between PUBLIC and PASSWORD; PUBLIC clears the saved password
- list_project_versions / rollback_project_version — Show retained versions and roll a fixed URL back to a historical deployment
- redeploy_project_latest — Restore an expired fixed preview link from the latest retained artifact
- delete_project — Delete a confirmed project and permanently remove its fixed URL, hosted project, deployment association, and Showcase entry
Codex Chat Sharing
PreviewShip also provides an optional Codex skill for sharing the current Codex conversation. It turns the visible chat transcript into a high-fidelity HTML page, deploys it with the PreviewShip CLI, and returns a public URL.
Install the skill
npx skills add blockdancez/PreviewShip --skill share-codex-chat -a codex -g --yesnpx skills add blockdancez/PreviewShip --skill share-codex-chat -a codex --yesUse in Codex
After installation, reference the skill in a Codex conversation:
$share-codex-chat 分享当前 Codex 对话Claude Code Chat Sharing
PreviewShip also provides an optional Claude Code skill for sharing Claude Code conversations. It reads local Claude Code JSONL history, renders the visible chat into a high-fidelity HTML page, deploys it with the PreviewShip CLI, and returns a public URL.
Install the skill
npx skills add blockdancez/PreviewShip --skill share-claude-code-chat -a codex -g --yesnpx skills add blockdancez/PreviewShip --skill share-claude-code-chat -a codex --yesUse in Codex
After installation, reference the skill from Codex and ask it to share a Claude Code conversation:
$share-claude-code-chat 分享 Claude Code 对话Cursor Setup
Cursor is fully compatible with VS Code extensions. You can install PreviewShip the same way.
Install via Command Palette
- 1Open Cursor, press Ctrl+P (Cmd+P on Mac)
- 2Paste the command below and press Enter:
ext install previewship.previewshipInstall via VSIX
If you prefer offline installation, download the .vsix file and follow the "Manual VSIX Install" section below.
VS Code Setup
Open VS Code, press Ctrl+P (Cmd+P on Mac), paste the command below and press Enter:
ext install previewship.previewshipManual VSIX Install
If the marketplace is unavailable in your environment, you can install the extension manually via a .vsix file.
Installation Steps
- 1Download the .vsix file using the button above
- 2Open Cursor or VS Code, go to Extensions panel (Ctrl+Shift+X)
- 3Click "..." in the top-right of the Extensions panel → "Install from VSIX..." → select the downloaded file
Alternatively, install via command line:
code --install-extension previewship-latest.vsixAPI Key
An API Key is required for all deployment methods (CLI, MCP, editor extension). Here's how to create one:
- 1Log in to previewship.com and go to the API Keys page
- 2Click "Create API Key", give it a name, and copy the generated key
- 3Use the key in CLI (previewship login), MCP config (PREVIEWSHIP_API_KEY env var), or editor extension (Set API Key command)
Deploy from Editor
Once the extension is installed and your API Key is set:
- 1Open your frontend project folder in the editor
- 2Open the command palette (Ctrl+Shift+P) and run "PreviewShip: Deploy Workspace, HTML, Markdown, or PDF File" or "PreviewShip: Deploy Active HTML, Markdown, or PDF File"
- 3The extension packages the selected build output, HTML, Markdown, or PDF file, uploads it, and returns a preview URL when ready
Console Deploy
You can also deploy directly from the web console without any tools. The console supports uploading a build-output zip, uploading a single HTML, Markdown, or PDF file, or pasting HTML source:
- 1Log in and go to the Deploy page
- 2Select or create a project, then upload a .zip containing static build output, upload a .html/.md/.markdown/.pdf file, or paste a complete HTML document
- 3PreviewShip deploys zip artifacts as static sites, packages single HTML input as index.html, adds a safe viewer for Markdown, and adds a redirect entry that opens PDF in the full-screen browser-native viewer
Project Management
Projects are the stable container behind PreviewShip links. Each project owns a fixed URL, a latest deployment pointer, access mode, retained versions, and optional Showcase state.
- Projects are created automatically when you deploy with a new project name, including claimed guest previews.
- The fixed project URL does not change on each deploy; deployments and rollbacks update what that URL serves.
- Public projects can be shared normally. Pro projects can use password access; switching back to public clears the password.
- Version history is plan-based: Free keeps 3 rollback-capable versions, Pro Monthly keeps 10, and Pro Yearly keeps 40 when artifacts are retained.
- Free includes 1 project. If the limit is full, delete an unused project or upgrade before deploying or claiming another preview.
- Deleting a project removes the fixed preview URL, hosted project, deployment association, and Showcase entry permanently.
- Only public, share-approved Showcase items can be indexed. Password projects, private or hidden items, and expired inaccessible content stay out of sitemap indexing.
Plans & Limits
PreviewShip plans combine deploy quota, project count, upload allowance, retention, version history, access control, and watermark removal:
| Feature | Free | Pro Monthly | Pro Yearly |
|---|---|---|---|
| Projects | 1 | 10 | 20 |
| Daily Deploys | 5 | 50 | 80 |
| Monthly Deploys | 20 | 300 | 500 |
| Concurrent Builds | 1 | 3 | 3 |
| Max Zip Size | 15 MB | 50 MB | 80 MB |
| Monthly Upload | 200 MB | 2 GB | 4 GB |
| Preview Expiry | 3 days | 30 days | 365 days |
| Version history / rollback | 3 versions | 10 versions | 40 versions |
| Access control | Public only | Public or password | Public or password |
| PreviewShip Watermark | Included | Removed | Removed |
FAQ
Which frameworks are supported?
PreviewShip works with any static frontend output — React, Vue, Svelte, Next.js export, vanilla HTML, Markdown documents, etc. Build first and deploy the output folder that contains index.html, or deploy a single .html/.md/.markdown/.pdf file directly.
How do I deploy from an AI coding agent?
Add the PreviewShip MCP server to your agent (Claude Code, Cursor, Windsurf), or use the CLI with --json flag. Your agent can deploy previews as part of the conversation.
What's the difference between CLI and MCP?
The CLI is a terminal command (npx previewship deploy). MCP is a protocol that lets AI agents call deploy as a native tool. Use CLI for scripts and manual deploys, MCP for seamless agent integration.
What happens when a preview expires?
Expired previews return a 404 page. The deployment record remains visible in your dashboard. You can redeploy to get a new link.
Is there a file size limit?
Yes. The Free plan allows up to 15 MB per upload. Pro plans support 50-80 MB depending on the billing cycle. Uploads can be build-output zips or single HTML, Markdown, or PDF files.
Is there a free tier?
Yes. The Free plan includes 5 deploys per day, 20 per month, 1 project, and 3 recent rollback versions. Free preview links include the PreviewShip watermark; Pro removes it, adds password access, and keeps more rollback history. No credit card required.
Can I deploy a single HTML, Markdown, or PDF file?
Yes. The web console accepts a single .html, .md, .markdown, or .pdf file or pasted HTML source; CLI/MCP accepts paths like ./report.html, ./README.md, and ./report.pdf; the VS Code/Cursor extension can deploy the active file. HTML and Markdown get web entry pages, while PDF opens in a full-screen browser-native reader.
Does each deployment create a new URL?
No. PreviewShip projects keep a fixed URL. A rollback queues a new deployment and switches the latest pointer only after it succeeds, so the review link stays stable across iterations.
Can I switch a password-protected project back to public?
Yes. Public access clears the stored project password. Public projects can be shared normally and may become eligible for Showcase and sitemap indexing when you choose to share them.
What should I do when the Free project limit is full?
Free includes one project. You can upgrade or delete an unused project before deploying or claiming another preview. Deletion removes the fixed preview URL, hosted project, deployment association, and Showcase entry permanently.