Skip to content
got.md?

Obsidian Command Palette: how to use it fast, pin favorites, and fix missing commands

Obsidian starts feeling powerful the moment you stop hunting through panes and start issuing commands.

That is what the Command palette is for.

It is not just a search box. It is Obsidian's control layer:
one place to run commands, discover features, surface plugin actions, and remind yourself which commands deserve real hotkeys.

The official docs describe the Command palette as a core plugin that lets you run commands from the keyboard, supports fuzzy matching, and lets you pin commands. But that is only the beginning. The real unlock is knowing when to use the palette, when to use Quick Switcher, when to use Slash commands, and when to graduate a command into a hotkey.

Obsidian Command Palette quick links

Quick answer

If you only need the short version:

  1. Open the Command palette with Ctrl+P on Windows/Linux or Cmd+P on macOS, or use the ribbon icon.
  2. Use it for commands across the app: toggles, views, note actions, plugin commands, and one-off workflows.
  3. If you run a command constantly, turn it into a hotkey.
  4. If you are opening or creating notes by name, use Quick Switcher instead.
  5. If you want to run commands without leaving the editor line, use Slash commands.

Screenshot: the Command palette open on desktop with 2 pinned commands, a few recent commands, and visible hotkeys on the right. This matters because readers need one immediate mental picture of what the palette actually is before the rest of the guide becomes useful.

How to open the command palette in Obsidian

The Command palette is a core plugin.

On desktop, the fastest path is:

You can also open it from the ribbon.

If the ribbon is missing, check Settings -> Appearance -> Show ribbon. The official ribbon docs also note that community themes or custom CSS can hide it, so that is worth checking before you assume the feature disappeared.

On mobile, there are 3 common ways to reach it:

If the palette does not open at all, first confirm the core plugin is enabled under Settings -> Core plugins.

What the command palette is actually for

Think of the Command palette as the place for verbs.

Not notes.
Not search results.
Not text snippets.

Verbs.

Examples:

This is why the Command palette stays useful even after you know Obsidian well.

You may forget where a button lives.
You may never bother memorizing a rarely used hotkey.
You may install a new plugin and have no idea where its commands show up.

The palette solves all 3.

Search faster with the palette

The official docs note that the palette uses fuzzy matching. That matters because you do not need the exact command name.

A practical search pattern:

Also note one subtlety from the official docs: recent commands can appear near the top, but once you start typing, shorter and stronger fuzzy matches can outrank them.

That is one reason not to over-rely on recency alone.

Command palette vs Quick Switcher vs Slash commands vs Hotkeys

This is the main blindspot in most Command palette content.

The tools are related, but they are not interchangeable.

Tool Best for Default entry point Mental model
Command palette running commands across the app Ctrl/Cmd+P verbs
Quick Switcher opening or creating notes by name Ctrl/Cmd+O notes
Slash commands running commands from inside the editor / in editor in-place insertions and editor actions
Hotkeys repeated commands you use constantly custom muscle memory

Use this simple rule:

That one distinction removes a lot of friction.

When to graduate from palette to hotkey

The Command palette is not a replacement for hotkeys.
It is the bridge to them.

The official Hotkeys page even says the fastest way to see whether a command already has a hotkey is to look it up in the Command palette.

A simple operating rule:

Use the palette to discover a command.
If it becomes part of your daily loop, bind a hotkey.

That is the clean path.
You do not need to memorize the entire app on day one.

Best commands to learn first

The winning move is not "learn every command."

It is "learn the commands that change how you use Obsidian."

Here is a starter set that has outsized leverage:

Command Why it matters Notes
Create new note fastest universal capture move also available from Manage notes
Open Quick Switcher jumps to notes faster than browsing folders better for note lookup than the palette itself
Add file property turns notes into structured records fast official Properties command
Bookmark / Bookmark heading under cursor / Bookmark block under cursor creates shortcuts to important notes, headings, and blocks see Bookmarks
Open graph view / Open local graph fast visual context without menu hunting useful when exploring related notes
Manage workspace layouts save and switch between writing, planning, review, and research layouts see Workspaces
Canvas: Create new canvas quick visual workspace creation see Canvas
Bases: Create new base fastest way to start a database-like view see Create a base
Create new unique note low-friction Zettelkasten-style capture requires Unique note creator
Insert Table faster than typing a starter table manually see Advanced formatting syntax
Open sandbox vault safest troubleshooting and learning environment built-in desktop troubleshooting path in Sandbox vault

The most useful command families

If you want to discover more without drowning in options, search these words inside the palette:

That is a better discovery strategy than randomly scrolling.

The command palette as a discovery layer

Official docs are spread across many pages.

The Command palette lets you stumble into features you would otherwise miss.

Examples:

That is why the palette is such a strong beginner page for got.md:
it helps people discover capability without needing them to memorize the entire app.

How to pin commands in Obsidian

The official workflow is simple:

  1. Open Settings
  2. Go to Command palette
  3. Next to New pinned command, select a command
  4. Press Enter

Official doc: Command palette

Screenshot: Settings -> Command palette with the pinned commands list and the "New pinned command" selector visible. This matters because pinning is one of the first durable upgrades most users should make.

What to pin first

Pin commands that are:

Good first pins:

