Works with · Figma Sites
Figma Sites · Website builder
Client feedback on Figma Sites
Built the site in Figma Sites? Review the published version with clients who don't use Figma. They comment on the live page, with separate notes for each screen size.
Free for 3 projects. Reviewers never need an account.
Why Figma Sites teams use HTMLAnnotate
Figma Sites lets designers publish straight from the canvas, which shortens the path from mockup to live page. Feedback still has a gap. Figma comments are excellent for designers and teammates, but commenting needs a Figma account, and the site preview follows the file's sharing permissions. Clients and stakeholders who don't use Figma either need access to your file or end up sending their notes another way.
Those other ways are familiar: screenshots of the published site, a Loom walk-through, an email with a numbered list. None of them point at the element, and none say which breakpoint the client was looking at. Figma Sites lays out each breakpoint separately, so "the image is too big" means something different on desktop and mobile. Without that context you guess, then guess again.
With HTMLAnnotate you publish to your figma.site address or custom domain, paste the link and send it. Clients use the real site in a normal browser, with interactions running, and click the exact heading, image or button. Comments stay in the Desktop, Tablet or Mobile view they were made in, which lines up with your breakpoints, and your design file stays free of client notes.
How it works with Figma Sites
Three steps, about a minute.
Publish the site
Publish to your figma.site address or a connected custom domain. Publishing needs a paid Figma plan. If a site password is set, remove it for the review round.
Paste it in
Paste the published URL into HTMLAnnotate and get a review link back. Reviewers can move between the site's pages from that one link.
Share with clients
Send the review link. Clients give a name and email once, then comment on the live site without a Figma account or file access.
A full review round, start to finish
What a typical round looks like on Figma Sites.
Set up your breakpoints
New Figma Sites webpages start with Desktop and Mobile breakpoints, and you can add more. If you've added a Tablet breakpoint, ask reviewers to check all three views in HTMLAnnotate so every layout you designed gets looked at.
Publish the version to review
Publish from Figma Sites and use the published URL rather than the preview, which shows a Figma header and follows file sharing permissions. If the site has a password, remove it in site settings for the length of the round.
Create and send the link
Paste the URL into HTMLAnnotate and share the review link. Sign in first so the link lasts up to 14 days on Free, or forever on Pro, which suits client rounds that stretch over a few weeks.
Collect notes per view
Clients browse first so scroll effects and interactions play, then switch to Comment mode. Notes made in Mobile stay in Mobile, so you know to fix the mobile breakpoint rather than the desktop layout, and nothing gets applied to the wrong frame.
Make changes in Figma
Work through the list in your Sites file. Edits to the primary breakpoint cascade to the others, so check comments in every view after a desktop change. Republish, and the review link loads the fresh site the next time it opens.
Sign off and close
Ask the client to press Approve when the site is right. Export a CSV for the project record, switch comments off on the link, and add the site password back in site settings if you use one.
Figma's own tools and HTMLAnnotate
Use both. Here is what each is good at.
| What you need | Figma Sites | HTMLAnnotate |
|---|---|---|
| Client feedback without Figma | Comments need a Figma account | Name and email, no account |
| Where comments live | In the Figma file | On the published site |
| Notes per screen size | Comments on breakpoint frames in the canvas | Separate Desktop, Tablet and Mobile views |
| Restricting access | Site password in site settings | Remove it while reviewing |
| Formal sign-off | Not available | Approve button with an approval count |
| Handing fixes over | Comments stay in the file | Copy for AI and CSV export |
What works
- Feedback on the real, published page rather than the canvas
- Desktop, Tablet and Mobile comments that line up with breakpoints
- No Figma seats or file access for clients
- Scroll effects and interactions keep running during review
- Your design file stays free of client comments
- Copy for AI for the next round
Good to know
- Only the published site can be reviewed. The canvas and the preview, which follows file sharing permissions, can't be imported.
- A site password asks visitors for it before showing anything. Remove it during review, since sign-in pages can't be imported yet.
- Publishing needs a paid Figma plan, so a site in a free Starter plan file can't be shared for review.
- Forms on the reviewed copy can't be submitted.
Tips for better Figma Sites reviews
Match breakpoints to views
Figma Sites starts each page with Desktop and Mobile breakpoints, and Figma suggests most sites need no more than desktop, tablet and mobile. Add a Tablet breakpoint if you expect tablet notes, so each HTMLAnnotate view has a matching layout.
Review published, not preview
The preview carries a Figma header and uses file permissions. Send the published figma.site address instead, so clients see exactly what visitors will see and don't need a Figma login.
Watch the cascade
Changes to the primary breakpoint flow down to the other breakpoints. After fixing a desktop comment, open the Tablet and Mobile views in the review link to check that nothing shifted.
Keep the file clean
Leave Figma comments for your design team and send client feedback through the review link. When the round closes, Copy for AI gives you one brief to work from instead of scattered pins.
Questions about Figma Sites
Isn't Figma commenting enough?
For your design team it often is. Figma comments need a Figma account and sit in the file. HTMLAnnotate lets clients without Figma comment on the published site in a normal browser, with notes split by screen size.
Do clients need Figma?
No. They open the review link and give a name and email once per browser. They don't need a seat, access to your file or a Figma login of any kind.
Does it work on a custom domain?
Yes. Paste whichever address the site is published on, your figma.site address or a connected custom domain. Reviewers can move between the site's pages from the same link.
Can I review a password-protected Figma Site?
Not while the password is on. Remove it in site settings for the review round and add it back afterwards. Figma applies password changes on save, without republishing.
Can I review the site before publishing?
Not with HTMLAnnotate. The preview follows Figma file sharing permissions, so it needs a Figma login. Publish the site, even just to the figma.site address, to get a link reviewers can open.
Will interactions and animations work?
Yes. Imported sites run with their own scripts, so scroll effects, hover states and interactions behave as they do on the published site. Reviewers use Browse mode to try them and Comment mode to leave notes.
Other website builders
HTMLAnnotate works with any page anyone can open in a browser.
Webflow
Framer
WordPress
Shopify
Squarespace
Wix
Ghost