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 file directly.

Is Cursor support different from VS Code support?

The extension setup is nearly identical because Cursor is compatible with VS Code extensions.

Docs / Cursor

Deploy a preview directly from Cursor

Install the PreviewShip extension in Cursor, set your API key, and deploy a built workspace output or active HTML file to a shareable preview URL.

Updated 2026-04-17

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 file. It removes the need to zip files manually or switch to a separate hosting dashboard.

Key takeaways

Best for developers iterating inside Cursor who want one-click sharing.
Works well with both human-driven and AI-assisted editing sessions.
Pairs naturally with MCP when you also want agents to trigger deploys.

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 or HTML 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 ask the agent to update a layout, build the project, inspect the result locally, and generate a share link without leaving the editor. For a single generated .html file, use the active HTML 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 file directly.
Is Cursor support different from VS Code support?: The extension setup is nearly identical because Cursor is compatible with VS Code extensions.