Important nuance: pinning is not the same as hotkeys

Pinning helps you before you type.

Hotkeys help you skip the palette entirely.

There is also a real-world limitation worth knowing: once you start filtering, pinned commands do not always stay at the very top of the matching results. If you need absolute reliability for a command, a hotkey is better than hoping search ordering always behaves the way you want.

For that reason:

A better way to think about pins

Do not pin commands because they are "important."

Pin commands because they save hesitation.

Good pin categories:

Obsidian command palette on mobile

Mobile is where a lot of confusion happens.

The official Mobile app docs say Quick Action defaults to opening the Command palette when you pull down from the top of the app.

That means two things:

The same docs also note that you can:

So the clean mobile setup is:

  1. Keep Quick Action mapped to Command palette if you want one-gesture access
  2. Add 1 or 2 global commands to the mobile toolbar if you need them often
  3. Use the mobile menu for ribbon actions when you are not editing

Screenshot: the mobile Quick Action settings page with Command palette selected. This matters because many "I lost the command palette" problems on mobile are really Quick Action configuration problems.

Mobile rule of thumb

On mobile:

That separation keeps mobile usable.

Obsidian command palette not working

When the Command palette feels broken, the fix is usually simpler than it seems.

1) Make sure the core plugin is enabled

The Command palette is a core plugin.

If it does not open at all, check:

2) If the ribbon icon is missing, check the ribbon itself

The official Ribbon docs say the ribbon can be hidden in Settings -> Appearance -> Show ribbon.

They also explicitly warn that community themes or custom CSS can hide the ribbon.

So if the icon is gone:

3) If the full list looks wrong, test with plugins off

A high-signal forum thread shows a case where the Command palette looked truncated until the user turned on Restricted Mode, which disabled community plugins and restored the full list.

So if the palette suddenly looks incomplete:

If that fixes it, the issue is probably plugin or theme interference, not the core palette itself.

4) Use the Sandbox vault to isolate the problem

The official Sandbox vault exists for exactly this kind of debugging.

Use it when you need to answer:

If the palette works in the sandbox, the problem is probably local to your vault setup.

Obsidian command palette missing commands

This is the most important troubleshooting section on the page.

Most "missing commands" are not missing.
They are context-dependent.

1) Check your current mode first

A useful forum example: a user could not find Tasks plugin commands until they switched from reading mode to editing mode.

That is not unusual.

Some commands only appear when:

So if a command exists in Hotkeys or docs but not in the palette, first try:

2) Confirm the relevant plugin is enabled

This applies to both core and community plugins.

Examples:

3) Remember that some commands are view-specific

The Obsidian developer docs note that editor commands only appear in the Command palette when there is an active editor available.

So if you search from the wrong pane, a command can appear to "not exist."

That is especially common with:

4) If a command is still missing, search more specifically

Search patterns that help:

For example:

Can the command palette delete notes?

Yes.

The official Manage notes docs explicitly mention Delete current file as a Command palette action.

If that makes you nervous, configure what "delete" means under Settings -> Files & Links:

For almost everyone, system trash or Obsidian trash is the sane default.

That one setting turns a scary command into a recoverable one.

Can the command palette create notes and structures?

Yes, and this is one of the best reasons to use it.

Examples from official docs:

That is why the palette is more than navigation.
It is a creation surface.

Command palette for plugin users

Once you install plugins, the Command palette becomes even more important.

Why?

Because plugin UIs are inconsistent.
Some live in sidebars.
Some add ribbon icons.
Some add context menus.
Some are almost invisible unless you know the exact command name.

The palette becomes your universal fallback:

That is the cleanest way to adopt plugins without turning Obsidian into a scavenger hunt.

Advanced move: Command palette as the human layer, CLI/URI as the automation layer

If you go beyond manual use, Obsidian now has two official automation surfaces worth knowing:

That gives you a clean mental model:

For advanced users, that is where the palette story gets bigger than "Ctrl+P."

FAQ: Obsidian command palette

What is the shortcut for the Obsidian Command palette?

By default, it is Ctrl+P on Windows/Linux and Cmd+P on macOS. See the official Command palette docs.

Is the Command palette a core plugin?

Yes. It is listed in Obsidian's official Core plugins.

What is the difference between Command palette and Quick Switcher?

Use the Command palette to run commands. Use Quick Switcher to open or create notes by name.

Why are commands missing from the Command palette?

Usually because the command is context-dependent, the relevant plugin is not enabled, or you are in reading mode instead of editing mode. Test the command again with an active editor and the correct plugin enabled.

Can I pin commands in Obsidian?

Yes. Open Settings -> Command palette and add them under pinned commands. Official steps are on the Command palette page.

Can I use the Command palette on mobile?

Yes. The official Mobile app docs say Quick Action defaults to opening the Command palette when you pull down from the top.

Should I use the palette or make a hotkey?

Use the palette first. If a command becomes part of your daily loop, promote it to a hotkey.

Can plugin commands appear in the Command palette?

Yes. The official Obsidian CLI docs note that command-related CLI actions include commands registered by plugins.

Can I automate Obsidian commands?

Yes. For official routes, look at Obsidian CLI and Obsidian URI.

Related pages

References

Official:

Community + supporting reading: