Capture research evidence from any page. Tag it later. Export it anywhere.
A browser extension for people who build products and services out of what real users actually say. Highlight a sentence anywhere on the web, save it in one keystroke, and let a tagged, searchable, exportable evidence base build itself while you read.
No account. No server. No subscription. Everything stays in your browser.
فارسی · Install guide · Project brief
Research evidence arrives scattered: an app store review here, a support ticket there, a forum thread, a competitor's cancellation page, a line in a PDF. It ends up spread across twenty tabs, a document, and a screenshot folder — and by synthesis day, half of it has lost its source.
The tools built for this problem are priced per seat, per month, in USD, and assume a research ops team behind them. Most designers don't have that. They have a browser and a deadline.
Evidence Clipper is the small version of that idea: capture is one keystroke, structure comes later, and the data belongs to you.
The single decision this tool is built around.
When you are reading, you are in flow. Any dialog that asks "which project? which tag?" at that moment costs you the thought you were having — and after three of those, you stop capturing altogether.
So capture is one action with zero questions. Tagging, projects, and notes happen later, in the library, where an Untagged filter acts as your triage queue. This mirrors how qualitative coding actually works: gather first, code in a dedicated pass.
| Role | What they get out of it |
|---|---|
| Service Designer | A source-linked evidence base behind every pain point on a journey map |
| Product Designer | Verbatim user language to defend a design decision in review |
| UX Researcher | Desk research and VoC capture without a per-seat repository tool |
| Product Manager | Feature requests and complaints collected in the customer's own words |
| Design Lead / Head of Design | A shared evidence standard across a team, with exports that survive tool churn |
| CX / Customer Experience Manager | Review, dispute, and support-channel signals aggregated by theme |
| Design Thinking Coach / Educator | A teachable, visible artifact of the "evidence, not opinion" habit |
| Consultant / Freelancer | Discovery findings that arrive at the client meeting with a URL attached |
| Founder | Early market and competitor signals gathered while reading, not as a separate project |
Discovery that survives the handoff. During discovery on a bank, insurer, or telecom, everything you find in the wild — complaints, app store reviews, regulator notices, forum threads — is captured with its source URL and date. When a stakeholder asks six weeks later "where did this pain point come from?", the answer is a link, not a memory.
Journey maps with citations. Tag by journey stage or by pain type, then filter. Each cluster becomes an evidence-backed section of the map instead of a workshop assumption written on a sticky note.
Competitor and benchmark teardowns. Tag Competitor and capture across rival products: pricing pages, cancellation policies, onboarding copy, terms. Export to CSV and you have a comparison table with sources.
Making the case for budget. Enterprise design work fails at the argument stage more often than the design stage. Fifteen verbatim quotes with URLs, filtered by theme, change a steering committee conversation more than any redesign mockup.
Multi-project separation. The project field keeps client work separate. One browser, several engagements, no leakage between them.
Team-friendly without a backend. No admin, no procurement, no data-processing agreement — the extension never sends anything anywhere. Sharing happens through exports, so a team can standardize on a tag taxonomy without a vendor contract. For regulated organizations, this is often the difference between "yes" and a six-month review.
Desk research and literature review. Capture claims, statistics, and definitions with the source attached. Markdown export drops straight into Obsidian, Notion, or a paper.
Voice-of-customer analysis. App store reviews, Trustpilot, Reddit, support forums, social replies — collected in one place, tagged by theme, exported for affinity mapping.
Secondary research for a synthesis session. Filter by tag, export Markdown, and print or paste onto the wall. Each item still carries its source.
Teaching qualitative coding. The base taxonomy is a starter codebook; the custom tags are where a student's own coding scheme emerges. The Untagged filter makes the coding pass visible as a distinct activity.
Longitudinal tracking. Because every item is timestamped, capturing the same theme over months shows whether a problem is getting better or worse.
Note on interview and session data. This tool captures what is on a web page. Consented participant data — recordings, transcripts, PII — belongs in a system built for it. Keep evidence public-source, and your export stays shareable.
- One-keystroke capture from any page — right-click or
Ctrl+Shift+E - Automatic metadata: source URL, page title, author, publication date, capture timestamp
- Surrounding paragraph saved as context, so a quote never loses its meaning
- Hybrid tag taxonomy: eight research-oriented base tags plus your own
- Project field for separating clients or studies
- Free-text note per item for your interpretation
- Full-text search across quotes, notes, titles, and projects
- Filter by project, by tag, or by
Untagged - Export to CSV, Markdown, or JSON — always respecting current filters
- JSON import for backup and restore
- Bilingual interface (English / Persian) with full RTL support
- Fully local: no account, no network requests, no telemetry
Pain point · Quote · Need · Workaround · Opportunity · Delight · Competitor · Context
Custom tags are added from any card and become available everywhere. To change the base set, edit BASE_TAGS in src/i18n.js.
Not yet on the Chrome Web Store or AMO. Load it unpacked:
Chrome / Edge / Brave
- Download or clone this repository
- Open
chrome://extensions - Enable Developer mode
- Click Load unpacked and select the repository folder
- Pin the extension to your toolbar
Firefox — see docs/install.md for the two manifest keys Firefox needs.
Select text → right-click "Save as evidence" (or Ctrl+Shift+E / Cmd+Shift+E)
→ green badge confirms, showing your total
Click icon → library opens in a full tab
→ filter "Untagged", tag in a batch, export
- Create nothing. Just start reading — app store reviews, complaint threads, competitor onboarding.
- Capture every sentence that says something real. Twenty minutes, forty items.
- Open the library, filter Untagged, and go through them once: tag, set project to
signup-study, add a note where your interpretation differs from the quote. - Filter
Pain point+signup-study, export Markdown, and you have the findings section — with links.
CSV — one row per item, columns: text, note, tags, project, source, author, url, capturedAt, context. UTF-8 with BOM so Excel opens Persian and Arabic text correctly. Built for spreadsheets, affinity tools, and Miro/FigJam import.
Markdown — blockquote, your note, attribution line, hashtags. Built for Obsidian, Notion, and reports.
> I gave up and just called the branch instead.
3rd participant to abandon at ID upload
— [Reddit — r/personalfinance](https://example.com/thread) · 2 Aug 2026 · Bank onboarding
#Pain-point #WorkaroundJSON — the full data model, lossless. This is your backup format and the one to use for restore.
{
id: "uuid",
text: "the selected sentence",
context: "surrounding paragraph, up to 800 chars",
note: "your interpretation",
tags: ["pain", "workaround"],
project: "bank-onboarding",
url: "https://…",
title: "page title",
source: "example.com",
author: "from page metadata, when present",
published: "from page metadata, when present",
capturedAt: "ISO timestamp"
}manifest.json Manifest V3: permissions, shortcut, icons
src/
background.js Context menu, keyboard shortcut, capture, storage
library.html Library markup
library.css Design tokens and layout
library.js Render, filter, tag, edit, export, import
i18n.js Bilingual strings, base taxonomy, author credit
icons/ 16 / 48 / 128 px
docs/ Install guide, project brief, images
Vanilla JavaScript. No framework, no bundler, no build step — edit a file, reload the extension, done.
The extension has no server and makes no network requests. Captured evidence lives in chrome.storage.local, inside your browser profile, and nowhere else.
The practical consequence: uninstalling the extension deletes your data. Export JSON weekly. That file is your backup and restores through Restore from file in the library.
Permissions and why each is needed:
| Permission | Reason |
|---|---|
storage |
Save evidence locally |
contextMenus |
Add "Save as evidence" to the right-click menu |
activeTab + scripting |
Read the selected text — only on the tab you act on, only when you act |
There is no <all_urls> host permission. The extension cannot read pages in the background.
- Floating capture button next to the selection, for capture without the right-click menu
- Active project, set once instead of typed per item
- Screenshot capture alongside text
- Keyboard-driven triage in the library
- FigJam / Miro-shaped export for affinity mapping
- Firefox build published to AMO
Issues and pull requests are welcome — see CONTRIBUTING.md. The most useful contribution right now is a report from real use: which tags you added, which ones you never used, and where the flow broke.
MIT — see LICENSE.
Designed and built by Sodeh Abadi · 2026