Keyboard Shortcuts Reference
Web Developer ToolsReference for common keyboard shortcuts across OS and apps
General
Editing
Multi-cursor
Navigation
Search
View
How to Use This Tool
Enter your input
Type or paste the value you want to look up or convert into the input field.
Get instant results
Results are computed immediately in your browser — no network request needed.
Use the reference
Browse the built-in reference table to find related values, codes, or descriptions.
Copy what you need
Use the "Copy" button to grab any value from the results for use in your project.
About This Tool
Keyboard Shortcuts Reference is a free, instant, browser-based tool that reference for common keyboard shortcuts across os and apps. Web developer tools provide quick access to reference data and small utilities that come up constantly during development. HTTP status codes, Unix timestamps, chmod permission calculators, ASCII tables, and similar references are things every web developer looks up regularly. Having them in one place, instantly accessible in your browser, speeds up your workflow significantly.
This tool runs entirely in your browser with no server calls required. Results appear instantly and everything works offline once the page is loaded.
Bookmark this page for quick access during development sessions. Whether you're debugging a 403 vs 401 response, converting a timestamp from a database field, setting file permissions on a Linux server, or checking what ASCII character code 127 corresponds to, having a reliable, distraction-free reference tool cuts down the time you spend looking things up and lets you stay focused on the problem at hand.
Keyboard Shortcuts reference provides a searchable list of shortcuts for popular tools and operating systems. Memorizing key shortcuts dramatically improves productivity in IDEs, terminals, design tools, and browsers.
Why Use This Tool?
Keyboard Shortcuts reference provides a searchable list of shortcuts for popular tools and operating systems. Memorizing key shortcuts dramatically improves productivity in IDEs, terminals, design tools, and browsers.
Common pitfalls and gotchas
The mistakes that come up repeatedly when working with web developer tools tools — most of them invisible until they cause production failures or silent data corruption.
Treating reference data as immutable forever
HTTP status codes, MIME types, and CSS units evolve. New status codes (425 Too Early, 451 Unavailable for Legal Reasons) get added; new MIME types appear for new file formats. Reference data baked into client code at build time can drift from current standards over years. Pin to a versioned reference and update on a regular cadence.
Confusing user-agent strings with reliable device detection
User-agent strings are spoofable, parseable but not authoritative, and increasingly being frozen or randomized by browsers (Chrome's User-Agent Reduction). Don't make security decisions based on UA detection. For feature detection, use real feature checks (`if ('IntersectionObserver' in window)`) rather than UA strings.
Hardcoding timestamps in local time
Timestamps stored as local-time strings without timezone information are unrecoverable when the codebase moves servers, when users span timezones, or when daylight-saving transitions create ambiguity. Always store timestamps as Unix epoch seconds (UTC) or ISO-8601 with explicit timezone offset.
Frequently asked questions
Are these references kept up to date?
Yes — we update reference data when standards change. HTTP status codes, MIME types, CSS units, and similar references reflect current specifications. If you spot something outdated, please email support and we'll fix it.
Can I rely on these tools for production decisions?
These tools are reliable references for routine work — looking up status codes, parsing user agents, converting timestamps. For high-stakes decisions (security configurations, compliance claims), cross-reference with the underlying RFCs and W3C specifications, which are the authoritative sources.
Will these tools work offline?
Once the page is loaded, most tools work offline — they run entirely in your browser. You can use them on a flight or in any environment without internet access after the initial page load. Refreshing the page may require connectivity.
Why is my browser showing different viewport dimensions than expected?
Browsers apply zoom level, system DPI scaling, and developer tool overlays that affect reported dimensions. The tool reports what the JavaScript runtime sees — which is what your CSS media queries also see. If a discrepancy exists, check zoom (Ctrl+0 to reset) and any open dev tool panels.
Related Tools
HTTP Status Codes
Reference for all HTTP status codes with descriptions
MIME Type Lookup
Look up MIME types for file extensions
User Agent Parser
Parse browser user agent strings into readable info
Timestamp Converter
Convert Unix timestamps to human-readable dates and back
Cron Parser
Parse and explain cron expressions
Chmod Calculator
Calculate Unix file permissions in octal and symbolic notation