Framer Client Feedback: How Freelancers Collect Comments on a Framer Site Without the Chaos

The fastest way to collect client feedback on a Framer site is to share the published URL with a visual overlay that lets the client click anywhere and leave a pinned comment, no login required. Framer's built-in comments only work for paid editors inside the Framer workspace, so they don't help when the client just needs to review the live site. For freelancers, the practical answer is a separate visual feedback layer that sits on top of the published URL.

If you've ever shipped a Framer site and then waited five days for the client to come back with twelve loose screenshots, three voice notes, and an email starting with "small thing but…", you already know the problem. Framer is brilliant at letting you design and publish a site fast. It's not built to handle the messy, asynchronous, picky review cycles that freelance projects actually run through. This guide shows how to fix that without forcing the client to sign up for anything.

The real problem with Framer client feedback

Framer is design-first. The editor is built for designers; the workspace is built for teams of designers. The client is neither.

You will hit the same pattern again and again:

• You finish the site and publish to a .framer.website URL or a custom domain.
• You send the link to the client over Slack, email, or WhatsApp.
• The client opens it on their phone, screenshots three things, and sends them back with arrows drawn in the iPhone photo editor.
• Two days later they email a "few quick fixes" with vague references like "the hero section feels off."
• You spend forty minutes guessing which section "the second one" means, which breakpoint they were on, and what browser they used.

Framer's own commenting feature does exist, but it lives in the editor. It requires the reviewer to log into a Framer account, be invited as a workspace member, and use the canvas. Most clients won't do any of that. Some can't, because Framer's seats cost money you don't want to spend on a one-shot reviewer.

The honest summary: Framer ships a great product but leaves the client review layer to you.

How freelancers actually collect Framer feedback (compared)

Here is how the common methods stack up for a typical freelance review cycle.

Method  ·  Setup time  ·  Pinned to UI?  ·  Client login?  ·  Captures browser/device?  ·  Cost

Framer comments  ·  10–20 min per client  ·  Yes (canvas)  ·  Yes (seat needed)  ·  No  ·  per seat

Email + screenshots  ·  None  ·  No  ·  No  ·  No  ·  Free

Slack/WhatsApp  ·  None  ·  No  ·  No  ·  No  ·  Free

Loom video walkthrough  ·  5 min per round  ·  No  ·  No  ·  No  ·  Free–paid

Google Doc list  ·  2 min  ·  No  ·  No  ·  No  ·  Free

Visual feedback overlay (e.g. dotts)  ·  1 min to share link  ·  Yes (on live site)  ·  No  ·  Yes  ·  Free–one-time

Two things are worth pulling out of that table.

First, only two methods actually pin feedback to a specific place on the live site: Framer's native commenting and a feedback overlay. Everything else degenerates into a list of vague references that you then have to translate.

Second, only one of those two methods doesn't require the client to log in or buy a seat. That's the entire reason "share a feedback link" workflows exist.

What "share a link and let them click" actually looks like

If you've never used a dedicated visual feedback tool on a published Framer site, the workflow is simpler than you'd expect:

1. You publish the Framer site to its URL as usual.
2. You generate a feedback link in the overlay tool, pointing at that URL.
3. You send the link to the client. They open it in any browser, on any device.
4. They click any element on the page and type a comment. The comment gets pinned to that exact element, at that breakpoint, with their browser and device info auto-attached.
5. You see the pins in your dashboard, resolve them as you fix, and reply if anything's unclear.

There is no account creation, no plugin, no Framer seat. The client just clicks and types. That's the entire feature.

For a freelancer this changes the math on revisions. Instead of five rounds of email back and forth, plus a thirty-minute call to clarify what they meant by "the gap," you get a list of pinned items that resolve themselves down to a clear to-do list.

Three things to set up before you share the link

It's tempting to just send the URL and hope. Don't. A small amount of setup makes the difference between a clean review and another mess.

1. Lock in the version

Framer auto-publishes when you click Publish, which is great until you push a fix mid-review and the client suddenly sees something different than what they were commenting on. Before you send the feedback link, decide if you're sharing the live production URL or a staging/preview URL, and tell the client which it is. If you're iterating in parallel, share a staging URL and only push to production once the round is signed off.

2. Give them a structure

Most clients will leave generic comments like "nice" or "can we change this?" if you don't ask for anything specific. In your intro message, tell them what you want feedback on, and what you don't. For example: "Please flag anything off about the copy, spacing, or imagery. Don't worry about animations yet — those are coming in round two."

This single sentence cuts review time roughly in half. It also avoids the painful conversation where the client wants to redesign the navigation in round three.

3. Set a deadline

Open-ended review windows kill freelance projects. Put a clear date on it: "Feedback by Thursday EOD please, otherwise we ship as-is." It feels uncomfortable the first time you write it. It will save you weeks across the year.

What about Framer's own comments?

