Prepare the frontend URL
Deploy the Craft frontend to an accessible environment, or use Craft Team or Pro to create a tokenized URL for the entry and Preview Target under review.
Paste the deployed frontend or, with Craft Team or Pro, a valid tokenized Preview Target URL, send one review link, and collect contextual comments on the rendered experience.












Loved by1,250+Agenciesand companies in 100+ countries
Craft drafts power Live Preview, while Craft Team and Pro support tokenized URLs through Preview Targets. Deployment remains part of the project’s hosting workflow.
Four documented boundaries matter before client review:
Craft splits the screen between a simplified editor and the frontend preview, refreshing it when the provisional draft is auto-saved.
In Craft Team and Pro, a tokenized Preview Target URL can be opened by someone without a Craft account, but it reflects the draft state when accessed and does not auto-refresh like Live Preview.
Craft says shared preview tokens expire after one day by default. The defaultTokenDuration setting controls that duration.
A decoupled frontend must detect the token parameter and pass the same token with the content request so Craft can return the previewed content.
How it works
Deploy the Craft frontend to an accessible environment, or use Craft Team or Pro to create a tokenized URL for the entry and Preview Target under review.
Paste the deployed or preview URL into BugSmash and share the generated link with the client or QA team.
Update the Craft draft or project, publish the content, complete the deployment, and verify the resulting browser URL.
Attach feedback to the page location rather than describing an entry or template in a separate message.
With Craft Team or Pro, use a valid Preview Target URL when a stakeholder needs to see unpublished entry content.
Review the deployed Vue, React or other frontend after it has been configured to request the correct Craft content.
Review desktop, tablet and mobile presentation and retain the viewport with every comment.
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
External reviewers can use an accessible frontend or, with Craft Team or Pro, a tokenized Preview Target URL without receiving a Craft control-panel account.
Use the rendered frontend or, with Craft Team or Pro, a valid Preview Target URL. Craft control-panel permissions, token lifetime and frontend access rules continue to apply.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public Craft CMS frontend | Works | Paste the public page URL and start the review. |
| Accessible staging frontend | Works | Use the staging URL after confirming every reviewer can open it. |
| Tokenized Craft Preview Target URL (Team or Pro) | Works until expiry | Share the URL while its temporary preview token remains valid. |
| Decoupled frontend preview | Configuration-dependent | Confirm the frontend forwards Craft’s token when it requests preview content. |
| Craft Live Preview in the control panel | Editor access required | For Craft Team or Pro, use a tokenized Preview Target URL for external review instead of sharing the control-panel interface. |
| Protected or authenticated frontend | Access-dependent | Authenticate in the review session or use the Feedback Widget. A pasted URL does not bypass the frontend gate. |
Add the BugSmash Feedback Widget to the rendered frontend when review must remain inside an authenticated or stateful experience. Install it in the frontend visitors actually open, including a decoupled application.
Keep Drafts and Live Preview with editors while clients, designers and QA review the browser output produced by the project.

Share the deployed frontend or, with Craft Team or Pro, a tokenized Preview Target URL while keeping project code and control-panel access within the delivery team.
See how
Use Craft drafts and Live Preview for authoring, then collect stakeholder comments on the relevant frontend state.
See how
Review templates, responsive presentation and decoupled frontends with technical browser context attached.
See howRoute an actionable website comment with its page URL, selected location, screenshot, browser, operating system and viewport context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the frontend beside content PDFs, images, videos, presentations and release materials, with feedback and approval in one project.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

Send the deployed frontend URL. With Craft Team or Pro, you can use a Preview Target URL containing Craft’s temporary preview token for unpublished entry content.
Paste an accessible Craft frontend or valid preview URL and send a focused review link.
