Omnivy Web Clipper
A browser-first web clipper that turns any page into clean, editable Markdown and saves it into Obsidian, Notion, or your cloud drive.
ReactTypeScriptViteRedux ToolkitNext.jsChrome Extension APIs
Project overview
What this project is and why it exists.
Built to solve the gap between quick web clipping and a genuinely usable knowledge base entry, with extraction tuned per site type rather than one generic scraper.
Who it was built for
People building a personal knowledge base in Obsidian or Notion who want clean, structured captures instead of raw HTML.
Scope
Monorepo covering a Manifest V3 Chrome extension for capture and a Next.js web app for auth, provider connections, and clip history.
Business challenge
Coordinating extraction, editing, and multi-destination saving across an isolated browser extension context and a separate authenticated web app.
Solution approach
Built a knowledge pipeline that selects a site-aware extraction strategy per page, then either writes to Obsidian via local URI or sends the clip to the web app API, which refreshes provider tokens and uploads the Markdown to Google Drive, OneDrive, Dropbox, or Notion.
Technical architecture
pnpm/Turbo monorepo with a Manifest V3 extension (React, TypeScript, Vite, Redux Toolkit) for in-browser extraction, and a Next.js 15 web app (NextAuth, Prisma, Postgres) for OAuth connections, encrypted provider tokens, and clip history, sharing a UI and config package.
Project gallery
A closer look at Omnivy Web Clipper.
Goals
- Capture any page as clean, editable Markdown in one click
- Support save destinations across Obsidian, Notion, and major cloud drives
- Keep captured content structured enough to use immediately, not just archived
Constraints
- Extraction quality varies across very different site types (docs, forums, AI chats, code hosts)
- Provider tokens must be encrypted and refreshed safely across extension and web app boundaries
Services delivered
- Extension architecture and content extraction
- Web app auth and provider integrations
- Cross-context state and token handling
- Site-aware extraction strategy design
Key features
- Site-aware extraction for GitHub, Stack Overflow, forums, AI chats, Notion, docs, and articles
- Editable capture: title, source, author, tags, and custom properties before saving
- Multi-destination saving: Obsidian, Google Drive, OneDrive, Dropbox, Notion
- Popup, background auto-save, and context-menu capture options
Technical highlights
- Manifest V3 extension architecture with isolated content scripts and popup UI
- Encrypted provider token storage with short-lived extension token issuance
- Site-aware extraction pipeline instead of a single generic scraper
- Shared monorepo tooling across extension, web app, and UI packages
Lessons learned
Clipping tools are only as useful as what happens after the save — structuring the output well matters more than capturing faster.
Services connected
Third-Party & API Integrations
Stop wasting time doing manual data entry. We connect your website, web applications, and backend tools using APIs and custom webhooks, so data moves automatically between systems instead of being re-entered by hand.
Solutions connected
Technologies connected
Case studies connected
Personal Engineering • architecture
Omnivy: A Chrome Extension for Clipping the Web into Obsidian, Notion, and Cloud Storage
Case study on building Omnivy, a Chromium browser extension that turns articles, code, and discussions into clean Markdown and routes it to Obsidian, Notion, Google Drive, OneDrive, or Dropbox.
- Chrome Extension (Manifest V3)
- TypeScript
- Notion API
Insights connected
Related insight articles are not linked yet.
Transparency note
This page intentionally avoids fabricated metrics, testimonials, and timeline claims. If data is private or unavailable, it is not guessed.
Need a similar outcome?
Tell us your current challenge and we will map a practical path using the most relevant services and implementation approach.