Bluetooth HDT Demonstration Shows Faster Transfers on Nordic Prototype Silicon
- IoT.Business.News
- 901 reads
Nordic measured about 3.8 Mbps transferring a 2 MB file with Bluetooth HDT, while noting that performance depends on link conditions, payload size and compatible hardware.



Bluetooth Low Energy could handle larger transfers without adding a second radio to some IoT products. Nordic Semiconductor has demonstrated its upcoming High Data Throughput (HDT) feature on prototype silicon, reporting a 3.8 Mbps average during a 2 MB file transfer. The result suggests a substantial speed increase for workloads that currently push manufacturers toward Wi-Fi, though it comes from a preliminary office test and won’t apply equally to every Bluetooth link.
What Nordic measured
Nordic tested two prototype systems-on-chip by sending a 2 MB file. In the fastest HDT configuration, the transfer averaged approximately 3.8 Mbps and took about four seconds. Under the same test conditions, Bluetooth LE 2M averaged approximately 1.4 Mbps and took 12 seconds; LE 1M averaged around 0.76 Mbps and took 22 seconds.
The test used 508-byte payloads in an office environment. Those conditions matter: radio performance varies with the link, and Nordic has said more detailed laboratory benchmarking will follow. The reported figures show what the prototype achieved in that test, not a performance guarantee for products in different environments.
HDT is an upcoming enhancement to Bluetooth LE, with the Bluetooth specification expected to include it later in 2026. Nordic announced its silicon demonstration on October 29 and is among the first semiconductor vendors to show the feature operating in hardware. The demonstration establishes feasibility; Nordic has not announced a commercially available HDT chipset or supplied a product release date.
Radio changes and link trade-offs
The increase comes from changes to both radio modulation and packet handling. Bluetooth LE currently offers 1 Mbps and 2 Mbps physical layers, or PHYs. HDT adds five options—HDT2, HDT3, HDT4, HDT6 and HDT7.5—that use more advanced modulation schemes with forward error correction. It also supports longer packets, so a greater share of each transmission can carry payload data instead of protocol overhead.
These PHYs make different trade-offs between throughput, radio sensitivity and operating conditions. The faster modes need better link quality; lower-rate modes can work more effectively as signal conditions worsen. HDT includes link-quality feedback to support dynamic switching between PHYs, allowing a connection to respond to changing conditions.
Payload length also shapes the result. Longer packets can use radio time more efficiently, but that benefit shrinks when a device sends only a small amount of data. Nordic’s technical analysis indicates that HDT can perform worse than Bluetooth LE 2M for very short packets. A sensor that sends occasional temperature readings or status messages may therefore gain little from HDT, even if a product that moves files benefits significantly.
Where faster transfers could help
HDT looks most relevant to products that exchange larger data sets periodically while still needing a compact, low-power wireless design. Wearables and connected healthcare devices could synchronize stored information in less time. Smart home products could shorten firmware transfers, while industrial devices could move diagnostic files more quickly during maintenance. Nearby phones and peripherals could also exchange richer data, such as images or compressed video, within the capability of the connection.
For product teams, one architectural question is whether HDT can cover a workload now handled by a separate Wi-Fi radio. Some devices use Bluetooth LE for routine low-power links and Wi-Fi for larger transfers. If an HDT connection meets the application’s data needs, a future design might omit that second radio, reducing hardware and integration complexity. The actual power, cost and size effects will depend on the HDT chipset and how the product uses it; the demonstration does not provide those figures.
Higher peak throughput alone does not settle that design choice. Engineers will need to consider transfer size, how often transfers occur, the required link quality and the capabilities of the device at the other end. A short burst of data and a sustained file transfer place different demands on the radio. HDT’s multiple PHYs offer room to adapt, but the measured 3.8 Mbps result describes one configuration and test, not every combination of distance, interference and payload.
Silicon and ecosystem requirements
HDT requires radio modulation capabilities that existing Bluetooth LE SoCs don’t have, so a software update alone cannot add full support to current silicon. Manufacturers will need compatible chips in their products, and the other end of the connection must support HDT too. For many IoT devices, that means phones, gateways or other host equipment will be part of the adoption path.
Nordic plans to integrate HDT into its existing software and development environment, giving customers familiar tools to evaluate the technology. The Bluetooth Special Interest Group is expected to finalize the specification in late 2026, and Nordic plans to show HDT at electronica 2026 in Munich. Until compatible products arrive and interoperate, the demonstration remains an early hardware result rather than an immediately deployable feature.
The practical takeaway is workload-specific: HDT may reduce transfer time for larger payloads, while adding little for devices that exchange only small readings. The next useful evidence will be detailed lab measurements and commercial silicon specifications that let engineers compare speed, sensitivity and power under conditions closer to their own designs.