Markup.io captures the comment. Drafty closes the loop.
Both tools let a client pin a note on the exact spot with no login. The gap shows up after that: Markup.io gives you a pile of pins. Drafty gives you a threaded conversation with a resolve button, a searchable library of every artifact, and an agent that reads the feedback and ships the fix — on the same URL.
Drafty vs Markup.io
An honest, capability-by-capability look — including where Markup.io is the better pick.
| What your client needs | Drafty |  Markup.io |
|---|---|---|
| Point-and-comment with no client account | ||
| Threaded reply / resolve / reopen on every comment | ||
| Searchable library of every artifact you've shared | ||
| Agent reads the thread and ships the fix on the same link | ||
| Free to start — no credit card | ||
| 30+ file types including video uploads | ||
| Loom / screen recording attached to a comment |
How it works
Your client points at the exact spot
They open the link, hover the element, and pin a note. No account, no extension. Same first step as Markup.io.
The comment becomes a thread
Reply directly in the thread, ask a follow-up, mark it resolved when it's done. Not a static sticky — a real conversation anchored to that element.
Claude reads the thread and ships the fix
It reads every open comment, makes the changes, and pushes a new version on the same link. The thread marks itself done. Your client sees the update without a new email chain.
Why people switch
- Comments land but there's no way to reply, follow up, or know what's resolved
- Last quarter's client feedback is buried in a list of links with no search
- You still have to action every comment yourself, one by one
- Threaded replies with resolve / reopen — Every note has a clear status — nothing slips through
- Searchable library of every artifact — Find any brief, mockup, or proposal instantly with ⌘K
- Claude reads the feedback and ships the fix — The fix lands on the same link, versioned — you review, not retype
Who it's for
Share the mockup. Your client marks the exact section. The thread tells you what's open, what's resolved, and what Claude already fixed.
The deliverable is the link. Your client annotates inline, you reply in the thread — the whole review lives in one place, not scattered across email and Slack.
Drop the spec doc or v0 app. Testers comment on the exact line. Claude reads the open threads and pushes a new version — no account required to leave a note.
Questions
- What's the main difference between Drafty and Markup.io?
- Both let a client pin a comment on the exact spot with no login. Markup.io stops there — you get a pile of pins. Drafty adds threaded replies, a resolve/reopen status on every comment, a searchable library of every artifact, and an agent that reads the feedback and ships the fix on the same link.
- Does Drafty support as many file types as Markup.io?
- No. Markup.io supports 30+ file types including video uploads and Loom screen recordings — that's a genuine advantage if your workflow involves video review. Drafty focuses on docs, designs, PDFs, and live websites.
- Can clients comment without an account on both tools?
- Yes, on both. Markup.io guests can view and comment on markups they've been invited to. Drafty guests open the public link and comment directly — no invite required.
- What does Markup.io do better than Drafty?
- Markup.io has broader file format support — video files, Loom recordings, images, and 30+ types. It also has a polished, designer-focused annotation UI that teams already know. If video review is central to your workflow, Markup.io has the edge there.
- Is Drafty free compared to Markup.io?
- Drafty is free to start with no credit card required. Markup.io removed its free plan in early 2025; the Pro tier starts at $79/month and requires a card for the 30-day trial.
- What happens to comments in Drafty after they're made?
- Each comment becomes a thread. You or your client can reply, and you can mark it resolved when the change is done — or reopen it if more work is needed. Claude can also read the open threads and ship the fix directly, versioned on the same link.
Keep exploring
Send your next client a link, not a login.
Free to start. No card. They comment in one click — Claude ships the fix.