Deploy a preview directly from Cursor
Install the PreviewShip extension in Cursor, set your API key, and deploy built output or an active HTML, Markdown, or PDF file to a shareable URL.
Answer First
If you work in Cursor and want the shortest path from edited files to a public preview URL, install the PreviewShip extension, set your API key once, and deploy a built static output folder or the active HTML, Markdown, or PDF file. It removes the need to zip files manually or switch to a separate hosting dashboard.
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
Recommended workflow
Install the PreviewShip extension in Cursor using `ext install previewship.previewship`.
Run “PreviewShip: Set API Key” and paste your key.
Open the project workspace you want to share.
Run “PreviewShip: Deploy Workspace, HTML, Markdown, or PDF File” and copy the preview URL.
Why editor-native deploys convert better than dashboard-only flows
For fast iteration, every context switch adds friction. A deploy path inside the editor feels closer to “save and share” than “prepare and publish.”
That is especially helpful for freelancers, solo builders, and small teams who review changes frequently with non-technical stakeholders.
Cursor plus PreviewShip
Cursor already sits close to the coding loop. PreviewShip extends that loop to live review by making the current workspace deployable from the same interface.
In practical terms, that means you can update a layout, build the project, and generate a share link without leaving the editor. For one .html, Markdown, or PDF file, use the active-file deploy command directly.
FAQ
Does Cursor need a separate PreviewShip build step?
No separate dashboard step is required. After the extension is installed and authenticated, deploy runs from the editor.
Can I still use CLI with Cursor?
Yes. The extension is convenient for interactive use, while the CLI remains useful for scripts and automated flows.
Can Cursor deploy a source-code zip?
PreviewShip expects static artifacts, not raw source zips. Build first and deploy dist/build/out, or deploy a single .html, Markdown, or PDF file directly.
Is Cursor support different from VS Code support?
The extension setup is nearly identical because Cursor is compatible with VS Code extensions.