Notate is for anything where pointing beats describing: design and motion review, product walkthroughs, code review, and handoffs. Unlike screenshot tools, it freezes open menus, hover and focus states before they disappear, or records a flow so you can pin the exact frame where an animation breaks. Gesture-based annotation keeps the flow fast; smart crop and reopenable sessions preserve the image, comments, and context so feedback stays useful when it reaches a teammate or an agent.
Hey Product Hunt 👋
I built Notate because I spend most of my time on frontend work—web, desktop, mobile, Electron, SwiftUI—and the hardest UI problems are often the hardest to explain in words.
When an animation’s easing felt wrong or a bug only appeared between two states, my workflow was absurd: record the screen, ask an agent to split it into frames, find the relevant frame, annotate it, then explain what the annotation meant. Regular screenshot tools lose transient UI states and have no useful sense of motion. They’re also awkward for designer feedback: the image and written context live separately, with no structured metadata to carry the feedback forward.
Multimodal agents changed the equation. They’re now genuinely good at understanding screenshots and annotations, so I wanted a system-wide tool that could capture anything—not an annotation feature trapped inside one chat app.
Notate freezes disappearing states, records motion frame by frame, lets me point and comment directly, and packages the visual with its context for a teammate or an agent. I’ve used it for real work since the first prototype became functional; it started as a workaround and quietly became part of how I build.
I’d love to hear how you handle visual feedback today—and where Notate could fit or fall short.
the freeze-frame capture for hover states is genuinely useful, that pain point always kills me with regular screenshot tools. one thing i'd love to see is a quick way to turn a pinned comment into a short loom-style video clip instead of just a still image, basically so i can show the broken animation in motion when a teammate opens the session. would make the handoff feel way more clear honestly.
The hover-state capture is genuinely useful. I was reviewing a dropdown animation that kept closing before I could comment, and being able to freeze it mid-hover saved me a ton of back-and-forth with the dev.
the honesty in this thread is what's selling me on it tbh. one thing I didn't see covered - since it's a full screen recording tool, what happens when a password field or some other sensitive text is visible in a frame that gets captured. is there any blur/redact step before the .notate file gets handed off to a teammate or an agent, or is it on the user to notice and re-record
@victor_aremu Hey! Just checked out Notate. The gesture-based approach (closing a loop to snap a shape) is super clever. Since it exports markdown for agents, I'm curious how you see the UI evolving for non-devs like designers who might use this for handoffs? The current dark minimal vibe is great for code review, but wondering if a lighter mode or web version is on the roadmap. Congrats on the launch!
Love the freeze-on-hover idea, that's been a pain point forever. One thing I'd really want: a way to tie comments to a specific element rather than just coordinates. When the layout shifts between draft rounds, my pinned feedback ends up pointing at the wrong button. Element-anchored notes would solve it.
the 'no replay guarantees, I will never pretend to reproduce app state' line further up is a rare kind of honesty for a launch post, most tools would just quietly overclaim there. practical question on the recording side - a long capture with per-frame data plus the pixel history for the perceptual diff sounds like it could get heavy fast. is there a size ceiling or compression pass on longer sessions, or does a 10 minute recording just produce a genuinely large .notate file you're expected to live with
Shared annotations for humans and agents could provide valuable execution context. How does Notate keep annotations attached when the underlying webpage, design, or code changes substantially?
The capture half is solved here in a way I haven't seen elsewhere, so my question is about the other end of the loop. I annotate the frame where the easing breaks, the agent changes the code — and now I have to get back to that exact state to see whether it's fixed. Same hover, same interruption point in the animation, same window size. That reproduction step is manual, and it's the reason I stopped filing my own visual bugs properly: the before was cheap, the after was a chore, so I'd eyeball it and move on.
Does a .notate session carry enough to make the re-capture repeatable — app, window geometry, frame timestamp — so a second capture is comparable to the first frame by frame? A diffable before/after pair is what would turn this from a feedback tool into a regression check, and the typed manifest you described to Anand sounds like it's already most of the way there.
"For humans and their agents" is the phrase doing the most work here. A human annotation is fundamentally positional — this thing, right here — and an agent has no pixels to point at, so the same note has to arrive as something structural instead.
What does the agent actually receive? Just the note text, or the note plus enough surrounding context to know what it was attached to? I'd guess "make this button smaller" is close to useless without the second part, and that's the piece that seems genuinely hard to get right.
Freezing transient UI states is the part that has always been missing. Regular screenshots lose hover states and animation frames at exactly the moment you need to point at them. The agent-readiness angle is the interesting differentiator here. How does Notate structure annotation metadata for agents? Is there a typed schema alongside the visual, or does the agent infer context from comments and pin positions?
Freezing hover states and pinning feedback to the exact frame solves a real gap in UI review. Can a teammate reopen a shared session and add or resolve annotations without needing the original capture environment?
About Notate on Product Hunt
“Annotate anything for humans and their agents”
Notate launched on Product Hunt on July 27th, 2026 and earned 110 upvotes and 18 comments, placing #13 on the daily leaderboard. Notate is for anything where pointing beats describing: design and motion review, product walkthroughs, code review, and handoffs. Unlike screenshot tools, it freezes open menus, hover and focus states before they disappear, or records a flow so you can pin the exact frame where an animation breaks. Gesture-based annotation keeps the flow fast; smart crop and reopenable sessions preserve the image, comments, and context so feedback stays useful when it reaches a teammate or an agent.
Notate was featured in Design Tools (261.5k followers), Developer Tools (516.5k followers), GitHub (41.3k followers) and Menu Bar Apps (12.2k followers) on Product Hunt. Together, these topics include over 146.7k products, making this a competitive space to launch in.
Who hunted Notate?
Notate was hunted by Victor Aremu. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Notate stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Victor Aremu