Update, May 25 (07:30 am ET): Fitbit says the Luxe is not using a USB-C connector.
What you need to know
- The latest Fitbit Luxe fitness tracker uses a USB-C charging cable.
- Until now, Fitbit had been using USB-A charging cables for its fitness trackers and smartwatches.
- The Luxe is also the brand's first fitness tracker with a color screen.
The Fitbit Luxe, which was announced last month, is the company's most impressive fitness tracker yet. Not only does the Luxe offer a ton of advanced health tracking features, but it comes in a sleek design and is also the first Fitbit fitness tracker to come with a color display.
While the Fitbit Luxe will begin shipping only in June, the company has now listed (opens in new tab) the Luxe Charging Cable on its website. As reported by 9to5Google, Fitbit has finally ditched USB-A in favor of USB-C with the Luxe. The Luxe charging cable includes a physical button too, which can be used to perform a reset in case the tracker doesn't respond.
Fitbit's best fitness trackers — including the popular Ace 3 and Inspire 2, use the older USB-A connector. The Fitbit Sense, which is one of the best Android smartwatches, also uses a USB-A charging cable.
Now that Fitbit has decided to switch to USB-C, it is likely to become the standard for its upcoming wearables. However, it is unclear if Fitbit will start shipping new USB-C charging cables for its existing devices.
Update, May 25 (07:30 pm ET) — The Luxe uses a USB-A connector
Fitbit has told 9to5Google that the image for the Luxe charging cable on its website was just a "sample" and the fitness tracker is actually using a USB-A connector.
The Fitbit Luxe is a premium fitness tracker with an elegant design, a vibrant AMOLED display, and a host of health-tracking features. It can also track physical signs of stress and includes a pulse oximeter for measuring blood oxygen saturation.
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.