Obsidian Quick Capture: 6 Setups That Fit GTD

The best Obsidian quick capture setup is the one that takes a thought out of your head before you have decided where it belongs, on a phone you have not unlocked yet, with no folder to pick and no tag to choose.

The honest conclusion, up front: for most people the fastest reliable route into an Obsidian vault is not the Obsidian app at all. It is a Shortcut or a small capture app that writes a timestamped markdown file straight into an Inbox folder. Obsidian’s own mobile Quick Capture, which has been arriving through early access builds, closes a lot of that gap and may well become the default answer. Until it is out of early access on your platform, keep a fallback. And whatever you pick, the capture route is the easy half. The half that fails is the emptying.

The Job Quick Capture Has to Do in a GTD System

Capture, in David Allen’s sense, is the habit of getting every open loop out of your head and into a trusted external place. The official description of the five steps puts capture first for a reason: nothing downstream works if the collection habit leaks.

The capture test: seconds from a locked screen, decisions on the way

Measure it properly. Not “how fast is it once the app is open”but how many seconds pass between your phone being face-down and locked, and the words existing somewhere you will look again. Then count the decisions you were asked to make: which note, which folder, which tag, which project, which date.

Two numbers. That is the whole test.

A lock screen Shortcut that dictates into a new file in /Inbox lands in roughly five seconds on a modern iPhone. Launching the full Obsidian mobile app, waiting for the vault to open and index, managing to a note and tapping into the right place is a longer sequence, and it gets longer as the vault grows. Those extra seconds are not an inconvenience. They are the difference between capturing the thought and telling yourself you will remember it.

Any decision at capture is the clarify step in disguise

This is the mistake I see most often in carefully built vaults. Someone wires up a capture template that asks for a type, a project link and a context tag, because the resulting note is so tidy. For a fortnight it is lovely. Then a client rings at 4pm, you have one free thumb, and the prompt chain asks you three questions you cannot answer yet. You skip it. After that you skip it quietly and permanently.

Folder, tag, project and due date all belong in clarify, at a desk, in a batch. Capture gets one job: text in, no questions.

One inbox, not five

A vault inbox only counts if nothing else competes with it. If some thoughts land in /Inbox, some get appended to the daily note, some sit in Apple Notes because that was quicker, and some go to a text file called notes2.txt on the desktop, you do not have an inbox. You have four half-inboxes and a retrieval problem. Pick the landing spot, then make everything else point at it.

Why plain markdown makes capture fiddly

Obsidian’s great strength is that your notes are plain markdown files in a folder you own, with no server deciding anything. That is also why capture is harder here than in a dedicated task inbox. A task app accepts a line of text into a cloud inbox and sorts out the plumbing itself. Obsidian needs a file, in a path, on a device, which then has to sync. Owning the files means owning the edge cases.

Three Mobile Routes Into Your Vault

1. Obsidian’s built-in mobile Quick Capture

Recent Obsidian mobile early access builds (1.14 onwards at the time of writing) introduced Quick Capture with Locations: text can be sent to a new note, to today’s daily note, to a bookmarked note, or to any note you choose. That removes most of the reason to bolt on a third-party tool, and because it is first-party it will not break when a plugin falls behind an update.

Best for

• Anyone who wants one vendor, no plugins and no Shortcut maintenance
• People already paying for Catalyst and comfortable running early access builds

Pros

• No plugin dependency and no external app in the chain
• Locations cover both the new-note and daily-note styles of working

Cons

• Early access means the behaviour can change; check the current release notes before building a habit on it
• Still relies on the vault being present on the device

2. Apple Shortcuts writing straight into /Inbox

My own default on iPhone. One Shortcut: dictate text, append a timestamp, save as a new markdown file in the vault’s Inbox folder. Put it on the lock screen or in a widget and you skip the app launch entirely. Use seconds in the filename (2026-10-11-143207.md), not just minutes, or two captures in the same minute will fight over the same name.

