How to share a Windsurf project with a client

Build the static output from your Windsurf project, share one controlled review link, and feed client comments into the next Windsurf session.

From build to client review

  1. 1

    Run the production build

    Ask the editor to run the project's tests and its documented production build, then read the diff yourself.

  2. 2

    Check the static output

    Locate the output directory, confirm index.html exists and open the built files in a clean browser.

  3. 3

    Create the review project

    Zip the contents of the output directory and upload them. Add a project password when the preview should be limited to people who have it.

  4. 4

    Ask for pinned feedback

    Send the link with a deadline and ask the client to comment on the exact elements they want changed. No account or extension is needed.

  5. 5

    Build the next round

    Turn open comments into one structured prompt for the next Windsurf session and upload the new build to the same project.

Common questions

Can I upload my Windsurf source folder?

Upload the built static output, not source that still needs a bundler or dev server. The archive needs an index.html.

Can clients comment without installing anything?

Yes. Reviewers identify themselves with a display name and need no account.

Does the client link change between revisions?

No. Each upload goes into the same project, so the URL stays stable. Comments stay with their version, and older versions are pruned by your plan's version limit.