Webflow news
Webflow comments: when they can replace a markup tool
Direct links, emoji reactions, @mentions and an API: what Webflow comments have offered since 2025 and when they can replace a markup tool like Markup.io.
By Christian Schmitt
2 min readKey takeawaysThe main points and every section to jump to.Show or hide the summary
- 01
Since 2025, Webflow comments have direct links, emoji reactions, clickable links, @mentions and an API.
- 02
Comments work on CMS content, which helps content teams.
- 03
The API sends comments to Slack, Asana or other tools via Zapier or Make.
- 04
Markup tools still lead on visual markers, guest feedback on live sites and bug reports with browser details.
- 05
If the project lives in Webflow and the reviewers have access, Webflow comments are usually enough.
Feedback is at the heart of every website project. Yet many teams still switch to a separate markup tool such as Markup.io, Marker.io or BugHerd to collect it. Since the updates in April and May 2025, Webflow’s own comments cover a lot of that ground.
What Webflow comments can do since 2025
- Direct links to comments. Share a specific comment with your team instead of describing where it is.
- Emoji reactions. A quick 👍 or ❓ instead of another reply.
- Clickable links in comments. Point to assets, tickets or documentation.
- Copying comment text. Reuse feedback in a ticket or a brief.
- Comments on CMS content. Feedback directly on blog posts and other dynamic content.
- @mentions. Tag the person who should act on a comment.
- A comments API. Connect comments to Slack, Asana or other tools via Zapier or Make.
A typical flow: an editor leaves a comment on a CMS item and mentions the developer. Through the API, the comment lands in Slack, and the developer jumps to it with the direct link.
What markup tools do differently
Markup tools let people annotate a live website or a design with pins, arrows or boxes. Depending on the tool, they add bug reports with browser and screen size, integrations with Jira and similar trackers, and guest access through a link, without an account.
When Webflow comments are enough
- The whole project lives in Webflow, and the people giving feedback have access to it.
- Most feedback is about content and layout, not browser-specific bugs.
- You want feedback in the same place as the work, without another subscription.
When a dedicated tool still fits better
- Clients or stakeholders should comment without a Webflow seat.
- You need screenshots with browser, device and screen size attached to every comment.
- The site isn’t built in Webflow, or the fixes happen in code.
For that last case, I built Margin: clients pin comments to an element through a personal link, and coding agents like Claude Code read the comment, element and screenshot via MCP.
Conclusion
Webflow comments are no longer a side feature. For teams that review inside Webflow, they often replace a separate markup tool. Try them on your next project before you add another subscription, and switch to a dedicated tool only where they fall short.
Questions
Reviewers need access to the Webflow project, for example as reviewers in the workspace. Check your workspace plan for how many reviewer seats it includes. Markup tools usually let guests comment on the live site through a link, without an account.
For teams that review inside Webflow, often yes. If you need visual markers, feedback from people without Webflow access or bug reports with browser and screen details, a dedicated tool still fits better.
It lets you read comment threads from outside Webflow, for example to post new comments to Slack or create tasks in Asana through Zapier or Make.