Framer's built-in comments are good for teammates. They live on the canvas, threaded by selected element, and they're great when you're working with another designer in the same workspace.

For client review they have three problems:

1. Account requirement. The client has to create or log into a Framer account, accept an invite, and be added to the workspace. Most clients won't do this. Some can't, due to internal policy.
2. Seat cost. Adding a reviewer to a paid workspace usually means another seat. For a single-project freelancer, that's a hard sell.
3. Canvas, not site. Comments are on the design surface, not the published site. The client comments on the version you're building, not the version they're reviewing. Out of date the moment you publish.

If you're working with another designer or developer who actually needs to be in the Framer editor, use Framer comments. If you're handing the site to a client for review, use a separate feedback layer on the published URL.

What clients actually care about during review

You're going to hear a lot of "this looks great, just a few small things." That sentence is doing a lot of work. Underneath it the client is usually checking:

• Does my logo look right at the top? Is it the new version?
• Is the headline saying what I want it to say?
• Do the images match what we agreed in the brief?
• Does this look okay on my phone? (They will check this.)
• Can I find the contact form, pricing, or signup quickly?
• Is anything still labelled "placeholder" or "lorem ipsum"?

If your review tool pins comments to the actual element, on the actual device, you cover all of these in one round. If it doesn't, you'll spend round two cleaning up things you could have caught in round one.

A real example

Jana is a freelance designer based in Hamburg. She builds for small B2B clients, mostly in Framer. Her old workflow with a SaaS client looked like this.

She'd publish the staging site, paste the URL into an email, and write "let me know what you think." The client would reply two days later with a list like: "1. Logo a bit big? 2. The blue feels off. 3. Section three should be section two? 4. Footer." Jana would spend half an hour translating this into actual changes, often guessing wrong on one of them and re-doing it.

She switched to sharing a feedback link the client could click on. Same staging URL, but now with a pin overlay. Same client, same review week. The feedback came back as nine pinned comments, each on the exact element, with the browser and device captured automatically. She fixed all of them in an afternoon, hit the staging link with a "round two ready" note, and the client signed off the next day.

The work didn't get easier. The review cycle got shorter, because the friction went down to zero on the client's side.

Bottom line

Framer's built-in commenting is for the editor. For client review on a published Framer site, give the client a no-login, pinned feedback experience on the live URL. You'll cut revision rounds, kill the screenshot email, and finish projects faster.

FAQ

Does Framer have a built-in feedback tool for clients?

Framer has a comments feature, but it lives inside the editor and requires the reviewer to log into the Framer workspace as a member. It's built for collaborating designers, not external client review. For a client reviewing a published Framer site, you'll need a separate visual feedback layer like dotts that sits on top of the live URL and doesn't require the client to sign up.

How do I let a client leave comments on a Framer site without giving them editor access?

Share a feedback link that points at your published Framer URL. The client opens it in a browser, clicks anywhere on the page, and types a comment. The comment is pinned to that element with browser and device info captured automatically. No Framer account, no seat needed, no editor access.

What's the best framer website feedback tool for freelancers?

The right framer website feedback tool depends on your workflow, but for solo freelancers the priorities are usually clear: no client login, pinned comments on the live site, automatic browser and device capture, and a flat price instead of per-seat. Tools built for agencies tend to be priced and structured for teams; tools built for freelancers like dotts optimize for the single-project review cycle.

Can I use Framer comments for client review?

Technically yes, practically no. Framer comments are on the canvas inside the editor and require the reviewer to be invited as a workspace member. Most clients won't go through that, and adding them often costs a seat. Use Framer comments for collaborators; use a separate feedback overlay for clients.

Will a visual feedback tool slow down my Framer site?

A good visual feedback overlay only loads in the review session, not for end users on the live site. Your published Framer site stays fast for visitors and the feedback layer only appears when someone opens the dedicated review URL. Check the tool's documentation to make sure that's how it works before you wire it into production.

How do I keep client feedback organised across multiple review rounds?

Treat each round as its own list. Resolve all pinned comments from round one before opening round two, and only share the new staging link once round one is closed. This keeps the client focused on one batch at a time and stops the review from becoming an endless drip of small requests. Tools that let you mark comments as resolved make this much easier than a Google Doc.

What's the difference between Framer comments and dotts?

Framer comments live in the editor and require a workspace seat. They're built for designers collaborating on the canvas. dotts lives on the published URL, requires no client login, captures browser and device data automatically, and is built specifically for the freelancer–client review cycle. Different jobs.

How long should I give a client to leave feedback on a Framer site?

Three to five working days is a reasonable default for a single review round on a small project. Anything shorter feels rushed; anything longer and the project loses momentum. State the deadline clearly in your share message and treat silence past the deadline as approval, but only if you put that in writing first.

Stop chasing screenshot emails. [Try dotts free →](https://dotts.se)