Chromebook touchpad can look completely dead when ChromeOS has simply disabled it, but the same symptom can also come from a temporary hardware-controller problem or a failed touchpad.
Start with one check that is especially important on current ChromeOS versions.
Check Whether ChromeOS Disabled the Touchpad
Open:
Settings > Accessibility > Cursor & touchpad
Find Disable built-in touchpad.
Set it to Never while troubleshooting.
ChromeOS can disable the built-in touchpad when a mouse is connected, so this setting is the first place to look when the problem began after connecting a USB mouse, wireless receiver, dock, or another pointing device.
Unplug the external mouse as a quick test too.
If the touchpad immediately starts working, the hardware is probably fine.
The Cursor Does Not Move at All
A completely unresponsive touchpad needs a different approach from one that moves normally but cannot click or scroll.
Turn the Chromebook off and wipe the touchpad with a clean, dry microfiber cloth. Remove moisture, grease, and debris around the edges without pouring cleaner directly onto the surface.
Google also recommends two unusually simple Chromebook-specific checks.
Press Esc several times and test the touchpad again.
If nothing changes, place several fingers on the touchpad and perform a short finger “drumroll” for about ten seconds.
Then shut the Chromebook down completely and restart it. Do not just close and reopen the lid.
Test the touchpad before launching several apps.
Compare the Touchpad With a USB Mouse
Connect a known-working wired USB mouse if one is available.
USB mouse works normally
ChromeOS is still accepting pointer input, so attention shifts toward the built-in touchpad, its settings, or its hardware connection.
Check the disable-touchpad setting again, then consider the hardware reset below.
USB mouse also fails
The problem may be broader than the internal touchpad.
Restart ChromeOS, try another USB port or mouse, and install available ChromeOS updates.
When pointer input fails across multiple devices, do not assume the internal touchpad alone has failed.
Cursor Moves but Clicking Does Not Work
Test tap-to-click and the physical click separately.
Open:
Settings > Device > Touchpad
Make sure Tap to click is enabled.
Now tap the surface without physically pressing it.
When tapping works but pressing the touchpad does not, the touch sensor is still responding. The mechanical click mechanism may be obstructed, damaged, or under physical pressure.
Use tap-to-click as a temporary workaround and inspect the touchpad from the side.
A touchpad that is raised, unusually stiff, or no longer sits flush with the palm rest deserves particular attention because pressure from a swollen internal battery can affect the trackpad assembly.
Do not press a raised touchpad back into place.
If the Chromebook case is bulging or you suspect battery swelling, stop using and charging the device and arrange professional service.
Physical Click Works but Tapping Does Not
This usually points back toward configuration rather than a completely failed touchpad.
Open:
Settings > Device > Touchpad
and enable Tap to click.
Also test ordinary pointer movement and two-finger scrolling.
When physical clicking, movement, and scrolling all work, replacing the touchpad would make little sense just because tap-to-click was disabled.
Two-Finger Scrolling or Right-Click Is the Only Problem
A Chromebook commonly uses a two-finger tap or click for right-click.
When pointer movement and normal clicking work but two-finger gestures do not, clean and dry the touchpad first. Then test with two fingers placed slightly apart.
Review the touchpad settings and restart ChromeOS.
Also check whether scrolling is actually working in the opposite direction. ChromeOS provides a scrolling-direction setting, so reversed scrolling can be mistaken for a broken gesture.
Test two-finger scrolling in several ordinary webpages or ChromeOS screens before deciding the touchpad hardware is failing.
For a context menu, Alt + click can also work as an alternative on Chromebooks.
Touchpad Stops Working Only When a Mouse Is Connected
This symptom has a particularly direct explanation on current ChromeOS versions.
Return to:
Settings > Accessibility > Cursor & touchpad
If Disable built-in touchpad is set to When a mouse is connected, ChromeOS is intentionally turning the touchpad off.
Change it to Never when you want the external mouse and built-in touchpad available at the same time.
There is no reason to reset or Powerwash the Chromebook for this behavior.
Touchpad Works in Another User Account
Sign out and test another Chromebook account where practical.
If the touchpad behaves normally there, the physical device is clearly capable of working. Focus on the affected profile and its settings instead of opening the Chromebook for repair.
Back up important local files before removing an account.
Google recommends removing and adding the affected account again when the touchpad works under another user.
On a managed school or business Chromebook, account controls may be restricted. Contact the administrator rather than trying to bypass management.
Touchpad Fails After Sleep but Returns After Restart
This pattern suggests an initialization or system-state problem more strongly than a permanently dead touchpad.
Check for a stable ChromeOS update:
Settings > About ChromeOS > Check for updates
Install an available update and restart.
Disconnect docks, USB receivers, and other external input devices temporarily.
If the keyboard also stops working when the Chromebook wakes, the hardware reset below becomes especially relevant because Google says that reset restarts hardware including the keyboard and touchpad.
For a keyboard problem that continues independently, see Chromebook Keyboard Not Working? Test It and Find the Cause.
Perform a Chromebook Hardware Reset
Use this when the touchpad remains unresponsive after the simpler checks, especially when the problem affects the keyboard too or repeatedly appears after sleep.
For most Chromebooks:
- Turn the Chromebook off.
- Press and hold Refresh.
- Tap Power.
- Release Refresh when the Chromebook starts.
Some models use a different procedure, so check the manufacturer’s instructions for the exact Chromebook when necessary.
A hardware reset is not a Powerwash. It restarts hardware components rather than deliberately erasing your Chromebook profile.
Google warns that a hardware reset might delete some files from Downloads, so protect important local files first when possible.
Test the touchpad immediately after startup.
Touchpad Is Missing From ChromeOS Settings
This is a stronger warning sign than a touchpad that is detected but configured incorrectly.
Restart the Chromebook and perform the hardware reset.
Then check for ChromeOS updates and compare another user account if available.
If normal touchpad controls remain absent while a USB mouse works correctly, ChromeOS may not be detecting the internal touchpad properly.
At that point, manufacturer support is more appropriate than repeatedly changing browser or accessibility settings.
Touchpad Is Laggy, Jumpy, or Clicking by Itself
Do not treat erratic movement as the same problem as a dead touchpad.
Clean and dry the surface first.
Then open:
Settings > Device > Touchpad
Review Touchpad speed and Touchpad acceleration.
Test the pointer in a simple ChromeOS screen such as Settings.
If movement is smooth there but becomes erratic only inside one game, Android app, remote desktop session, or website, focus on that application.
Random clicks everywhere deserve a physical inspection. Moisture, contamination, damage, or battery swelling can produce input that looks like a software glitch.
Touchpad Behaves Differently While Charging
When the pointer becomes erratic only while the charger is connected, test without the charger and note whether the behavior immediately changes.
Use the Chromebook’s original or manufacturer-approved compatible charger where possible, and try another wall outlet.
Disconnect docks and hubs during the comparison.
Do not continue using a charger that is damaged, overheating, sparking, or causing other abnormal device behavior.
A consistent charger-dependent touchpad problem deserves hardware or power-adapter investigation rather than repeated ChromeOS resets.
After a Drop, Spill, or Chassis Damage
Physical history changes the diagnosis.
A software setting will not repair a damaged touchpad cable, click mechanism, or chassis.
Look for:
- uneven gaps around the touchpad;
- a raised trackpad surface;
- a bulging bottom case;
- liquid exposure;
- damage around the palm rest;
- clicking that became stiff immediately after an impact.
Liquid exposure and battery swelling deserve professional attention.
When the Chromebook was dropped and the touchpad stopped working immediately afterward, hardware inspection should move ahead of factory-resetting ChromeOS.
Powerwash Is Rarely the Next Step
Powerwash factory-resets the Chromebook and removes local user data.
It can be considered when the evidence genuinely points toward a persistent software/profile problem and less destructive measures have failed.
It is a poor choice when:
- the touchpad is raised or physically damaged;
- the Chromebook was dropped or exposed to liquid;
- the touchpad is no longer detected;
- only physical clicking has failed;
- an external mouse works while the internal touchpad remains absent;
- the chassis appears swollen.
Back up important local files before any factory reset.
Google’s Chromebook touchpad troubleshooting includes cleaning the touchpad, pressing Esc, performing the finger drumroll, restarting, testing another account, and using a hardware reset.
When a Chromebook touchpad still fails across user accounts after a hardware reset while a USB mouse works normally, the evidence has moved away from a simple ChromeOS setting. That is the point where the exact Chromebook manufacturer’s repair or warranty options become more useful than another round of software resets.
