Does Framer have a built-in way to collect client feedback?

Framer has collaboration features inside the editor — team members can comment on frames in the canvas view. But there's no built-in tool that lets an external client (who isn't in your Framer workspace) open the published site and leave a pinned comment on an element. For client review, you need something external: a review tool, a screen share, or a structured form.

How do I share a Framer site for review without giving the client editor access?

Publish the site and share the published URL — the .framer.app link or your custom domain. The published site opens in any browser with no Framer account required. The Framer editor link (framer.com/projects/…) requires an account to access, so don't send that one to clients.

Why do feedback tools break Framer animations?

Most website feedback tools use a proxy: they fetch your site through their own server and re-serve a copy to the reviewer. Framer's custom scroll effects, WebGL, and Framer Motion animations depend on the original runtime environment — when served through a proxy, the scripts often fail to load correctly and interactions stop working. Your client ends up reviewing a static-feeling version of a site that's supposed to feel alive. If this is a concern, test the tool yourself on your published URL before sending it to a client.

Can my client comment on my Framer site without creating an account?

Not natively inside Framer. If you use a third-party review tool on top of the published URL, look for one that supports guest commenting — the client opens the link in their browser and can leave notes without signing up. Most modern review tools offer this; check whether the guest flow requires an email address or truly has zero friction.

How do I collect feedback on a password-protected Framer staging site?

Framer's paid-plan staging URLs (.framer.app) can be password-protected. Proxy-based review tools typically can't access these because they can't pass through the password screen. Your options: remove the staging password temporarily while collecting feedback, use a screen share instead of a review link, or use a tool that can handle authenticated pages. Alternatively, publish to your custom domain (which can be done without a staging password) for the review period.

What's the best way to get specific, actionable feedback on a Framer site?

Two things make feedback specific: the right prompt and the right tool. For the prompt: ask about one section at a time with a concrete question, not "any thoughts?". For the tool: give clients a way to pin a note to the exact element they mean — element-anchored comments are unambiguous in a way that email descriptions aren't. "This hero button" pinned to the button beats "the button near the top" in a Slack message.

drafty

How to get feedback on a Framer site

Quick answer

To get feedback on a Framer site, share the published URL — not the editor link — then give your client a way to leave specific, located notes rather than a wall of text in email. Framer has no built-in guest comment layer for external reviewers, so you need something on top: a review tool, a screen share, or structured questions. The most common mistake is sending the raw Framer URL and asking "what do you think?" — you get back "looks good overall" and one vague point about the hero.

Step 1

Publish the site first — share the live URL, not the editor link

Framer has two shareable states: the editor (framer.com/projects/…) and the published site (yoursite.framer.app or your custom domain). Your client cannot leave useful feedback inside the Framer editor — they need to see the live, rendered version. Click Publish in the top-right corner of Framer, then share the published URL. If you're on a free plan, this lands on a .framer.app subdomain. If you've connected a custom domain, use that — it's cleaner to send a client and removes any "what is framer.app?" confusion. One gotcha: Framer's staging URLs (the .framer.app ones on paid plans) can be password-protected. If you've set a staging password, share it alongside the link or clients hit a login wall and email you to ask why the link doesn't work.

Step 2

Wrap the URL in a review tool that doesn't break your animations

The fastest way to get pinned, specific feedback: paste your published Framer URL into a review tool that wraps it with a comment layer. Your client opens the same live site — interactions firing, scroll effects working — and clicks any element to leave a note right there. One important detail if you're evaluating tools: most feedback tools are proxy-based. They fetch your Framer site through their own server before serving it to the client. Framer's custom animations, WebGL, and motion APIs often break through a proxy — your client ends up reviewing a static shell where nothing moves, which is misleading feedback on a site whose animations are half the point. Look for tools that operate on the live URL directly rather than re-serving a copy. If a tool's free plan covers your current project, test it yourself before sending it to a client: open the link, scroll through, trigger your interactions, and confirm they still fire.

Step 3

Run a 20-minute screen share for flow and first-impression feedback

