Interactive comparison of MQTT, CoAP, LoRaWAN, Zigbee, BLE, Thread, Matter & more.
| Feature | MQTT Application Protocol | CoAP Application Protocol | LoRaWAN LPWAN | Zigbee Short Range | BLE (Bluetooth 5) Short Range |
|---|---|---|---|---|---|
| Category | Application Protocol | Application Protocol | LPWAN | Short Range | Short Range |
| Frequency | N/A (TCP/IP) | N/A (UDP/IP) | 868/915 MHz (ISM) | 2.4 GHz (ISM) | 2.4 GHz (ISM) |
| Range | Internet-wide | Internet-wide | 2-15 km | 10-100 m | 10-400 m |
| Data Rate | Depends on transport | Depends on transport | 0.3-50 Kbps | 250 Kbps | 2 Mbps |
| Power Consumption | Medium | Low | Very Low | Low | Very Low |
| Topology | Pub/Sub (Broker) | Client/Server (REST) | Star-of-Stars | Mesh / Star / Tree | Star / Mesh (BT Mesh) |
| Security | TLS 1.2/1.3, Auth | DTLS | AES-128 (NwkSKey + AppSKey) | AES-128 | AES-CCM |
| Latency | Low (~10-100ms) | Low (~10-100ms) | High (1-10s) | Low (~15-30ms) | Very Low (~6ms) |
| Standard | OASIS / ISO 20922 | RFC 7252 | LoRa Alliance | IEEE 802.15.4 / Zigbee Alliance | Bluetooth SIG 5.x |
| Best For | Real-time telemetry, smart home, industrial IoT | Constrained devices, sensor networks, RESTful IoT | Agriculture, asset tracking, smart cities, metering | Home automation, lighting, sensor clusters | Wearables, beacons, proximity, health devices |
| IP Support | |||||
| Mesh Support | |||||
| License Free | |||||
| Bidirectional |
Real-time telemetry over internet
→ MQTT
Low latency pub/sub with QoS levels
Constrained devices with REST API
→ CoAP
UDP-based, low overhead, RESTful
Long range + low power (rural)
→ LoRaWAN
15+ km range, years of battery life
Smart home mesh network
→ Zigbee / Thread
Self-healing mesh, low power
Wearables & proximity
→ BLE
Ultra-low power, smartphone support
Unified smart home ecosystem
→ Matter
Cross-platform, Thread + Wi-Fi + BLE
Mobile asset tracking
→ LTE-M
Carrier coverage, handoff support
Static utility metering
→ NB-IoT
Deep indoor penetration, low cost
Enterprise message queuing
→ AMQP
Guaranteed delivery, rich routing
The IoT Protocol Comparison tool puts the five protocols that dominate connected-device design side by side: MQTT, CoAP, LoRaWAN, Zigbee, and Bluetooth Low Energy (BLE). Instead of reading five separate spec sheets, you get one table comparing the traits that actually decide a project — transport layer (TCP vs UDP), typical range (from BLE's ~10-100 m to LoRaWAN's 2-15 km), data rate, power draw, network topology (star, mesh, star-of-stars), messaging model (publish/subscribe vs request/response), and security defaults (TLS, DTLS, AES-128).
It is built for firmware and embedded engineers, IoT architects, and students who need to justify a protocol choice quickly. If you are deciding whether battery-powered sensors should speak LoRaWAN or BLE, or whether a gateway should broker MQTT or expose CoAP endpoints, this tool surfaces the trade-offs on one screen.
The tool organizes protocols by where they sit in the stack. MQTT and CoAP are application-layer messaging protocols: MQTT runs over TCP (default ports 1883, or 8883 for TLS) using a central broker and a publish/subscribe model with quality-of-service levels QoS 0, 1, and 2, while CoAP runs over UDP (default port 5683, or 5684 for DTLS) using compact binary headers and RESTful GET/POST/PUT/DELETE methods, making it lighter for constrained devices. LoRaWAN, Zigbee, and BLE are lower-layer radio protocols that define how bits move over the air, so they are often paired with an application protocol on top.
The physical characteristics drive most decisions. LoRaWAN uses sub-GHz ISM bands (868 MHz in the EU, 915 MHz in the US) with a star-of-stars topology and reaches several kilometers at low data rates (roughly 0.3-50 kbps), ideal for years of battery life. Zigbee (IEEE 802.15.4, 2.4 GHz) forms self-healing mesh networks at up to 250 kbps for home and building automation. BLE (2.4 GHz) targets short-range, low-latency links up to ~2 Mbps with BLE 5, common in wearables and beacons. A practical rule: pick range and power first, then layer messaging (MQTT for broker-based cloud telemetry, CoAP for RESTful constrained endpoints) on top.
Yes, it is completely free with no sign-up. The comparison data is static reference information rendered in your browser, so you enter no device or network data and nothing is uploaded to a server.
MQTT is a broker-based publish/subscribe protocol over TCP, well suited for reliable cloud telemetry with QoS guarantees. CoAP is a lightweight RESTful request/response protocol over UDP, designed for very constrained devices and smaller message overhead.
LoRaWAN offers by far the longest range, typically 2-15 km depending on environment, because it uses sub-GHz spread-spectrum modulation. Zigbee and BLE are short-range (tens of meters, extendable via Zigbee mesh).
No. LoRaWAN, Zigbee, and BLE are radio and network-layer protocols that transport data, while MQTT and CoAP are application-layer messaging protocols. They are often combined, for example BLE sensors feeding a gateway that publishes over MQTT.
For multi-year battery life at long range and low data rates, LoRaWAN is usually best. For short-range battery devices like wearables and beacons, BLE is the common choice because of its very low idle power.
MQTT is typically secured with TLS on port 8883, CoAP with DTLS on port 5684, and LoRaWAN, Zigbee, and BLE all use AES-128 encryption at the link layer. Actual security depends on correct configuration and key management.
Yes. Once you have chosen MQTT, you can use the MQTT Tester tool to connect to a broker and publish or subscribe to topics, and the Network Diagram Generator to sketch the resulting topology.