Skip to content

Sync to Obsidian

The Markdown export is a snapshot: you download it, unzip it, and that’s that. The Becoming plugin for Obsidian is the other kind: connect it once, and it keeps a folder in your vault filled with your highlights — one note per source, in the same format as the Markdown export — adding new ones as you import them. It works in Obsidian on desktop and on iPhone, iPad and Android.

Anyone with access to Becoming: during a free trial, on The Library or on The Academy. You also need Obsidian. The plugin is free to install; Obsidian lists it as Paid because it needs a Becoming plan.

If your subscription lapses, syncing pauses. The plugin tells you so — “Sync paused — your Becoming plan ended. Your files stay in your vault.” — and every note already in your vault stays exactly as it is. When you resubscribe, the next sync picks up where it left off. You can still remove devices and disconnect while your access is lapsed, and the CSV and Markdown downloads stay open either way.

Becoming is in Obsidian’s community plugins:

  1. In Obsidian, open Settings → Community plugins (if Obsidian asks, turn community plugins on first), click Browse and search for Becoming — or open it in Obsidian straight from here.
  2. Click Install, then Enable.

The same steps are in Becoming on the web: go to Settings → Exports and, in the Sync to an app card, click Set up on the Obsidian row. On a phone or tablet, the steps are the same in Obsidian’s mobile app.

  1. In Obsidian, open Settings → Becoming and click Connect. Your browser opens Becoming on a Connect Obsidian page.
  2. Sign in if you need to. The page names the device asking for access — something like “Obsidian · My Notes · macOS”, from your vault’s name and your system. Check it, then click Approve.
  3. The page reads “Connected. Return to Obsidian — it will finish on its own.” Back in Obsidian, within a few seconds, the plugin says “Becoming is connected. Syncing your highlights…” and runs its first sync.

While it waits, the plugin’s settings read “Waiting for approval in your browser…”, with a Cancel button. If ten minutes pass without an approval, the plugin stops waiting; click Connect again for a fresh page. Each page approves once; approve an old one again and Becoming tells you the link was already used.

Once connected, the device appears on the Obsidian page in Becoming (Settings → Exports, then Manage on the Obsidian row), under Devices. In the Becoming app on iPhone and Android, the Obsidian row in Settings → Exports shows the status: “Not connected” until a plugin is connected (tap it to open this guide), “Not synced yet” before its first sync, then when it last synced (“Synced 13 min ago”). With a lapsed plan and nothing connected, it reads “Subscribe to sync”. Managing devices happens on the web.

The plugin writes one note per source — each book, article, video or podcast you have highlights from — into a Becoming folder, sorted by kind:

Becoming/
├── books/
│ ├── Un Mundo Feliz.md
│ └── Deep Work.md
└── articles/
└── Naval on X.md

The folders are books, articles, videos and podcasts whatever your language, and only the ones you have something in are created. Each note is the same file the Markdown export produces for that source:

  • Frontmatter — title, author, type, origin, language, url, asin, becoming_url, highlights (how many the note holds) and exported_at, which Obsidian shows as Properties. Keep becoming_url: it’s how the plugin recognizes the note.
  • Highlights — one bullet per highlight, in reading order, ending with a link to where it sits in the source when there’s one: a Kindle link that opens the Kindle app at that location, a video link that jumps to the exact second, an X link that opens the post. Your tags — as #hashtags, so Obsidian picks them up — and your notes sit under each highlight as Tags: and Note: sub-bullets.
  • Notes — the notes you wrote on the source itself, as they were when the note was first written.

Headings and labels follow your account’s language; the frontmatter keys stay in English. Only your own highlights are included: popular passages, the ones Becoming’s AI surfaces, Themes, Practices and reflections stay out.

In Obsidian, under Settings → Becoming:

Setting Default What it does
Base folder Becoming Where new notes go. Changing it leaves the notes already in your vault where they are.
Group files in category folders On Sorts notes into books, articles, videos and podcasts. Off puts every note directly in the base folder.
Sync when Obsidian opens On Syncs 30 seconds after your vault has loaded, so Obsidian Sync or iCloud can bring your notes down first.
Sync frequency Every 12 hours Manual, every hour, every 12 hours or every 24 hours, while Obsidian is open.
Resync deleted files Off Writes deleted notes again in full at the next sync, including ones deleted before you turned it on. See Renames, Moves and Deletes.

Under Sync, at the top of the plugin’s settings, Sync now syncs right away and Resync everything sends all your highlights again (see Resync Everything). Both are also in Obsidian’s command palette, as Becoming: Sync now and Becoming: Resync everything.

Becoming can’t reach into your vault; the plugin fetches what’s new. So new highlights arrive whenever the plugin syncs: 30 seconds after Obsidian opens, every 12 hours while it’s open (or on the schedule you pick), and whenever you run Becoming: Sync now, which syncs right away and tells you how many new highlights it brought in. On desktop, the status bar shows when the last sync ran — “Becoming: synced 3 min ago” — or that sync is paused or not connected. The Obsidian page in Becoming shows the same from the other side: when your vault last synced, and how many highlights have reached it (“120 Highlights exported”).