Async comments catch specific UI issues; a live session catches whether the site makes sense at all. Book a 20-minute call with your client, open the published Framer site, and ask them to narrate out loud as they click through it. The thing most designers don't do: stay quiet. Don't explain what you built before they react to it. Say "take a look and tell me what you notice" — then listen. Their first 60 seconds of narration will surface confusion you never thought to ask about. Take notes during the call rather than trusting memory. A screen share is especially useful for Framer sites with complex interactions or micro-animations — the client sees them in context rather than reviewing a frozen screenshot. For clients who can't make a call, ask them to record a Loom of themselves clicking through the site.

Step 4

Send structured questions per section, not an open prompt

"Any feedback on the site?" gets you "looks great!" and one vague request. Instead, walk your client through each section with a concrete question: "On the homepage hero: is it immediately clear what we do?" / "On the pricing section: does the tier structure make sense?" / "On the contact form: is anything missing or confusing?" Six to eight questions, each tied to a specific part of the site. Embed a screenshot of each section in your email or doc so the client knows exactly what you're asking about — don't rely on them scrolling back to the right spot. If you can share the published URL alongside the questions, tell them to open it in a separate tab and refer to it while answering. This method works for clients who won't use a review tool but will answer a structured form. It doesn't give you anchored comments — you'll still be mapping their answers back to sections manually — but it's far more useful than an open request.

The faster way

If your client keeps describing things as "the section with the image on the left" or sends a three-paragraph email about one button — paste your published Framer URL into Drafty and send them the review link. They open the live site in their browser, click the exact element they mean, and leave a note pinned right there. No account, no install, no extension. Every comment threads by element so you see "this CTA" as a specific pinned note, not a vague description to decode. Works on any public Framer URL — custom domain or .framer.app.

Open a live demo

Questions

Does Framer have a built-in way to collect client feedback?: Framer has collaboration features inside the editor — team members can comment on frames in the canvas view. But there's no built-in tool that lets an external client (who isn't in your Framer workspace) open the published site and leave a pinned comment on an element. For client review, you need something external: a review tool, a screen share, or a structured form.
How do I share a Framer site for review without giving the client editor access?: Publish the site and share the published URL — the .framer.app link or your custom domain. The published site opens in any browser with no Framer account required. The Framer editor link (framer.com/projects/…) requires an account to access, so don't send that one to clients.
Why do feedback tools break Framer animations?: Most website feedback tools use a proxy: they fetch your site through their own server and re-serve a copy to the reviewer. Framer's custom scroll effects, WebGL, and Framer Motion animations depend on the original runtime environment — when served through a proxy, the scripts often fail to load correctly and interactions stop working. Your client ends up reviewing a static-feeling version of a site that's supposed to feel alive. If this is a concern, test the tool yourself on your published URL before sending it to a client.
Can my client comment on my Framer site without creating an account?: Not natively inside Framer. If you use a third-party review tool on top of the published URL, look for one that supports guest commenting — the client opens the link in their browser and can leave notes without signing up. Most modern review tools offer this; check whether the guest flow requires an email address or truly has zero friction.
How do I collect feedback on a password-protected Framer staging site?: Framer's paid-plan staging URLs (.framer.app) can be password-protected. Proxy-based review tools typically can't access these because they can't pass through the password screen. Your options: remove the staging password temporarily while collecting feedback, use a screen share instead of a review link, or use a tool that can handle authenticated pages. Alternatively, publish to your custom domain (which can be done without a staging password) for the review period.
What's the best way to get specific, actionable feedback on a Framer site?: Two things make feedback specific: the right prompt and the right tool. For the prompt: ask about one section at a time with a concrete question, not "any thoughts?". For the tool: give clients a way to pin a note to the exact element they mean — element-anchored comments are unambiguous in a way that email descriptions aren't. "This hero button" pinned to the button beats "the button near the top" in a Slack message.

Keep exploring

How to get feedback on a website How to get feedback on a landing page Design feedback tool BugHerd alternative

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo