reMarkable Connect Export vs a Git Vault: The PDF That Never Becomes a Note

reMarkable Connect makes leaving the tablet feel easy: tap share, get a PDF or sync a copy to the cloud apps you already tolerate. Months later the “notes” directory is a stack of PDFs named Meeting, Meeting (1), and Untitled. Nothing is lost. Nothing is a note you can link, diff, or grep. A git-backed vault is the opposite promise: every capture becomes a file with history—if you actually do the conversion work Connect pretends to finish.

This is the fork between convenient export and durable knowledge. It is written for people who bought a reMarkable to think, then watched the outputs pile up as beautiful dead ends.

What Connect is optimizing for

Connect is a delivery network. It moves pages to email, cloud drives, and reading apps with minimal ceremony. That matches the reMarkable product ethos: reduce friction between ink and somewhere else. PDFs are the lingua franca. Everyone can open them. Almost nobody can refactor them into a personal wiki without pain.

If your job is “send the annotated contract back to legal,” Connect is the product. If your job is “build a second brain across years,” Connect is a ferry, not a harbor.

What a git vault is optimizing for

A git vault—Obsidian, Logseq, plain markdown in a repo—optimizes for change over time. You care about titles, links, commits, and the ability to answer “what did I believe in April?” PDFs can live in that vault as attachments, but the atomic unit should be text you can edit.

Git also forces a ritual: stage, commit, sometimes push. That ritual is annoying on bad days and invaluable on the day the tablet dies or the Connect subscription story changes. Annoyance is part of the durability.

The PDF that never becomes a note

The failure mode is predictable.

1. You ink a useful page on reMarkable.
2. You export via Connect to Drive or email “so it’s safe.”
3. You feel finished because the file exists off-device.
4. You never title it, never extract text, never link it from a daily note.
5. Six months later search fails because PDF OCR was never run—or was run into another pile of untitled text.

Safety without retrieval is storage. Storage is not the same as a note. The emotional trick Connect plays is closing the open loop in your head before the knowledge loop is closed.

When Connect-first is still correct

• Outbound collaboration: other people need a PDF now.
• Read-it-later annotations you will not rewrite.
• Sketch-heavy pages where text extraction would be theater.
• You already have an assistant (human or script) who files exports weekly.

In those cases, name aggressively at export time. 2026-09-21-acme-pricing-sketch.pdf is a note-shaped PDF. Document.pdf is landfill.

When git-first is worth the friction

• You retrieve old thoughts weekly or more.
• You want links between projects, people, and decisions.
• You already live in Obsidian or a markdown repo.
• You distrust long-term dependence on any single vendor sync story.

Then Connect becomes a transport into an inbox folder watched by you or a script—not the final resting place.

Practical bridges that work

Inbox PDF → weekly markdown. Everything Connect dumps lands in Inbox/remarkable/. Every Sunday you create one markdown note per keeper PDF with title, three bullets, and a link to the file. Delete or archive trash. Time-box to forty minutes.

OCR into git, keep PDF as attachment. Desktop OCR produces a .md sibling. Commit both. Imperfect text plus image beats perfect PDF you never open.

reMarkable as capture, keyboard as structure. Use the tablet for messy thinking. Use the laptop the same day to title and place the note. Same-day is the magic; next-month is how PDFs fossilize.

Typed overlays. Where reMarkable typed text exists, prefer exporting something closer to text. Handwriting-only pages need the OCR bridge; typed pages should not wait in PDF purgatory.

Tooling without a Rube Goldberg shrine

You can automate Connect folders with desktop scripts, rclone, or OCR batch jobs. Start dumb. A manual Sunday review beats a broken automation that fills the vault with garbage text. Automate only after the naming rules are habits.

Git clients on the tablet are usually the wrong fight. Keep git on the computer that merges. The reMarkable is upstream capture.

Subscription and account risk, spoken plainly

