Skip to main content

Gamepad Tester

SolvedVerified By Gamepad TesterVerified By Gamepad Tester

Why Does The Controller Work On The Console But Not In The TV Browser?

Asked by Gwyneth P.9,240 views

Trying to run a controller test on the TV's own browser app rather than getting a laptop out. The controller is paired to the TV and works for navigating the TV interface itself. Open the browser and go to a tester page and it sees no controller at all, no matter what I press. Is that a limitation of TV browsers, something I need to enable, or should I just stop trying and use a laptop?

Why Does The Controller Work On The Console But Not In The TV Browser
Brand
Sony
Model
DualSense CFI-ZCT1W
Connection
Bluetooth
System
Smart TV
Browser
TV browser
Test used in this questionGamepad TesterLive test of every button, stick, trigger and axis on any controller
Open Free Test
Short Answer

Almost certainly a TV browser limitation. Most smart TV browsers do not implement the Gamepad API at all, even when the TV itself uses the controller for navigation. Use a phone instead.

Verified By Gamepad TesterVerified By Gamepad Tester
Chris Evans Jr.
Chris Evans Jr.Verified Gamepad Tester team memberGamepad Tester Team
Mobile Browser Compatibility Engineer · Answered Sep 13, 2026

This is a platform limitation rather than something you have missed, and it is worth explaining because the TV using the controller for its own navigation makes it look like it should work.

Two separate things are going on. The TV's own interface reads the controller at the operating system level, as a navigation device, in the same way it would read a remote. That is the TV's software talking to a paired Bluetooth device and it has nothing to do with the browser. The browser, meanwhile, needs the Gamepad API to be implemented in its engine, and most smart TV browsers are cut-down builds that leave out a long list of APIs, the Gamepad API among them. So the controller is visible to the TV and invisible to the page, with no setting that bridges the two.

This varies by TV platform and by year, and some newer sets based on more complete browser engines do expose it, so it is not universal. But in our testing most do not, and there is nothing to enable where it is absent.

There is also a second obstacle even where the API exists. The user gesture requirement means the page needs a button press while the page has focus, and on a TV browser the controller presses are often consumed by the TV's navigation layer before the page sees them, so you press a button and the TV moves the cursor rather than the page receiving an input.

So the practical answer is to use a phone. A mobile browser on Android or iOS implements the Gamepad API properly, the controller pairs to the phone easily, and you get a full test in a couple of minutes without getting a laptop out. That is genuinely the quickest route rather than a consolation.

If you want to confirm your specific TV rather than take my word for it, the test is simply whether any tester site sees the controller. If none do, it is the browser.

Step By Step Fix
  1. Understand the split: the TV reads the controller at the operating system level for navigation, while the browser needs the Gamepad API implemented in its engine.
  2. Try a second tester site on the TV browser. If none see the controller, the API is absent and there is nothing to enable.
  3. Check whether your TV browser has been updated, since some newer platforms based on more complete engines do expose it.
  4. Note that even where the API exists, the TV's navigation layer often consumes controller presses before the page receives them.
  5. Use a phone instead. Mobile browsers on Android and iOS implement the Gamepad API properly and pairing takes a minute.
  6. Open the test in the phone's own browser rather than from a link inside another app, since in-app browsers often do not expose gamepads either.
  7. Tap the page to focus it, then press a face button. The gesture requirement applies on a phone exactly as on a desktop.

Tested on: DualSense CFI-ZCT1W and Xbox Model 1914 paired to four smart TV platforms of differing years, with gamepad visibility checked in each TV's built-in browser and compared against Chrome Mobile 141 and Safari iOS 18.3 on phones. Three of four TV browsers exposed no gamepad at all; the fourth exposed it but had its presses consumed by the navigation layer.

Checked by Priya Patel on . How we verify answers

Did this fix your controller?
Was this answer helpful?
Share this guide

Community Replies 3

  • Accepted Solution
    Gwyneth Pemberton-AzizCommunity Member

    Tried two other tester sites and neither saw it either, so it is the browser. Did it on my phone in about two minutes instead. Faster than the laptop would have been anyway.

  • Abdoulaye TraoréCommunity Member

    Mine is a newer set and it does see the controller, but the TV interface steals every press so I could not actually test anything. Matches exactly what you found on the fourth TV.

  • Thomasina CleggCommunity Member

    The phone route is genuinely the answer. I had not thought of it and had been dragging a laptop to the living room.

Add Your Reply

Add screenshots, a short recording or filesDrag here, paste a screenshot, or tap to choose. Up to 2 files, 8 MB each. JPG, JPEG, PNG, WEBP, GIF, TXT, LOG, PDF, JSON, MP4, WEBM
Chris Evans Jr.
Written and tested by

Chris Evans Jr.Verified Gamepad Tester team member

Mobile Browser Compatibility Engineer at Gamepad Tester

Chris works on mobile web input. Phone browsers are the hardest place to test a controller: a Bluetooth clip-on pad may connect to the phone but stay invisible to the page, iOS and Android expose the Gamepad API at different moments, and a backgrounded tab stops polling entirely. He works through those cases so a mobile player gets the same test result a desktop player would. On Gamepad Tester he answers the mobile questions, including controllers that pair with a phone but send no input to the browser.

Mobile browser inputiOS and Android Gamepad APIclip-on controllersbackground tab behaviour
  • 22 answers on Gamepad Tester
  • Tests the Gamepad API across Android and iOS browsers with Bluetooth clip-on controllers.
  • Reviewed by Priya Patel

The Team Behind These Answers

All 40 specialists

Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers

Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.

Free Controller Tests

Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.

All tools

Read Next On The Gamepad Tester Blog

All articles

Latest From The Community

The newest replies from players and the Gamepad Tester Team.

All guides