Nordic Shows Bluetooth HDT Running on Prototype Silicon
- Published
- Author
- IoT.Business.News
- Reads
- 899
Nordic’s prototype reached about 3.8 Mbps in a 2 MB transfer, with performance depending on packet size, signal quality and compatible hardware.



Bluetooth Low Energy could handle some transfers that currently push product designers toward a second radio. Nordic Semiconductor has demonstrated Bluetooth High Data Throughput (HDT) on prototype silicon, reporting an average of about 3.8 Mbps during a 2 MB file transfer. The feature is intended to raise Bluetooth LE data rates while keeping devices within the existing Bluetooth ecosystem.
The demonstration, announced October 29, used two prototype systems-on-chip (SoCs). HDT is expected to become part of the Bluetooth specification later in 2026, but the prototype results are an early indication of capability, not a promise of performance from future products. Nordic has yet to disclose a commercial chipset or its release date.
What changes in the radio link
Bluetooth LE currently offers 1 Mbps and 2 Mbps physical layers (PHYs). HDT adds five PHY options, designated HDT2, HDT3, HDT4, HDT6, and HDT7.5. These use more advanced modulation schemes, alongside forward error correction, and allow longer packets. The modulation affects how data is represented over the radio link; error correction adds information that can help a receiver recover data when reception is imperfect.
Longer packets can reduce the share of transmission time spent on protocol overhead, leaving more time for application data. That efficiency depends on the amount of data being sent. For a substantial file, the overhead reduction can matter across many packets. For a short sensor reading, there may be too little data for longer packets to provide much benefit.
The five PHY options also reflect a familiar radio trade-off: the fastest modes need better link quality, while lower-rate modes can be more useful as signal conditions worsen. HDT includes link-quality feedback intended to support dynamic switching between PHYs. In practice, the value of that mechanism will depend on how reliably devices can assess the connection and adapt during use.
What Nordic measured
In Nordic’s preliminary 2 MB test, its fastest HDT configuration averaged approximately 3.8 Mbps and completed the transfer in about four seconds. Bluetooth LE 2M averaged approximately 1.4 Mbps and took 12 seconds under the same test conditions. LE 1M averaged around 0.76 Mbps, completing the transfer in 22 seconds.
The measurements came from an office environment and used 508-byte payloads. Nordic has said more detailed laboratory benchmarking will follow. Results from this single setup therefore provide a comparison under those conditions; they don’t establish the throughput that every product will see. Radio environment, link quality, device implementation, and the size and pattern of transferred data can all affect performance.
Packet length is a particular caveat. Nordic’s technical analysis indicates that HDT can perform worse than Bluetooth LE 2M with very short packets. A product that sends occasional status updates or temperature readings may have little to gain from a higher peak data rate. By contrast, a device that periodically moves a larger file could make better use of the added capacity.
Where higher throughput may help
The strongest use cases are devices that need to move substantial data but still benefit from Bluetooth LE’s place in a low-power product design. Wearables and connected healthcare devices could synchronize stored information faster. Smart home equipment could spend less time transferring firmware updates, and industrial devices could move diagnostic files during maintenance. These are potential applications; the practical improvement will depend on the hardware and transfer workload.
Some products pair Bluetooth LE for everyday connectivity with Wi-Fi for larger transfers. HDT could let designers reconsider that two-radio arrangement when the required bandwidth fits within HDT’s capabilities. Removing a radio may reduce hardware and integration complexity, but it doesn’t by itself guarantee lower power use or cost. Those outcomes depend on the design and the characteristics of commercial HDT chipsets, which Nordic hasn’t detailed.
Faster links could also make it more practical to exchange richer content between peripherals and phones, including images, compressed video, or other larger files. The key design question is whether these transfers happen often enough, and involve enough data, to justify HDT-capable hardware. Small, infrequent messages may still suit existing Bluetooth LE modes.
Hardware and ecosystem requirements
HDT needs radio modulation capabilities that existing Bluetooth LE SoCs don’t provide. A software update alone can’t give current chips full HDT support, so products will need compatible silicon. The receiving device also needs compatible hardware: a faster transmitter cannot deliver an HDT connection on its own.
That makes support across both ends of the connection a practical constraint for product teams. Smartphones, gateways, and other hosts need to be ready to communicate with HDT devices before manufacturers can rely on the feature across a product ecosystem. Nordic plans to integrate HDT into its software and development environment, giving customers a path to work with familiar tools, but that doesn’t resolve compatibility with third-party devices.
Nordic plans to showcase the technology at electronica 2026 in Munich. The Bluetooth Special Interest Group is expected to finalize the HDT specification in late 2026. Until the specification is settled and compatible products become available, designers can treat the prototype results as evidence that HDT operates on silicon, while keeping performance and product plans provisional.
The useful signal for engineers is the combination of a measured file-transfer comparison and a clear set of trade-offs. HDT appears most relevant where devices periodically move larger payloads and both ends can support the new radio modes. The next evidence to watch is detailed laboratory benchmarking, followed by commercial hardware and interoperability results.