Chromebook Keyboard Not Working? Here Is How to Fix It

Chromebook keyboard problems split into two very different groups, and telling them apart before you start is what saves an afternoon.

The first group is not faults at all. ChromeOS puts keys in places other laptops do not, leaves out keys other laptops have, and hands several top-row keys to the operating system in a way no application can see. A great many "my Chromebook keyboard is broken" reports turn out to be a key that never existed, a Search key doing exactly what it should, or an input method left switched on.

The second group is real: a dead key, a dead row, liquid damage, or a loose ribbon connector. Those need a different response.

This guide separates them, then works through the fixes in the order that resolves the most cases per minute spent. If you want to see which keys are actually registering while you read, keep the Chromebook keyboard test open in another tab — it uses the real ChromeOS layout rather than a Windows one.

---

First: the keys that were never there

Before troubleshooting anything, check whether the key you are hunting for exists on a Chromebook at all. This is the single most common cause of a "broken" Chromebook keyboard.

Most Chromebooks have no dedicated Delete key and no Caps Lock key. Both positions are used for something else. If Delete "stopped working", it did not — there is nothing there to stop.

The Search key is not a broken Windows key

Where Caps Lock sits on other laptops, a Chromebook has the Search key (a magnifying glass on older models, a Launcher circle on newer ones). It reports itself to the browser as MetaLeft — the identical code a Windows key sends.

This confuses generic keyboard testers, which light up a key labelled "Win" in the wrong position and make it look like something is wrong. Nothing is. If you want to check the Search key properly, use a test built on the ChromeOS layout so the key appears where your fingers expect it.

The top row is browser actions, and half of it is invisible to websites

The ChromeOS top row is Back, Forward, Reload, Fullscreen and Show-windows, followed by brightness, volume and lock. The first five send their own key codes and can be tested in a browser. The rest — brightness, volume, and the lock key — are consumed by ChromeOS before any application sees them, so no web page in any browser can detect them. That is by design, not a limitation of a particular test.

To send a real F1 through F12 instead of the printed action, hold Search and press the top row key. To flip it permanently, go to Settings › Device › Keyboard and turn on "Treat top-row keys as function keys".

---

Now the actual troubleshooting, in order

Work down this list. Each step is quick, and they are ordered so the highest-yield checks come first.

1. Restart, then hard-reset

A plain restart clears transient input-stack problems and takes thirty seconds.

If that does not help, do a hardware reset, which is different from a restart and resets the embedded controller that the keyboard talks to:

1. Shut the Chromebook down completely.
2. Hold Refresh (↻) and press Power.
3. Release Refresh when the machine starts.

On tablets, hold Volume Up and Power for about ten seconds instead. This resolves a surprising share of unresponsive-keyboard cases and loses nothing, because it does not touch your files.

2. Check for a stuck or dirty key

If the keyboard is unresponsive as a whole, a single stuck key can be the reason — a held modifier suppresses normal typing everywhere. Look for a key sitting lower than its neighbours, press each modifier individually, and clean around anything that feels different.

Compressed air is the right tool: hold the can upright, tilt the Chromebook, and use short bursts at an angle across the key rather than straight down. Avoid prying the keycap off — Chromebook keycaps clip onto thin scissor hinges that snap easily, and a broken hinge cannot be repaired the way a keycap can be replaced.

3. Turn off the accessibility features that mimic a fault

Under Settings › Accessibility › Keyboard and text input, three settings produce symptoms that read exactly like failing hardware:

• Sticky keys — modifiers latch instead of needing to be held, so Ctrl or Shift appears stuck on.
• On-screen keyboard — can capture input in ways that make the physical keyboard seem dead.
• Auto-repeat settings — a very short repeat delay causes doubled characters; turning repeat off entirely makes held keys do nothing.

Any of these can be enabled accidentally.

4. Check the input method

Settings › Advanced › Languages and inputs › Inputs. If a second input method is installed, Ctrl + Space cycles between them — an easy accident.

The symptom to recognise here is specific: the right keys register but the wrong characters appear. Press the key next to Enter and get a different symbol than the legend shows, and your keyboard is fine — the active input method does not match the physical board. US and UK layouts catch people most often because they swap @ and ".

5. Sign in as a Guest

This is the step that splits software from hardware, and it is worth doing before anything drastic.

Sign out, then sign in as a Guest. A guest session runs without your extensions, settings, or profile. If the keyboard works normally as Guest, the fault is in your user profile — an extension, a setting, or a sync problem — and the hardware is fine. If it fails identically as Guest, the problem is below the profile layer.

6. Remove extensions

