A useful shortcut sheet is short, personal to your workflow, and specific about the application. A long list copied from another operating system is harder to trust than six commands you have checked.
Start with a few documented examples
Download the editable shortcut CSV. Its example rows are source-checked against official references, not claimed as device-by-device execution tests.
| Action | Windows | macOS | Scope |
|---|---|---|---|
| Copy | Ctrl-C | Command-C | Selected content in a supporting app |
| Paste | Ctrl-V | Command-V | Current insertion target |
| Find | Ctrl-F | Command-F | Current app, document, or page |
| Reopen closed Chrome tab | Ctrl-Shift-T | Command-Shift-T | Chrome normal browsing context |
The platform modifier is not interchangeable. A website, remote desktop session, accessibility setting, or application can intercept a shortcut.
The CSV deliberately keeps official source and source-check date separate from tested application/version, tested platform, test date, and observed result. Its documented examples have the software-test fields blank. Put “not run” in your own test status until you actually press the keys in that named application. A URL in a source column is evidence for documentation, not a test environment.
Add only recurring actions
For one workday, note the actions you repeat: finding text, moving between fields, opening a recent tab, or saving a draft. Choose a few harmless actions to verify first. Leave destructive commands off the initial learning sheet.
Add columns for application, platform, key combination, expected result, and the date you actually checked it. An official reference supports the documented command; your own test establishes how it behaves in your setup.
Test with disposable content
Open a practice text file, select a word, copy it, and paste into another blank practice file. Confirm the insertion point before pressing Paste. For Find, search for a known word and check the scope. For tab recovery, close only a harmless public page.
If the result differs, inspect focus and application scope before changing key bindings. A shortcut can be correct while focus is in the wrong control. Do not test an unfamiliar command against unsaved important work.
Keep the sheet readable
Write key names consistently, such as Command rather than mixing symbols and abbreviations without a legend. Group by task, not by alphabet. Keep Windows and macOS in separate columns so a quick glance does not combine their modifiers.
Mark an untested custom shortcut as unverified. Remove a row if an app update or workflow change makes it misleading. The reference succeeds when it helps you perform a few checked actions reliably, not when it contains the most commands.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- Keyboard shortcuts in Windows
Windows copy, paste, find, undo, and rename shortcuts; app behavior varies. - Mac keyboard shortcuts
Command-based Mac copy, paste, find and undo shortcuts; application scope matters. - Chrome keyboard shortcuts
Restore a closed tab with Ctrl+Shift+T or Command+Shift+T.