Export Your Highlights to Obsidian and Notion

If you keep a personal knowledge base, your reading pipeline probably has three moving parts: somewhere to stash links, something to highlight the ones you actually read, and a vault or database where the keepers end up. That's usually a read-later app, a separate web highlighter, and Obsidian or Notion — three tools, two subscriptions, and a sync step you have to remember.

Cowpin collapses the first two. You save links to it, it keeps a readable copy of each page, you highlight and annotate directly on that copy, and then you export the distilled version as Markdown into wherever your notes live. This post is about that last step: getting highlights out of Cowpin and into a knowledge base in a way that doesn't create busywork.

The shape of the export

Open any saved bookmark and hit Read. Cowpin shows its archived copy of the article — no ads, no popups, just the text. Select a passage to highlight it; you get five colors (yellow, green, blue, pink, orange), and each highlight has its own note field for a thought in your own words. Everything you mark collects in a Highlights & notes list under the article, so you're never re-scrolling a long piece to find what you flagged.

When you're done with a piece, that list has two buttons — Copy as Markdown and Download .md. The output is deliberately plain:

# The title of the article
Source: https://example.com/the-original-url

> The passage you highlighted, as a blockquote.

Your note on that passage, sitting right below it.

---

> The next passage you kept.

One heading per source, each highlight as a blockquote, your note underneath, a link back to the original, and a --- between sources if you exported more than one. It's the Markdown you'd type by hand if you had the patience — which is exactly why it drops into any tool without reformatting.

The export is per-source: you pull one article's highlights at a time, from that article's reader view. For a knowledge base that's usually what you want anyway — one source note per thing you read, not one giant dump.

Into Obsidian

The cleanest setup is a Sources/ (or Literature/) folder that holds one note per article. The workflow, once a week or whenever a piece is "done":

1. In Cowpin, open the article's reader view and hit Download .md.
2. Drop the file into your Sources/ folder. The # Title becomes the note name; the Source: line is your canonical link back to the original.
3. Read back through your own notes — the plain-text lines between the blockquotes — and pull anything that deserves to be a permanent, standalone idea into its own note, linking [[back to the source]].

The blockquotes render as clean quote blocks, and because the Source: URL is right at the top, every idea you promote out of that note keeps a trail back to where it came from. If you use a literature-note template, paste the Cowpin export into the body and let your template's frontmatter (author, date read, status) wrap around it.

A small thing that pays off: pick a meaning for each highlight color and stick to it. For example — yellow for a passage worth quoting later, blue for something you disagree with, green for an action or a follow-up. The colors don't come through in the Markdown, but by the time you're exporting you've already done the sorting in your head, and the note you write in each highlight's note field is what actually lands in the vault.

Into Notion

Notion doesn't take a .md file drop the way Obsidian does, but it reads pasted Markdown. Keep a Reading database with a page per source:

1. Use Copy as Markdown in the reader view.
2. Create a new page in your Reading database — title it after the article, fill in whatever properties you track (URL, topic, status, rating).
3. Paste into the page body. Notion converts the # heading, the > blockquotes, and the --- divider automatically. Your notes come in as plain paragraphs under each quote.

From there the source page is a first-class Notion object: you can relate it to a topic database, roll it up into a weekly review, or @-mention it from a project doc. The Source: link stays in the body as the pointer to the original.

Why the highlights hold up

All of this rests on one design choice: your highlights sit on Cowpin's own archived copy of the article, not the live page. Pages move, sites shut down, and publishers quietly swap content under the same URL. When that happens to a page you annotated in a browser extension, your highlights point at nothing. In Cowpin the archived text is what you marked, so the quotes you export are the quotes you actually read. (We went deeper on that in Highlight and Annotate Anything You Save.)

Nothing about the export is proprietary either. It's portable Markdown, and Cowpin also exports your whole bookmark library in Pinboard-compatible JSON, Netscape HTML, or Delicious XML. The door out is open in both directions, permanently — which is the point of moving your reading into a tool you can leave.

Getting your existing reading in

If your saves are currently spread across Pocket, Instapaper, Pinboard, Wallabag, or a browser's bookmarks, Cowpin's one-click import brings the links over — keeping tags, privacy, and read-later state — and then archives each page so you can start highlighting against a copy that won't rot.

Import your library and start highlighting — Cowpin is free while we're finding our first users.