If Guest mode worked, an extension is the likely culprit. Some extensions listen on key events and re-dispatch or swallow them. Disable them all, confirm the keyboard behaves, then re-enable in batches to find the offender.

7. Powerwash (last software resort)

Settings › Reset settings › Powerwash returns the Chromebook to factory state. Your Google account data syncs back, but anything stored locally is erased — back up local files first.

Do this only after Guest mode has failed to isolate the problem, because it is a lot of disruption for a fault that a guest session would have identified in a minute.

---

Reading the pattern of failure

Which keys fail tells you more than how badly they fail.

One key dead, everything else fine. Physical, and often fixable. Debris under the cap is the most common cause on any laptop keyboard. Clean it first — it works more often than people expect.

A whole row or column dead. Not the switches. Keys in a row share a trace in the keyboard matrix, so a full row failing points at that trace, the connector, or the ribbon cable running to the mainboard. That cable flexes every time the lid opens and is a genuine wear item. Intermittent whole-row dropouts are sometimes fixed by reseating it.

Scattered keys dead with no pattern. Usually liquid. If something was spilled, the fault will not resolve itself — residue keeps conducting after it dries, and sugary drinks are considerably worse than water.

Everything dead, all at once. Try the hardware reset first, then the ribbon connector. If an external USB keyboard also fails, the problem is not the keyboard at all.

Keys register twice from one press. A different fault with a different fix — that is switch chatter, and the double typing test measures the millisecond gap that confirms it.

---

If it is the hardware

Chromebook keyboards are a single assembly. There is no swapping one switch, so the realistic options are cleaning, replacing the whole keyboard, or working around it.

Check the warranty first. Chromebooks are commonly bought for schools and carry manufacturer coverage; keyboard failure within the term is a standard warranty claim. If the device was issued by a school or employer, go through their IT process rather than opening it.

Weigh the repair against the machine. On many Chromebooks the keyboard is riveted into the top case, so replacement means replacing the whole palmrest assembly. On a budget model that can approach a large fraction of what the device is worth. An external USB or Bluetooth keyboard is a legitimate answer on an older Chromebook, not a defeat.

If liquid was spilled, power the machine off immediately rather than shutting it down cleanly, unplug it, and turn it upside down to drain. Leave it to dry for at least 24 to 48 hours. Do not apply heat, and do not put it in rice — that has never been shown to draw out moisture and it adds dust and starch to the problem.

---

Frequently asked questions

Why does my Chromebook have no Delete key?

Because ChromeOS maps forward delete to Alt + Backspace instead. Most Chromebook keyboards genuinely have no Delete key at all, so if you are following instructions written for Windows, that key does not exist to press. The same is true of Caps Lock, which is replaced by the Search key and available as Alt + Search.

What is the Search key and why does it show as a Windows key?

The Search key — magnifying glass on older Chromebooks, Launcher circle on newer ones — sits where Caps Lock is on other laptops and opens app search. To the browser it identifies itself as MetaLeft, the same code a Windows key sends, which is why generic keyboard testers label it "Win" and put it in the wrong place. That is a limitation of the tester, not a sign that anything is wrong.

How do I use F1 to F12 on a Chromebook?

Hold Search and press the corresponding top-row key. The top row is printed with browser actions — Back, Forward, Reload, Fullscreen, Show windows — because those are what most people use most. To swap the default permanently, enable "Treat top-row keys as function keys" under Settings › Device › Keyboard, after which the browser actions require Search instead.

Why can't a website detect my brightness and volume keys?

ChromeOS handles them internally and never passes them to applications. This is deliberate and applies to every browser — a web page cannot see brightness, volume, or the lock key on any Chromebook. If a keyboard test greys those keys out and leaves them out of its progress count, it is being accurate rather than incomplete.

Will a Powerwash fix my keyboard?

Only if the cause is software, and you can find that out much faster by signing in as a Guest. A guest session runs without your profile, extensions or settings; if the keyboard works there, the problem is in your profile and a Powerwash will clear it. If the keyboard fails in Guest mode too, a Powerwash will not help and you should be looking at hardware instead.

My Chromebook types the wrong characters. What is wrong?

The active input method does not match your physical keyboard, which is a settings problem rather than a fault. Ctrl + Space cycles installed inputs and is easy to hit by accident. Check Settings › Advanced › Languages and inputs, and remove any input method you did not intend to add. US and UK layouts are the pair that catches most people, since they swap the at sign and the double quote.

---

Related tools and reading

• Chromebook keyboard test — the real ChromeOS layout, Search key included
• Laptop keyboard test — mechanism-level faults common to all laptops
• Double typing test — if keys register twice from one press
• Stuck key test — if a key appears to be held down