Keyboard Shortcuts
Copy, tabs, screenshots and the rest — both operating systems in one searchable table.
Two systems, one table
Windows and macOS use different modifiers for the same idea: Control against Command, Alt against Option. Showing them side by side is faster than two separate pages, and it makes the pattern obvious.
The ones worth learning
Copy, paste, undo, tab switching and screenshots cover most of the time a shortcut saves. The list is short for that reason — a hundred shortcuts nobody remembers help nobody.
Browser and system
Shortcuts marked as browser ones work in Chrome, Edge and Firefox. The system ones are current Windows 10/11 and macOS; older versions differ in a few places.
Good to know
Screenshots differ more than anything else on the list: Windows has Win+Shift+S, macOS has three separate combinations depending on whether you want a window, a selection or the whole screen.
Learning three shortcuts properly beats skimming thirty. Copy, undo and switching tabs save more time than everything else on this page put together.
On a laptop with a compact keyboard, some combinations need Fn held as well, which is why a shortcut that works on a desktop can appear broken on a small machine. Testing one key combination at a time is the quickest way to find out.
How Keyboard Shortcuts works
A searchable list of the shortcuts people actually use, side by side for Windows and macOS. The method behind Keyboard Shortcuts is the single-purpose logic inside wave55.js, and this page shows the result with its assumptions in the open.
- Open Keyboard Shortcuts and provide keyboard shortcuts — the page accepts it in the field it shows.
- For Keyboard Shortcuts, parsers and formatters run as JavaScript on the text you paste.
- The Keyboard Shortcuts output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.
A worked example for Keyboard Shortcuts
A typical run of Keyboard Shortcuts starts with keyboard shortcuts and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.
Paste a payload you know is valid, then break it deliberately — the error message should point at the exact line, which is the difference between a formatter and a black box. That check applies directly to Keyboard Shortcuts with keyboard shortcuts.
When to use Keyboard Shortcuts — and when not to
Reasonable uses: Reading an API response; Checking a config file before committing; Comparing two payloads. Keyboard Shortcuts is deliberately narrow: it does one job and states its assumptions instead of hiding them.
Editor extensions do this inside a project; they cannot help with a snippet from a ticket. A page that parses in isolation is the right tool for pasted text. The honest ceiling for Keyboard Shortcuts: for Keyboard Shortcuts, parsing happens in the tab, so huge files can stutter.
- Best case for Keyboard Shortcuts: Reading an API response
- Also fine with Keyboard Shortcuts: Checking a config file before committing
- Not what Keyboard Shortcuts is for: for Keyboard Shortcuts, parsing happens in the tab, so huge files can stutter.
Reading the Keyboard Shortcuts result
The output of Keyboard Shortcuts is a function of the inputs alone — no hidden state and no server.
Accuracy and limits of Keyboard Shortcuts
The method is the single-purpose logic inside wave55.js. Keyboard Shortcuts prints results at the precision its inputs justify, and the limits below are the honest ones:
- Keyboard Shortcuts: For Keyboard Shortcuts, parsing happens in the tab, so huge files can stutter.
- For Keyboard Shortcuts, no validation against a schema unless the page says so.
Privacy and speed on the Keyboard Shortcuts page
The Keyboard Shortcuts page is a static file plus wave55.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.
Speed follows the build: Keyboard Shortcuts loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.
What you get from Keyboard Shortcuts
The output of Keyboard Shortcuts appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the developer work finishes the moment the numbers are in.
Because Keyboard Shortcuts is built from wave55.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.
Questions
What does Keyboard Shortcuts do?
A searchable list of the shortcuts people actually use, side by side for Windows and macOS. Everything runs in your browser; nothing is uploaded.
How accurate is Keyboard Shortcuts?
The method is the single-purpose logic inside wave55.js. For Keyboard Shortcuts, parsing happens in the tab, so huge files can stutter.
What are the limits of Keyboard Shortcuts?
For Keyboard Shortcuts, no validation against a schema unless the page says so.
Is anything uploaded when I use Keyboard Shortcuts?
No. Keyboard Shortcuts runs entirely in the browser tab; nothing is uploaded, stored or logged.
Can I use Keyboard Shortcuts offline?
Yes — Keyboard Shortcuts keeps working offline once the page has loaded; the whole tool is a local script.
Keep going
More developer tools
Keyboard Symbols
Every symbol on a keyboard and the key combination that types it, including Alt codes and the layout differences.
Open toolJSON Formatter
Format, validate and minify JSON with precise error messages. Everything runs locally in your browser.
Open toolASCII Table
The full ASCII table with decimal, hex, character and the name of every control code.
Open tool