Best for

• IPhone and iPad owners who want the shortest possible time to captured
• Voice-first capture while walking between meetings

Pros

• Free, fast, and writes a real file with no app to wake up
• One file per capture, so no conflict risk

Cons

• Breaks silently if you rename or move the folder it writes to
• Apple only, and you will maintain it yourself

3. Capture apps that sit in front of the vault

Tools such as Type and Funnel exist precisely because cold-start speed is the problem. They open to a cursor, accept text, and file it. What you give up is control: another developer in the chain, another subscription in some cases, and a filing convention that is theirs rather than yours. Check before buying whether the one you fancy still needs the vault stored locally on the device, because most of them do.

Best for

• Android users, who do not have Shortcuts to fall back on
• Anyone who wants fast capture without building anything

Pros

• Opens to a text field in about a second, which is the whole point
• Usually handles timestamping and inbox filing for you

Cons

• Exit cost if the developer stops updating, and nothing you can patch yourself
• Some are paid or subscription, for a job a free Shortcut already does

Three Desktop, Voice and Paper Routes to the Same Inbox

4. A global hotkey on the desktop

At a keyboard, the test changes: it is now keystrokes, not seconds from a locked screen. QuickAdd with a capture template bound to a global hotkey does the job inside Obsidian. Outside it, fire the documented obsidian://new URI from Raycast, Alfred or whatever launcher you already run, so a thought can be captured from a full-screen spreadsheet without switching apps. Either way, aim the capture at a new file in Inbox, not at a shared running note.

5. Drafts as the front door

Drafts on Mac and iPhone takes the opposite approach: everything starts as text in one place, then an action decides where it goes. Capture first, destination later, which is exactly the GTD order. One action files the text into the vault as a markdown file; another sends it to OmniFocus, Things or Todoist if it turned out to be an action rather than a thought. The cost is a second app in the stack, which is only worth it if you were going to use Drafts anyway.

6. Voice assistant, wearable and paper

Siri or Google Assistant triggering the same Shortcut, a watch dictation, a note scribbled on an index card while your phone is in a bag with no signal. All of them count, provided they join the same queue. I still carry paper, and I am not apologetic about it: a vault you cannot reach is not an inbox. The rule is that the pocket notebook gets emptied into Inbox during the weekly review, same as everything else. If it does not get emptied, it is a souvenir.

Where Obsidian Quick Capture Quietly Breaks

Appending to one shared note from two devices. This is the classic one. An iPad and a Mac both append to today’s daily note inside a synced folder, the sync layer cannot merge two edits to the same lines, and you get a conflicted copy sitting beside the original. Obsidian’s own sync documentation is clear that conflicts are a thing you handle, not a thing that never happens, and third-party folder sync over iCloud or Dropbox is worse. A conflict file is a note you will never read again. One file per capture sidesteps the entire problem: two devices dropping separate timestamped notes into Inbox have nothing to argue about.

Cold start cost. Worth repeating because it is the real reason captures get skipped. Launch, index, tap, type is four steps where one would do.

Plugin dependency. QuickAdd, Templater and Dataview are community plugins. Not all community plugins run on mobile, and any of them can lag behind an app update or be abandoned. Build your capture chain so that if every plugin vanished tomorrow, you could still write a file into Inbox by hand.

Silent failures. Watch for a Shortcut writing to a folder you renamed three weeks ago, filename clashes from minute-only timestamps, and captures that land outside the vault entirely because the file picker defaulted to iCloud Drive. Nothing warns you. You just find out during a review that a fortnight is missing.

Turning Captured Notes Into Next Actions

Obsidian is not a task manager. Treating the vault as a to-do list is what turns a decent capture habit into a two-hundred-note swamp, and I have seen three months of unreviewed capture do exactly that.

Sort by type. Reference and project support material stays in the vault. Anything with a next action leaves for the list you actually look at in context, whether that is a filtered OmniFocus perspective, Things, or a Todoist inbox fed by its own capture routes.

