How to Test If Function Keys Are Working
To test if your function keys are working, check every key from F1 through F12 in a keyboard tester, then repeat the row while holding Fn. Also confirm any brightness, volume or other system action on the device itself. This comparison matters because a browser can detect many F-key events, but the keyboard, operating system or browser may handle some actions before the page sees them.
Quick function key test
- Save open work because some function keys can refresh a page, change volume or trigger another shortcut.
- Open the function key test and click inside its test area.
- Press F1, F2 and each remaining key through F12 one at a time.
- Record the keys that highlight and any browser or system action that occurs.
- Hold Fn and repeat F1–F12, checking whether the result changes.
- Retest any missing key in another application, such as a plain text editor or the keyboard viewer supplied by your operating system.
A highlight confirms that the page received a keyboard event for that function key. No highlight does not automatically mean the physical key is broken: the browser or operating system may reserve the shortcut, or the top row may currently be set to media controls.
How to check every F1–F12 key
Work from left to right so it is easy to notice a gap. Press and release each key once rather than holding several keys together. If an action moves focus away from the test, return to the test area before continuing.
Use a small results table while testing:
| Physical key | Without Fn | With Fn | What to check |
|---|---|---|---|
| F1 | Browser event or Help | Alternate action | Did either result occur? |
| F2 | Browser event or app command | Alternate action | Compare in a second app |
| F3–F4 | Browser event, search or system action | Alternate action | Note what actually changed |
| F5 | Browser event or refresh | Alternate action | Save work before testing |
| F6–F10 | Browser event, focus or media action | Alternate action | Refocus the tester as needed |
| F11 | Browser event or full screen | Alternate action | Exit full screen before continuing |
| F12 | Browser event or developer tools | Alternate action | Close any panel that opens |
The exact action varies by operating system, application and keyboard model. The useful evidence is whether the physical key consistently produces its configured result, not whether every computer assigns the same shortcut to it.
Test the Fn layer separately
Laptop and compact-keyboard top rows commonly have two layers: F1–F12 and media or system controls. Depending on the current setting, a plain top-row press may change brightness or volume, while Fn plus that key sends F1–F12. Another device may use the opposite arrangement.
Test both states and compare them with the legends printed on the keys. If holding Fn reliably switches between the two intended actions, that is evidence that the Fn layer is responding even when Fn itself never appears in the browser tester.
If the row works in the wrong mode, look for a marked Fn Lock key or a manufacturer setting. Do not assume one universal shortcut: the method varies by model. The Fn key troubleshooting guide explains how to compare firmware, operating-system and vendor settings.
How to interpret the results
| Test result | What it usually shows | Next check |
|---|---|---|
| All F1–F12 keys highlight | The browser received each F-key event | No further browser test is needed |
| A system action works but no key highlights | The action may be handled before the page | Confirm the same action twice and check the device guide |
| A key works only while holding Fn | The top row is using its alternate layer | Check Fn Lock or function-row preferences |
| One key fails in both modes | The problem may involve that key or its mapping | Try another app and, if possible, another computer |
| The whole row fails | A mode, remap, utility or connection issue is more likely than 12 simultaneous switch failures | Reconnect, review settings and compare another keyboard |
| A key fires more than once | The key may be chattering or software may be repeating it | Use the double typing test |
Repeat an unexpected result before changing settings. A single missed event can come from lost focus, a page navigation or an operating-system shortcut. Consistent results across two applications are more useful than one pass through a tester.
Check function keys on a laptop
On a laptop, test the action shown by both legends on each top-row key. For example, if one key is labeled F2 and has a brightness symbol, try it alone and with Fn. Watch the screen indicator or visible brightness change as well as the browser tester.
If every top-row key works but the default behavior is inconvenient, that is a configuration issue rather than proof of hardware failure. Check the computer manufacturer's documentation for its function-row or action-key setting. Some models expose it in an operating-system utility or firmware setup rather than through a keyboard shortcut.
For a wider laptop check, use the laptop keyboard test and verify letters, modifiers, arrows and the top row in the same session.
Check function keys on Windows, macOS and Chromebook
On Windows, compare the online result with the intended action in an ordinary desktop application. Vendor hotkey software can affect brightness, volume and other special actions, so a system action and a browser event are not interchangeable tests.
On macOS, the Keyboard settings can determine whether the top row behaves as standard function keys or system controls. Test the visible system action, then test the corresponding F-key combination.
On a Chromebook, the top row normally uses Chromebook-specific actions. Search, Launcher and other shortcuts can provide F-key equivalents, depending on the device and its settings. Use the exact model's help documentation when the printed top row differs from a standard F1–F12 layout.
When a function key still does not work
If one key consistently fails in both layers and in more than one application, shut down the device and inspect around the key for debris or physical damage. Do not pry off a laptop keycap unless the manufacturer's service instructions say it is removable. An external keyboard comparison can help separate a built-in keyboard issue from an operating-system setting.
If all function keys changed at the same time, first review Fn Lock, recent remapping, accessibility settings, keyboard-layout utilities and manufacturer hotkey software. Replacing hardware should come after those reversible checks.
A browser test reports the keyboard events that reach the page. It cannot measure the internal switch electrically, prove long-term reliability or override shortcuts reserved by the browser or operating system. See how Keyboardtest evaluates keyboard input for those limits.
Frequently asked questions
Can I test function keys online?
Yes. An online function key test can show which F1–F12 events reach the browser. Pair it with the real system action because some shortcuts are handled outside the page.
How do I know if my Fn key is working?
Hold Fn while pressing a dual-purpose top-row key. If the result reliably switches between its F-key behavior and its media or system behavior, the Fn layer is working even if Fn does not appear as a separate browser event.
Why does F5 refresh instead of appearing in the test?
F5 is commonly assigned to refresh in browsers. The browser may perform that shortcut before the tester can present a useful result. Save work, reopen or refocus the test, and compare F5 in another application.
Why do my function keys control volume or brightness?
Your keyboard may default to its media or action layer. Try the documented Fn combination and check the model's Fn Lock or function-row preference.