Publish the intended version
Use Preview inside Figma to inspect the work, then publish the version intended for review to its figma.site address or connected custom domain.
Paste the published figma.site or connected custom-domain URL, send one review link, and collect contextual comments on the visitor-facing website.












Loved by1,250+Agenciesand companies in 100+ countries
Figma separates the editable Sites file, inline Preview, published website, domain settings, audience selection and password protection.
Four documented boundaries matter before review:
Figma Sites is in open beta. Publishing is available on paid plans; the Education plan includes one published site and may have bandwidth limits.
Figma documents Preview as an inline way to check animations, interactions and responsive behavior without publishing. Publishing is the separate step that puts the site on the web.
After publishing, Figma assigns a random figma.site subdomain. A site can later use a connected custom domain, subject to the documented domain settings.
Organization and Enterprise plans can restrict publishing to an internal audience, and paid plans can password protect a published site or individual pages. A pasted URL does not bypass those controls.
How it works
Use Preview inside Figma to inspect the work, then publish the version intended for review to its figma.site address or connected custom domain.
Paste the accessible published page URL into BugSmash and share the generated review link with stakeholders.
Apply revisions in Figma, publish an update, and verify the live page; canvas changes do not appear on the published site until they are published.
Attach each note to the rendered page location rather than translating it into a separate feedback list.
Review the assigned figma.site address or the one connected custom domain documented for the site.
Review desktop, tablet and mobile presentation while retaining the viewport with each comment.
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
A public published URL does not require giving every reviewer edit access to the underlying Figma Sites file.
Internal-audience and password requirements remain Figma-controlled gates for the published website.
Use an accessible published figma.site URL or connected custom domain. Inline Preview and the editable Figma file are separate surfaces, and a pasted URL does not bypass passwords or internal-audience access.
| Your URL | Review by URL | What to do |
|---|---|---|
| Published figma.site visitor URL | Works | Paste the published page URL shown in Figma and begin review. |
| Connected Figma Sites custom domain | Works when connected | Use the live custom domain after Figma reports it connected. |
| Inline Figma Sites Preview | Pre-publish check only | Use Preview inside Figma, then publish the intended version for website URL review. |
| Internal-audience published site | Organization sign-in required | Figma limits this surface to logged-in organization members. A Website-project URL does not grant organization access. |
| Password-protected published site or page | Password required | The Figma password remains required. A Website-project review URL does not remove it. |
| Unpublished Figma Sites file | Not on the public web | Publish the intended version before reviewing its visitor-facing website URL. |
If the rendered site includes the BugSmash Feedback Widget, reviewers can leave feedback within that page after Figma grants the required access. Figma remains responsible for passwords and audience rules.
Move from inline checks to published-site sign-off while keeping designers, marketers and QA aligned on the same visitor-facing page.

Collect page-specific feedback on the published website while editing and publishing remain in Figma.
See how
Review the visitor-facing URL without receiving edit access to the Figma Sites file.
See how
Verify responsive output, domains and access states with reproducible 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 website beside campaign images, PDFs, videos and presentations, 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.

Use the published figma.site visitor URL or the connected custom domain. Inline Preview is a pre-publication surface inside Figma, not the published website.
Paste an accessible published figma.site or custom-domain URL and send a focused review link.