A worked example. You capture “waiting for Sam to send the signed contract”during a phone call. At the weekly review it becomes a Waiting For entry with the date you asked, on the task manager, while the contract PDF stays in the vault as project support material linked to the project note. Two destinations, one capture, no decision made while you were still on the call.

The emptying needs a query. A saved search or a Dataview table listing files in Inbox with no tag and a creation date older than seven days takes about a minute to set up and is the only thing standing between you and a faster bin. Fast capture into an unreviewed folder is not a system.

An AI assistant earns its place in clarify, not capture. “Sort pension thing”is a useless list item, and an assistant is good at turning it into a verb-led next action such as “Ring Aviva about combining the two old workplace pensions”. It stops being useful the moment it starts deciding priority or inventing context it cannot know, which is the line I draw in the six GTD jobs ChatGPT handles well. Metadata, likewise: a context tag, a project link and a waiting-for date all belong here, where you have time to think.

Choosing the Setup That Fits Your Devices

iPhone plus Mac: lock screen Shortcut for mobile, launcher-fired URI on the desktop. Add Drafts only if it is already in your stack.

Android plus Windows: a capture app in front of the vault, plus a hotkey on the desktop. No Shortcuts, so the paid app earns its keep here more than anywhere else.

iPad first: built-in Quick Capture or a Shortcut on the Slide Over, and accept that typing speed rather than launch speed is your constraint. The iPad note-taking picks go into that in more detail.

Mixed work and personal machines: keep capture identical on both and let clarify split the streams. Do not run two inboxes.

On Obsidian vs Notion: a database-first tool gives you structure at capture and charges you in speed, because it wants a page in a database with properties filled in. Obsidian gives you a file in seconds and charges you in structure, because you must impose it later. Neither is wrong; the trade-off is just the one in the real costs of switching between them. If your captures are mostly half-sentences, speed wins.

Run one route for a week. Count the thoughts you lost, honestly, including the ones you meant to type and did not. Keep it or swap it before you add anything clever. If you want the underlying habit rather than the plumbing, read the sub-five-second capture piece next, then come back and wire up whichever Obsidian quick capture route survived your week.

Frequently Asked Questions

Does Obsidian have a built-in quick capture feature?

Yes, on mobile, through Quick Capture with Locations, which can send text to a new note, today’s daily note, a bookmarked note or a note you choose. It has been rolling out via early access builds (1.14 onwards at the time of writing), so check the current release notes for your platform. On desktop, the nearest equivalent is a global hotkey, usually via the QuickAdd community plugin or the obsidian:// URI scheme.

What is the fastest way to capture a note to Obsidian on a phone?

On iPhone, a lock screen or widget Shortcut that dictates a thought and writes a timestamped markdown file into your Inbox folder, which typically takes about five seconds end to end. On Android, a small capture app that opens straight to a text field does the same job. Both beat launching the full app, because they skip the vault indexing step.

Should quick capture go to the daily note or a separate inbox note?

Separate files in an Inbox folder, one per capture. Appending to a shared daily note from two devices across a syncing folder is the standard route to conflicted copies, and a conflict file is one you will never open again. If you prefer the daily note for review purposes, collect the inbox files into it during clarify instead.

Do you need Obsidian Sync for quick capture to work across devices?

No. ICloud Drive, Dropbox-style folders and other sync services all work, and Obsidian Sync is a paid convenience rather than a requirement. What matters is that your capture route writes separate files, because that is what survives two devices syncing at once regardless of which service is underneath.

Should tasks be captured in Obsidian or sent to a task manager?

Capture wherever is fastest, then split during clarify. Reference material and project support notes stay in the vault; anything with a next action should end up on a list you review in context, such as OmniFocus, Things or Todoist. Keeping actions in the vault works for a while and then quietly stops, usually around the point you have a few hundred notes.