Becoming writes each note once and from then on only adds to it:

  • A source you haven’t synced before becomes a new note.
  • New highlights on a source that already has a note are added at the end, under a dated heading such as ## New highlights added Oct 13, 2026. In the frontmatter, the highlights: count and the exported_at: date are updated in place; nothing else in the note is touched.
  • Changes made in Becoming to a highlight that’s already in your vault don’t follow it there. Edit a highlight, a note or a tag in Becoming later, and the note keeps what was sent the first time. The same goes for notes you add to a source afterwards; the Markdown export always has them.
  • Quit Obsidian in the middle of a sync and the next one picks up where it stopped. At worst, the note being written at that moment gets the same new highlights twice; delete the repeat.

The notes are yours, and your edits are never overwritten. Add your own thoughts, links, headings and properties: the plugin only ever adds at the end of a note and updates those two frontmatter lines.

  • Rename or move a note, or the folder it’s in, and new highlights still go to it. The plugin follows the rename, and if it ever loses track, it finds the note again by its becoming_url frontmatter — so keep that line.
  • Delete a note in Obsidian and it stays deleted: the plugin remembers the deletion — including one synced in from another device — and skips that source’s new highlights. Turn on Resync deleted files and deleted notes, including ones deleted before you turned it on, are written again in full — every highlight, old and new — at the next sync. Becoming: Resync everything also brings back every deleted note.
  • A note that’s missing without having been deleted in Obsidian — because Obsidian Sync or iCloud hasn’t brought it down to this device yet, say — is written again in full, so new highlights always land in your vault. At worst, your vault sync keeps a conflict copy; nothing is lost. A note removed while Obsidian was closed (in Finder, say) also counts as missing, and comes back in full with that source’s next new highlight.

Becoming: Resync everything sends all your highlights again, as if the vault had never synced; it asks before it starts. Each Becoming note you haven’t touched since the plugin wrote it is rewritten in place. A note you edited stays as it is, and the fresh copy is written next to it with a number added — Dune 2.md — and the plugin tells you where. Notes you deleted come back.

If your vault already holds notes from the Markdown export, the plugin recognizes them by their becoming_url frontmatter, wherever they are in the vault. A note that still matches what Becoming would write today is picked up as it is, and new highlights are added to it — nothing is duplicated. A note that has changed — because you edited it, or because highlights reached Becoming after you downloaded the zip — is left alone, and the plugin writes a fresh copy next to it (Dune 2.md).

If you never edited the notes from the zip, the tidiest start is to delete that folder before you connect and let the plugin write everything fresh into Becoming.

Using the same vault on your computer and your phone — through Obsidian Sync, iCloud or another sync service — works. If your sync service also carries Obsidian’s settings (the vault’s .obsidian folder), the plugin arrives on the other device already installed and connected. If it doesn’t, install and connect the plugin there too; each connection shows up as its own device in Becoming.

Only one device syncs at a time. If another one is mid-sync, the status bar reads “Becoming: syncing on another device”; the next sync — or Becoming: Sync now a minute later — goes through. What one device writes reaches the others through your sync service, not a second time from Becoming. When Obsidian opens, the plugin waits 30 seconds before syncing, so your sync service can first bring down what another device wrote; Becoming: Sync now syncs right away.

Becoming keeps a single record, per account, of which highlights have reached your vault — not one per vault. Connect a second vault — or copy a vault’s plugin settings into another — and the two split new highlights between them: each one goes to whichever vault syncs first and never to the other. So keep one vault connected; the same vault on your computer and your phone counts as one.

To move to a different vault, remove the old vault’s device under Devices in Becoming, connect the plugin in the new vault, then run Becoming: Resync everything there to write your whole library into it.

There are three ways to stop syncing, and they do different things:

  • Disconnect, in the plugin’s settings in Obsidian, forgets the token in this vault’s plugin settings — and if your vault sync carries the .obsidian folder, that’s every device sharing it. Becoming keeps listing the device, and the token keeps working, until you remove it. To stop syncing for sure, use Remove.
  • Remove, next to a device under Devices on the Obsidian page in Becoming, revokes that device’s token for good: every install using it stops syncing and says it’s no longer connected. Click Connect in Obsidian to connect again. Add another device, on the same page, shows the install steps.
  • Disconnect Obsidian, at the bottom of that page, signs out every plugin install at once; click Disconnect and confirm.

In every case, the notes already in your vault stay exactly where they are. And since Becoming remembers which highlights reached your vault, connecting again later picks up where it left off — adding to the notes you have rather than starting over. If you reconnect in an empty vault, run Becoming: Resync everything to bring your whole library back.

A token that goes unused for 180 days is revoked on its own; connect again if you come back to that vault.

Connecting stores a token in the plugin’s data.json, inside your vault’s config folder — usually .obsidian/plugins/becoming/data.json — in plain text. It can only read your highlights and record what was synced; it can’t change anything else in your account. If your vault syncs through iCloud, Git or another service, the token travels with it. If it ever ends up somewhere it shouldn’t — a public repository, say — remove the device in Becoming and the token stops working.

The plugin talks only to Becoming. Nothing from your vault is sent except the vault’s name, which labels the device when you connect.