← How-Tos
electronics Sep 6, 2026 ◯ 4 min read

Qwiic and STEMMA QT: Plug-and-Play I2C Sensor Ecosystems for Makers

QwiicSTEMMA QTI2CSparkFunAdafruitsensor breakout

Our I2C wiring guide covers the protocol itself — addresses, pull-ups, bus sharing. What it doesn't cover is the connector standard that's made I2C sensor wiring almost solderless for a huge chunk of the hobbyist market: SparkFun's Qwiic and Adafruit's STEMMA QT. They're mechanically and electrically the same 4-pin JST-SH 1.0mm connector carrying power, ground, SDA, and SCL, which means boards from either company (and a long list of third parties who've adopted the standard) snap together with a cable and no soldering. If you've been hand-wiring I2C sensors to breadboards, this is worth knowing about before your next project.

Qwiic and STEMMA QT Are the Same Connector

SparkFun introduced Qwiic in 2017; Adafruit followed with STEMMA QT using an identical JST-SH 4-pin, 1.0mm pitch connector with the same pinout. A Qwiic cable works on a STEMMA QT board and vice versa — there's no adapter needed between the two ecosystems, which is unusual for competing "standards" and is a large part of why it caught on. The only naming distinction that matters: Adafruit's separate "STEMMA" (not STEMMA QT) line uses a different, larger JST-PH connector for non-I2C signals like analog sensors and single-wire protocols — check which connector a board actually has before ordering cables, since STEMMA and STEMMA QT are not interchangeable despite the similar name.

PinSignalNotes 1GNDCommon ground across the chain 23.3VBus power — confirm every board on the chain is 3.3V tolerant before daisy-chaining from a 5V source 3SDAI2C data line 4SCLI2C clock line

Why This Matters Beyond Convenience

The Bus Loading Problem

Each Qwiic/STEMMA QT board typically includes its own pair of pull-up resistors (commonly 2.2k-10k ohm each) on SDA and SCL. Daisy-chain more than 3-4 boards and you can end up with pull-up resistance low enough to distort the bus signal, especially at longer cable runs or higher I2C clock speeds — the same fundamental bus-loading issue covered generally in our I2C protocol guide, just easier to run into by accident here because adding a device is as easy as plugging in a cable. If you're seeing intermittent I2C errors after chaining several sensors:

Using a Qwiic/STEMMA QT Hub

For projects with more than a handful of sensors, a dedicated I2C multiplexer hub (SparkFun's Qwiic Mux, or similar third-party boards) is more reliable than daisy-chaining everything through each board's pass-through connector — it isolates address conflicts onto separate mux channels and centralizes the pull-up situation to one location instead of scattered across every board in the chain.

Where the Ecosystem Falls Short

Not every sensor worth using has a Qwiic/STEMMA QT breakout — plenty of specialized or industrial sensors are still bare-breakout-and-breadboard only, and the connector doesn't do anything for SPI, analog, or single-wire devices. It's also a convenience layer that adds a small cost premium over a bare sensor IC — fine for prototyping and one-off builds, less sensible once you're designing your own PCB where you'd wire I2C directly anyway per our PCB design guide.

For breadboard prototyping and quick sensor swaps across ESP32, Pi, and Arduino projects, standardizing on Qwiic/STEMMA QT breakouts removes a genuine amount of wiring friction — just watch the pull-up and address conflicts once a chain grows past a few devices, and don't assume it replaces understanding the underlying I2C protocol when something goes wrong.