Connect’s convenience is bundled with account surface. Even if today’s export works offline-ish, your muscle memory may assume cloud presence. A git vault on hardware you control fails differently: you can lose a laptop and still have remotes, or lose a remote and still have a disk. Diversify on purpose. Do not argue ideology—copy the kept notes.

A 30-day experiment

For one month, forbid “export and forget.” Every export must either (a) become a named markdown note within 24 hours, or (b) be deleted as not worth keeping. Count how many PDFs you currently keep out of guilt. Most people discover half the pile was anxiety, not knowledge.

After thirty days, keep Connect for collaboration PDFs and git for anything you expect to search. That split is the sane end state.

Decision guide

Use Connect export as the finish line only when another human needs the PDF or the page is inherently non-textual.

Use a git vault as the finish line when future-you must find, link, and revise the thought.

Use Connect as a ferry into git when you like reMarkable’s writing feel but refuse to live in an untitled PDF swamp.

The PDF that never becomes a note is not a Sync failure. It is a definition-of-done failure. Redefine done as “named, linked, and in the vault”—and suddenly Connect is helpful again instead of a guilt generator with excellent pen latency.

If you remember one rule, make it this: never let the share sheet be the last time a page receives a title. Titles are how PDFs become notes. Git is how notes survive. Connect is how ink leaves the tablet. Keep each tool in its lane.

Naming rules that prevent the swamp

Adopt a single pattern and refuse exports that violate it. A workable pattern is yyyy-mm-dd-topic-source.pdf plus a matching markdown stub with the same stem. If Connect’s share sheet makes renaming annoying, rename on the desktop in the same sitting—before the file disappears into a Drive folder titled “reMarkable.”

Ban the words Untitled, Document, Scan, and Meeting without a proper noun. Ban duplicate exports of the same page unless the new one is a true revision with v2 in the name. When you break the rule, delete the file; do not “park it.” Parking is how swamps form.

Also decide where attachments live in the vault: a flat attachments/remarkable/ folder is easier to backup than nesting PDFs beside every note. Link from the note; do not rely on folder proximity as memory.

Collaboration versus personal knowledge

Split the mental model. Outbound PDFs can stay PDFs forever. Personal insight must graduate. If a page is half collaboration and half personal reflection, duplicate intentionally: send the clean PDF, keep a markdown extract of the reflection only. Mixing those intents in one artifact is how searchable knowledge gets trapped in a file you are afraid to edit because legal already has a copy.

What to do with the existing PDF pile

Do not OCR everything this weekend. Triage. Sort by modified date and keep only the last year unless a project is still live. For each keeper, spend two minutes: title, one-sentence summary, link from a project note. Move the rest to an _archive/remarkable-raw/ folder that you accept may never be searched well. Guilt-reading a thousand PDFs is not a knowledge practice.

If a PDF is purely outbound (signed forms, annotated readings for someone else), leave it in Drive and out of the vault. The vault is for thoughts you will reuse—not for every pixel the tablet ever produced.

Versioning without fetish

Git history is useful when you revise decisions, not when you commit every OCR experiment. Commit meaningful markdown; do not commit five OCR retries of the same page. If OCR quality improves later, replace the text, keep the PDF attachment, and write a one-line commit message. The goal is a narrative of your thinking, not a museum of recognition engines.

Tags like source/remarkable help you audit how much of the vault still depends on ink capture. If that percentage is high and retrieval is poor, your bridge is underbuilt—not your tablet.

Closing the loop the same evening

The cheapest upgrade is temporal: export, then process before sleep. Morning-you will not be kinder to untitled PDFs. Pair the tablet with a charging routine that includes “clear Connect inbox into vault inbox.” When the battery cable goes in, the files get names. Habit beats tooling.

If you skip that pairing, Connect will keep feeling productive while your future search stays empty—and you will blame the tablet for a ritual you never built.

Build the ritual once; let the pen stay joyful and the vault stay findable.