How it works

Two surfaces.
One promise.

A web app handles the one-time migration. A Chrome extension handles the ongoing clipping. Both route to the destinations you already trust.

01 · Migration
01
Export

Evernote → File → Export notebook → ENEX.

.enex (up to 50k)
02
Drop

Drag the ENEX into the web app. Nothing uploads.

client-side parse
03
Pick format

Markdown, HTML, JSON, or push direct.

5 output formats
04
Download

ZIP of clean files, preserving structure.

preserves tags + urls
02 · Ongoing clipper

One shortcut. Three destinations. Zero library.

  • CapturePress ⌘⇧E on any page. Works with articles, threads, PDFs opened in browser.
  • CleanStrips nav, ads, cookie banners. Preserves headings, links, source URL.
  • RouteSends to every destination you have enabled. In parallel.
  • PurgeSuccess → delete within minutes. Failure → hold 7 days for retry.
# data flow
browser → router → destination

purge_ttl:
  success: ~immediate
  failed:  7d

stored_on_router:
  nothing, by design

logs:
  24h rolling, exportable
Privacy posture
We route. We don't store.

No training on content. No analytics on body text. No library. The archive lives where you already work.

Read the essay →