Features

Everything Pinnote does, from the click on your client's screen to the fix in your code.

Commenting on the page itself

Reviewers click Feedback, then the thing they'd change, and type. Nothing to install, no account to make.

Pin anything: Click any element to pin a note to it. The pin stays on that element as the page scrolls, resizes or changes.
Highlight an area: Drag instead of clicking to mark a whole region, like a section that feels too busy.
Draw on it: Circle or underline what you mean, and the screenshot keeps the drawing.
Whole-page notes: A General note is about the page as a whole, with no pin.
Replies in place: Your answer appears next to their note on the page. They can reply back, edit or delete their own.

Every note arrives with the detail that saves the follow-up email.

A screenshot: Exactly what the reviewer saw, with their pin and any area they marked.
The element: The thing they clicked, down to its text and HTML, so you can find it in your code.
Page, screen and browser: The address, the screen size and the browser, so a bug comes with where it happens.
Console errors: The last errors the page logged before the note was written, for whoever fixes it.

The review desk shows one note large on its screenshot, the conversation beside it and the rest as a strip of thumbnails.

Keyboard first: J and K move between notes, / searches, and resolving moves on to the next one.
Filters: By status, page, priority, label, who it's assigned to, and notes where a teammate tagged you.
Bug, idea or question: Reviewers can say what a note is in one click, and you filter by it. Turn it off for client reviews.
Priority and labels: Mark notes urgent or low, and label them your way. Urgent notes come first.
Export: A CSV for a spreadsheet, or a report with every screenshot and answer, to print or send to a client.
List view: Every note in rows with its thumbnail, to resolve or reopen many at once.
Email when it matters: As it happens, a daily summary, or nothing. Each person chooses.

One table: visitors, your site's logged-in users and the people you invite, with nothing to change on the site itself.

People you invite: By email or with your share link. They get the review tools, even where visitors see nothing.
Visitors: No button, or the simple form or the review tools, for as long as you like or for 7, 14 or 30 days.
Off: Switch the button off for everyone, invited people included, until you switch it back on. No new links needed.
Some pages only: Show it on some pages and hide it on others, like the dashboard but not its settings, with * for "anything after".
Review rounds: Ask for feedback on chosen pages until a date. Reviewers get a reminder the day before; you get a summary and a report.
Newcomers and blocking: Approve new people before others see their notes, keep each reviewer to their own notes, and block anyone.

Invite your team to a workspace. Everyone sees and answers the feedback on the sites they're given.

Site access: Give each teammate every site, or only the ones they work on.
Team-only notes: Talk it over beside the client's note. Reviewers never see team notes.
@tags: Tag a teammate in a team note and they get an email straight away.
Assign and track: Assign a note to someone, mark it in progress, resolve it, or send it to GitHub as an issue.

Clients see what's happening without chasing you.

Reply emails: Reviewers who leave an email hear when you reply or resolve their note.
Confirming the fix: When you resolve a note, the reviewer can say it looks right, or reply and it opens again.
A status page: One link listing what they asked for: to do, in progress and done, with your latest answer.
Clear invites: Invite emails say exactly what to click, with no account or password to set up.

Feedback reaches your team where it already works, with nothing to copy across by hand. Slack, webhooks and GitHub are part of Pro.

Slack: New feedback, replies, resolved and reopened notes post to a channel. Team-only notes never do.
Webhooks: The same events as signed JSON, for Zapier, Make or your own tools.
GitHub: Turn a note into an issue with its screenshot and element, in one click or by itself for every new note or only bugs. Closing the issue resolves the note.

Claude Code, Codex, Cursor or VS Code can read each note with its screenshot and element, fix it, reply and resolve it.

One line to connect: Add Pinnote as an MCP server with a key you can switch off at any time.
Never deletes: Agents can read, reply and resolve, but never delete. Pinnote marks their replies as coming from an agent.
Copy as prompt: Not using MCP? Every note has a button that copies it as a prompt for any agent.

Works on any site you can add a script tag to. See the integrations, the getting started guide and pricing.