LocalFeedback | Visual Client Feedback with Screenshots
Visual, in-context feedback for WordPress. Pin, highlight and box annotations stored entirely in your own database.
Solid choice
LocalFeedback is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 73/100 on our health check.
- Actively developed — last update 2 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (10+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where LocalFeedback stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| annotation | #35 |
| client feedback | #21 |
| comments | >100 |
| feedback | >100 |
| staging | >100 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About LocalFeedback
From the official readme · v1.10.1Description
LocalFeedback is a self-hosted feedback and annotation tool for the build and review phase of a WordPress project. Your team and your clients leave comments directly on the page — a pin on a spot, a highlight on a piece of text, or a box around an area — and every one of them is stored in this site’s own database table.
There is no connected hub site, no cross-site sync and no external service. That is the whole point: comments cannot fail to save because a remote dashboard was unreachable.
Core features
- Pin, text highlight, box and general comment types
- Annotation tools right beside the Feedback button, so commenting never needs the panel open
- Right-click anywhere to drop a pin, or right-click selected text to comment on it
- A panel that sits beside the page instead of over it, on either side, at whatever width you drag it to
- Threaded replies on any comment
- Best-effort automatic screenshot of the annotated area
- Device type and exact viewport width recorded with every comment
- Status workflow (open / in progress / resolved), priority, tags and category
- Tags picked from a dropdown you control, with an optional “Other…” for one-offs
- Teams, including internal-only visibility, an optional join password, and one-click review links for clients
- Three site modes: development, live client review on chosen pages, and live feedback from anyone that only moderators can read
- A site-wide review link that hides the toolbar from everyone else, so feedback can be gathered on a site that is already public
- Password-protected pages respected: nothing shows until the password is entered
- Per-page control from the editor sidebar, or by listing pages, directories and wildcards in settings
- A screenshot library with the same filters as the feedback list, plus a one-click purge when a project wraps
- Guest commenting by default, or restrict to logged-in WordPress users
- A short welcome popup that shows first-time reviewers how to use the tools
- Optional follow-up emails so commenters hear about replies and status changes, with one-click unsubscribe
- A shareable link for every comment that opens the page and highlights the annotation
- Filterable, sortable admin table with customisable columns and CSV export
- One click from any page — its admin bar, its editor, or the Pages list — to just that page’s feedback in the dashboard
- Instant email notifications and an optional daily digest
- Documentation built into the plugin
Built for reliable saving
- The comment box never clears until the server confirms the save
- Failed saves retry automatically with a growing delay
- Unsent text is kept in the browser, so a reload does not lose it
- Every save carries a unique key, so a retry can never create a duplicate
- If the REST API is blocked, the same request is retried through admin-ajax.php
License
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
Installation
Requires WordPress 6.2 or newer.
- Upload the
localfeedbackfolder to/wp-content/plugins/, or install the ZIP through Plugins → Add New. - Activate the plugin.
- Visit LocalFeedback → Settings to choose who can leave feedback.
- Open any page on the front end and use the Feedback button in the bottom right corner.
Frequently asked questions
Does any data leave my site?
No. Feedback, screenshots and settings are stored in this WordPress installation. The only outbound messages are the notification emails you switch on, sent through your own server. The “Ideas & bug reports” menu item simply opens a form in your browser; the plugin itself sends nothing.
Can people leave feedback without a WordPress account?
Yes, that is the default. You can require a WordPress login instead in Settings.
Where are screenshots stored?
In wp-content/uploads/localfeedback, with random filenames, deliberately outside your media library so review captures never mix in with your real content. Capture happens entirely in the visitor’s browser and is best effort — cross-origin images, embedded media and strict content security policies can prevent it. The comment is always saved either way. LocalFeedback → Screenshots shows everything stored and can delete it all in one go.
Can I share a screenshot outside WordPress?
Yes. Every screenshot has a direct URL with a long random filename, so you can paste one into a task in Asana, Teamwork, Slack or anywhere else and it will load for whoever opens it. The flip side is that the link is the only thing protecting the image: it is never shown to anyone who cannot already read the comment, and the filename cannot realistically be guessed, but a link you paste somewhere public is viewable by anyone who has it.
Can I use this on a live site without visitors seeing it?
Yes, and there are three ways to keep it contained. Set the site mode to “Live site for client review” and the toolbar appears only on pages you have listed or ticked in the page editor. Protect those pages with a WordPress page password and the toolbar waits until the password is entered. Or set “Who can leave feedback” to “Only people with the review link” and it stays hidden from everyone who has not opened the link. They combine freely.
Can visitors on my live site send feedback without seeing each other’s?
Yes. Set the site mode to “Live site for anyone to comment”. Visitors can leave feedback on any page, but only moderators can read it. Each visitor still sees the comment they just sent, so they can correct it during the edit window.
What happens on password-protected pages?
The toolbar and the page’s feedback stay hidden until the page password has been entered, the same as the content. The feedback is protected on the server as well, not just hidden. A link to one comment still works: it opens that comment once the password is in. You can turn this off in Settings.
Notification emails are not arriving. What can I do?
The plugin sends email through WordPress, which uses your server’s own mail system. Many hosts deliver that mail badly or not at all. Install an SMTP plugin and connect it to a proper email service; that fixes delivery for the whole site.
How do I turn feedback on for just one page?
Edit the page and tick “Allow feedback on this page” in the Feedback box in the sidebar. That writes to the same “Limit to these pages” list the settings screen shows, so there is only ever one list to reason about — changing either place changes both. The checkbox appears once a page is published, because until then it has no final address to record.
Does it work with Elementor, Divi and other page builders?
Yes. The toolbar appears on the finished page, where reviewers see it, and stays out of the builder’s own editing screen so it never sits on top of the design you are working on. To switch feedback on or off for a page, view it on the front end while signed in and use the Feedback item in the admin bar. That works the same with every builder. The “Allow feedback on this page” checkbox on the WordPress edit screen does the same job.
Does it work with caching plugins?
Yes. The front end fetches its session and security token at runtime rather than reading them from the cached HTML.
What happens when I deactivate or delete the plugin?
Deactivating asks first: keep the comments and screenshots for later, or delete them because the project is done. A CSV export is offered before anything is deleted. Deleting the plugin removes nothing unless you ticked “Delete all feedback…” in Settings beforehand.
Changelog
Adds an Activity screen for reading whole conversations, default visibility settings, and dates in your own timezone.
1.10.1
- Fixed: feedback containing code — an embed code, an iframe, a snippet of HTML — failed to save on many hosts with only “Request failed”. The host’s security firewall was refusing the submission as a suspected attack before WordPress saw it. Comment text now travels encoded, so the firewall has nothing to object to, and is decoded and checked on arrival exactly as before. The same applies to replies from the dashboard.
- Fixed: code in a comment was silently deleted when it did get through, so a pasted embed code vanished and left the comment making no sense. Comments are now kept exactly as written. They were never displayed as markup and still are not: every place a comment appears shows it as text.
- Fixed: previews in the feedback list, the screenshot library and notification emails no longer drop anything that looks like a tag.
- Changed: when something in front of WordPress blocks a save, the panel now says so plainly, instead of “Request failed”, and keeps the text so nothing is lost.
1.10.0
- Added: the annotation tools sit beside the Feedback button, and work with the panel open or closed. Leaving feedback no longer means opening a panel that then covers part of the page you are commenting on, and a tool you have picked stays picked when you close the panel to reach something behind it.
- Added: right-click to comment. Right-clicking the page drops a pin there; right-clicking selected text comments on that text. Shift + right-click still opens the browser’s own menu, form fields keep theirs for copy and paste, and touch screens are left alone. It can be switched off in Settings.
- Added: side by side. With the panel open, the page moves over and reflows into the space beside it instead of sitting underneath. Headers, cookie bars and chat bubbles the site pins to the window are moved clear of the panel too, including headers that only pin themselves once you scroll, and every change is put back exactly when the panel closes. On a window too narrow to fit both, the panel lays over the page as before.
- Added: the panel can go on either side of the window, and its edge can be dragged, or moved with the arrow keys, to make it wider or narrower. Each reviewer’s choices are remembered in their own browser.
- Added: links to one page’s feedback. The Feedback menu in the admin bar shows how many conversations the page has and opens them in the dashboard. The page editor links to them, the Pages and Posts lists show “Feedback (3)” under any page that has some, and the feedback list and Activity screen can be narrowed to one page from any row. Moderators also get the link inside the panel.
- Changed: moderators who cannot change settings now see the Feedback menu in the admin bar too, with the page’s feedback links but not the on/off switch.
- Added: feedback left with the panel beside the page records how wide the page actually was, alongside the window width. The site’s own breakpoints still see the full window, so side by side shows a desktop layout in a narrower space than any visitor would; the dashboard, the panel, notification emails and the CSV export now say so, so a layout problem only the narrowed page has can be recognised for what it is. Existing feedback is unaffected.
1.9.1
- Added: a position for the feedback button. Sites often already float something in the bottom right — an accessibility widget, a chat bubble, a cookie bar — and two buttons in one corner cover each other up. Choose any corner, and nudge the button further in to sit above whatever shares it.
- Fixed: on a page listed through a rule ending in “/”, the admin bar reported “Feedback: off” while the toolbar was plainly loading on that page, and offered to turn on something that was already on. The switch was testing the address with its trailing slash removed, which is not the address the toolbar is judged on.
1.9.0
- Added: an Activity screen that shows whole conversations, every thread with its replies underneath, either as a running log or grouped under the page they were left on.
- Added: a Replies column in the feedback list, linking straight to the thread.
- Added: default visibility settings. File new feedback to a team automatically, start it internal, or turn on “Always internal” so reviewers are not given the choice and nothing can be filed as client-visible by mistake.
- Added: bulk actions to open the feedback you have ticked in new tabs, either its full detail or the page it sits on.
- Added: Copy link buttons beside the review links on Settings and Teams, with generating a new link stepping back to a quieter action.
- Added: annotations record the heading they sit under and the text around them, and the CSV export carries those alongside the element selector. A pin with a screenshot and few words now means something in a spreadsheet.
- Changed: dates are shown in the reader’s own timezone, with the site’s own time on hover, so people in different places each see their own clock.
- Changed: integrations authenticated with an application password no longer need a browser security token, and the feedback route now describes the fields it accepts.
- Changed: a signed-in caller who can moderate may set the author name through the API. The account behind it is still recorded, and the dashboard shows both.
1.8.2
- Added: bulk actions for visibility in the feedback list. Select any number of comments and mark them internal (hidden from clients and guests), make them visible to clients again, or assign them to a team. Replies move with their thread.
- Fixed: marking a single comment internal left its replies visible to clients. Replies now follow the thread they belong to.
1.8.1
- Fixed: visitors who were not signed in to WordPress could not reply to feedback. The reply box refused the reply because it needed a name but offered nowhere to enter one. It now asks for a name, and for an email address when the site requires one.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best LocalFeedback alternatives
All annotation plugins →
FAQ
LocalFeedback: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 15, 2026
Is LocalFeedback free?
Yes. LocalFeedback is free to download and use from the official WordPress.org plugin directory.
Is LocalFeedback safe to use in 2026?
LocalFeedback is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 73/100 on our health check.
How many websites use LocalFeedback?
LocalFeedback is active on 10+ WordPress websites and has been downloaded 485 times since it launched in September 2026. It was downloaded 367 times in the last 30 days.
Does LocalFeedback work with WordPress 7.1?
Yes. The developer has tested LocalFeedback up to WordPress 7.1.3, the latest release. It requires WordPress 6.2 or newer.
What PHP version does LocalFeedback need?
LocalFeedback requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was LocalFeedback last updated?
The latest version, 1.10.1, was released on September 30, 2026 (2 weeks ago).
Who makes LocalFeedback?
LocalFeedback is developed and maintained by Matt Enser.
What are the best alternatives to LocalFeedback?
The most popular alternatives to LocalFeedback are Hypothesis (200+ installs), Side Matter (100+ installs) and Noted Visual Feedback (100+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
