Coda Keyboard Shortcuts
Coda's shortcuts split between document-editing actions inherited from a typical rich-text editor and table-specific actions that behave more like a database or spreadsheet, reflecting its blended identity as both a writing surface and a structured data tool within the same canvas. The slash-command system for inserting new elements is central to how Coda users actually build a doc day to day, similar in spirit to Notion's approach but with Coda's own specific command set geared toward its table and formula-heavy use cases. Coda's command palette (Cmd+/ on Mac, Ctrl+/ on Windows) is worth learning early since it exposes nearly every doc and table action by name, sidestepping the need to memorize individual bindings for less-frequent table operations. Packs, Coda's system for connecting external services (like Slack, Google Calendar, or Jira) directly into a doc's tables and buttons, extend the platform well beyond a self-contained document tool into something that can pull and push live data across a team's other tools, though wiring up a Pack integration means walking through that service's own authentication and configuration screens inside Coda's settings panel, a one-time setup task with too many moving parts for any single keystroke to replace. Because Coda blends the mental models of a document, a database, and a spreadsheet in one canvas, new users often need longer to find their footing than with a purely single-purpose tool, but that same flexibility is why teams sometimes consolidate several previously separate tools' functionality into fewer Coda docs.
Doc Editing
| Action | Windows | Mac | Description |
|---|---|---|---|
| Open slash command menu | / | / | Typing a forward slash at the cursor opens a searchable menu of insertable elements — tables, buttons, formulas, page links — Coda's primary mechanism for building out a doc's structure beyond plain text. |
| Bold selected text | Ctrl+B | Cmd+B | Applies bold to the current text selection inside a Coda doc canvas. Because a Coda doc mixes free-form rich text with embedded tables and formulas on the same page, this same bold shortcut also works on text typed into a table cell, applying consistent character-level formatting regardless of whether the cursor sits in the document body or inside a structured table row. |
| Create new page | Ctrl+Shift+N (varies) | Cmd+Shift+N | Adds a new page to the current doc's page hierarchy, Coda's structural unit roughly analogous to a tab or sub-document within a larger workspace doc. |
| Link to another page | Type @ followed by page name | Type @ followed by page name | Typing the @ symbol opens a search for pages, people, or dates to reference, inserting a live link — a convention shared loosely with Notion's @-mention system. |
| Insert a Pack integration | / then type Pack name | — | Inserts a connected Pack element (like a Slack notification button or a Google Calendar view) via the same slash-command menu used for other content, extending the doc beyond self-contained content into live integration with external services. |
| Italicize selected text | Ctrl+I | Cmd+I | Italicizes the current selection anywhere on a doc's rich-text canvas, unaffected by whatever table or structured element happens to be sitting nearby on the same page. |
Table Actions
| Action | Windows | Mac | Description |
|---|---|---|---|
| Add new row to table | Enter (at bottom row) or Ctrl+Enter | Return or Cmd+Return | Pressing Enter while positioned in the last row of a table creates a new empty row directly below, mirroring how spreadsheet row creation typically behaves. |
| Delete selected row(s) | Right-click row, Delete — no universal single key | Same | Deleting a table row requires right-clicking it and choosing Delete Row from the context menu, since Coda doesn't bind row deletion to a single default keyboard shortcut to avoid accidental data loss. |
| Edit a column's formula | Click column header, then formula bar | Same | Editing the underlying formula that computes a formula column's values requires clicking into the column header's formula bar, rather than a keyboard shortcut, given how substantial a formula edit typically is. |
| Filter a table view | Table view > Filter icon | — | Applies a filter condition to a table view, narrowing visible rows without altering the underlying data, useful for focusing on a specific subset like only incomplete tasks. |
| Sort table by column | Click column header dropdown > Sort | Same | Sorting a table view ascending or descending by a specific column is triggered from that column header's dropdown menu rather than a keyboard shortcut, applying only to the current view without altering the underlying stored row order. |
Navigation
| Action | Windows | Mac | Description |
|---|---|---|---|
| Open global search | Ctrl+K | Cmd+K | Opens a universal search across docs, pages, and workspace content, similar in spirit to Notion's and ClickUp's command-style search bars. |
| Navigate back | Alt+Left | Cmd+[ | Returns to the previously viewed page or doc, following standard browser-style back navigation conventions within Coda's own internal navigation history. |
| Duplicate the current doc | Doc menu > Make a copy | — | Creates a full copy of the current doc, including its tables and formulas, useful for turning a built-out template into a reusable starting point for future similar projects. |
Frequently Asked Questions
How is Coda's slash command different from Notion's?
Both use a forward-slash trigger to insert elements, but Coda's menu leans heavily toward its structured-data building blocks (tables, formulas, buttons that trigger actions) reflecting its database-app hybrid identity, whereas Notion's slash menu is comparatively more oriented toward content blocks for writing and basic page structure.
Why isn't there a single keyboard shortcut to delete a table row?
Row deletion is a destructive, often irreversible action affecting structured data that other parts of the doc might reference via formulas or lookups, so Coda requires the more deliberate right-click confirmation flow rather than a single keystroke that could be triggered accidentally.
Can buttons in Coda be triggered by keyboard shortcuts?
Not by default — Coda's button elements (which can run actions like adding a row, sending a notification, or modifying data) are click-triggered UI elements within the doc itself, without a built-in mechanism for assigning them to a global keyboard shortcut the way a desktop application's custom hotkeys might work.
What are Packs, and do they require technical setup to use?
They're Coda's plug-ins for pulling in outside services — Slack, Google Calendar, Jira, and dozens of others — so a table or button in your doc can read from or write back to that service directly. Grabbing a ready-made Pack from Coda's gallery and pointing it at your account is mostly a settings-panel job anyone can do; only building a brand-new Pack from scratch, rather than using an existing one, actually requires developer-level setup.
Is Coda harder to learn than a simpler tool like Notion or Airtable alone?
A little, yes — you're learning three mental models at once (document, database, spreadsheet) instead of just one, so the first week or two feels less immediately intuitive than opening a plain doc editor. What you get in exchange is the ability to fold several previously separate tools into a single Coda workspace, which is the actual reason most teams decide the initial learning curve is worth climbing.
Does filtering a table view change the actual underlying data?
No — filtering only affects which rows are currently visible in that specific view; the underlying table data remains fully intact and unaffected, so switching to an unfiltered view or removing the filter later reveals all rows exactly as they were before filtering was applied.
Does sorting a table view change the actual stored order of rows?
No — sorting affects only how that specific view displays existing rows; the underlying table data and any other views built on the same table remain unaffected, so a differently sorted or filtered second view of the same table can coexist without conflicting with the sort order applied elsewhere.