Keyboard Shortcut Reference
Quick reference for keyboard shortcuts in VS Code, Terminal, Git, Vim, and Chrome DevTools.
How it works
- 1Configure your options above
- 2Click "Show Shortcuts" — processing happens in your browser
- 3Copy or download the result
What to do next
About Keyboard Shortcut Reference
Keyboard Shortcut Reference is the kind of utility you bookmark and reach for when you need it. Quick reference for keyboard shortcuts in VS Code, Terminal, Git, Vim, and Chrome DevTools. It loads quickly, works on any modern browser, and produces a result you can download or copy in a single click.
Under the hood, Keyboard Shortcut Reference uses standard browser APIs to do the actual work. Input runs through the same engine, with a per-file ceiling of 0 MB so memory usage stays predictable on lower-end laptops and tablets. The engine ships as part of the page bundle, so once the page is loaded the tool keeps working even if your network connection drops.
Keyboard Shortcut Reference works well as a bookmarked utility you reach for when you need it. The first visit shows you what the tool does; the second is when you realise it is a low-friction option for the task and worth keeping in your tab list.
The execution model is straightforward: your file is bytes in the tab's memory, the engine reads those bytes, computes the result, and hands the result back to the browser. The transformation happens locally, which is why the tool keeps working when your network connection drops mid-job and why it produces the same result every run for the same input.
The hard constraints are easy to remember. Maximum input: 0 MB. Multiple files per run: no — one input at a time, by design, to keep results predictable. The same controls apply on every run.
If your task needs more than one step, chain Keyboard Shortcut Reference with HTTP Methods Reference, REST API Design Checklist, and ANSI Color Code Reference. Each tool produces output that is a clean input to the next, so multi-step workflows are just a matter of opening the next tool in a new tab and continuing.
Keyboard Shortcut Reference sees the most use from engineers debugging API payloads and students learning new languages, but the design is intentionally generic enough that you do not need a specialist background to get a good result. The defaults aim at the most common case so a first-time user can get the right output without changing any settings.
Once the engine finishes, the output is offered as an immediate download. There is no preview gate, no email-wall, and no "register to download" intermediary — the file is yours the moment it is ready.
Keyboard Shortcut Reference is honest about scope: it handles a single, well-defined developer utility step. Specialist edge-case work — uncommon formats, very large inputs, or pipelines that need scripting — is what dedicated desktop apps are for. This page handles the common case quickly.
Keyboard Shortcut Reference is structured around the idea that a useful tool should be its own page. Open the page, do the work, close the tab — the page is the entire product. There is no onboarding flow because there is nothing to onboard into.
Tips from users who reach for Keyboard Shortcut Reference regularly: process one input first to confirm the settings produce what you expect before committing to a batch; treat the page as the working surface and avoid leaving large jobs running in a backgrounded tab where the browser may throttle JavaScript; and if a particular file fails, check whether the source is intact by opening it in its native viewer — most "tool errors" are actually input errors.
Keyboard Shortcut Reference runs as a regular web page, so there is no install step or permission grant before the first run. The page can be audited by viewing the source or by watching the developer-tools Network tab while a job runs.
When something goes wrong, the cause is usually one of three things: a malformed input, a browser that is out of memory, or a corporate proxy that is interfering with the page's static assets. The first two are easy to diagnose; the third typically requires asking your IT team to allow standard browser APIs to load.
That is the whole tool. Use Keyboard Shortcut Reference for as long as it stays useful to you, and if it does, the catalog has many more tools built the same way. Each applies the same single-purpose discipline, so the way you used this page transfers to the next one you try.
How it works
- 1Open Keyboard Shortcut Reference in your browser. The page loads quickly and the tool is ready to use the moment it becomes interactive.
- 2Add your developer input by dropping it onto the page or browsing for it.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Hit the run button. standard browser APIs does the work in your browser tab.
- 5Save the output when it is ready.
- 6Re-run with different settings as often as you want. Each run produces a fresh output and the original file on disk is never modified.
Common use cases
- Decode a token to confirm its claims during a debugging session using Keyboard Shortcut Reference.
- Convert between data formats while wiring up an integration.
- Format a noisy log line into something a teammate can read.
- Inspect a payload during local development without writing a script.
- Compare two API responses to spot a regression.
- Hash a string for a quick reproducibility check.
- Generate boilerplate from a single specification line.
- Encode binary content for transport in a JSON body.
- Inspect a regex against a test string before committing it.
FAQ
Mac vs Windows?
Shortcuts show Cmd/Ctrl to cover both platforms; substitute Command on Mac or Control on Windows.
Custom keybindings?
These are default shortcuts; check your editor settings for customized bindings.
Which apps?
VS Code, Terminal (Bash/Zsh), Git commands, Vim, and Chrome DevTools.
Private?
Yes — generated locally.
Printable?
Copy the text output and paste into a document for printing.
Missing shortcuts?
This covers the most common shortcuts; refer to official documentation for comprehensive lists.
Does Keyboard Shortcut Reference have an API?
Keyboard Shortcut Reference is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (standard browser APIs) is open-source and can be used directly from your own code.
Does Keyboard Shortcut Reference require a browser extension or plug-in?
No installation is needed. Keyboard Shortcut Reference runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Keyboard Shortcut Reference on any computer you have temporary access to without leaving anything installed on it.
Will I notice a difference in the output from Keyboard Shortcut Reference?
Keyboard Shortcut Reference is built to preserve quality wherever the underlying developer format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
What is the maximum file size for Keyboard Shortcut Reference?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Keyboard Shortcut Reference as often as you need; every run produces a full-quality result.
What does the error message in Keyboard Shortcut Reference mean?
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is in a supported format and that it is below 0 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Is Keyboard Shortcut Reference licensed for business use?
Keyboard Shortcut Reference can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Will Keyboard Shortcut Reference keep working if my Wi-Fi drops mid-task?
Once the page is loaded, Keyboard Shortcut Reference can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
Does Favtoo keep a copy of files I process with Keyboard Shortcut Reference?
Favtoo keeps no copy of your file because Favtoo never receives your file. Keyboard Shortcut Reference runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.