⌘
Topic-first exploration
Follow hierarchical topic paths and understand broker namespaces without flattening the structure.
MQTT topic workspace
See broker data as a clear dashboard.
A focused independent guide to MQTT Explorer, with practical setup notes, compatibility guidance, troubleshooting steps, and a direct path to the configured source archive.
Topic tree visibilityBroker diagnosticsHome Assistant workflows
Structured topic view
Broker → client → topics
What is MQTT Explorer?
A visual client for understanding MQTT traffic.
Instead of scanning a raw stream, MQTT Explorer organizes messages into a topic hierarchy so you can reason about devices, sensors, automations, and retained values.
Tree
Navigate nested topic paths in a structured view.
Live
Observe changing payload values while connected.
Context over noise
Use hierarchy, payload inspection, and broker connection details together to understand where a message originates and what a system is doing.
Features
Dashboard-like visibility for everyday MQTT work.
↯
Live values
Track changing payload values as MQTT messages arrive so active devices are easier to inspect.
◎
Connection profiles
Keep broker hosts, ports, credentials, and connection settings organized for repeat workflows.
⌁
Nested topics
Expand parent and child topics in a structured tree that makes complex MQTT layouts easier to read.
◇
Debugging context
Trace sensors, commands, retained values, and automation events while keeping their topic context visible.
◫
Payload inspection
Review message payloads alongside topic paths to compare expected data with what the broker is actually receiving.
How it works
From connection details to a readable topic map.
Prepare
Collect broker host, port, credentials, and any TLS requirements.
Connect
Create a connection profile and authenticate to the broker.
Explore
Expand the topic hierarchy and watch values update.
Diagnose
Compare expected topics and payloads with actual traffic.
Compatibility
Choose the runtime that matches your environment.
Use a compatible desktop build or prepare a development environment when working from source.
Desktop packaging has historically covered macOS and Linux; verify the build path for your current environment.
Current source development also includes a browser-mode path, useful when a centrally hosted interface better fits your setup.
Use cases
Where the topic tree earns its keep.
Home Assistant
Trace discovery topics, sensor values, availability messages, and automation-triggering payloads.
IoT commissioning
Confirm a new device publishes to the right namespace before connecting downstream logic.
Broker cleanup
Spot unexpected topic branches, retained values, or high-frequency telemetry that deserves attention.
Installation / Setup
Know what you are downloading.
The configured download is a ZIP snapshot of the upstream master branch. It is source code, not a ready-made Windows installer.
Download NowSource workflow example
After extracting the archive, inspect its included project documentation and package requirements before running development commands.
yarn && yarn build && yarn startCommand availability depends on your installed development environment and the source version you downloaded.
Download
Download MQTT Explorer source archive.
This button opens the single configured external download: a ZIP archive of the MQTT Explorer master branch source.
Download MQTT ExplorerⓘSource archive only. Review project files and build requirements before running code on your system.
Safety notice: MQTT topics can control real devices. Confirm the broker, topic, and payload before publishing. Avoid testing on command namespaces connected to locks, power switching, alarms, HVAC, or other consequential equipment unless you understand the effect.
Pros and cons
Useful visibility, with a few practical tradeoffs.
Pros
- Clear hierarchical topic navigation
- Useful for Home Assistant and IoT debugging
- Connection-focused workflow for repeat broker access
- Helps reveal retained and changing data patterns
Considerations
- Busy brokers can create large, noisy topic trees
- Publishing to live command topics requires caution
- Source downloads need a build environment
- Android users may prefer a mobile-native client
Release information
Master source, not a mirrored release catalog.
This site does not repackage or mirror installers. The configured download points to the project’s master-branch source ZIP, so contents can change over time as upstream development changes.
Troubleshooting
Start with the connection path.
No connection
Verify host, port, protocol, firewall reachability, and whether the broker expects TLS or WebSockets.
Authentication rejected
Recheck credentials and broker ACLs. A valid login can still lack permission to subscribe to the topics you need.
Empty topic tree
Confirm that traffic exists, subscription permissions are broad enough, and you are connected to the intended broker.
High CPU or memory use
Look for wildcard subscriptions against very high-frequency topics and reduce unnecessary message volume while diagnosing.
Guides preview
All GuidesFocused answers for common MQTT Explorer searches.
MQTT Explorer on Windows 11
Understand the difference between source archives and installer builds.
Read guide →
MQTT Explorer with Home Assistant
Use topic inspection to trace discovery, sensors, and automations.
Read guide →
Fix connection errors
Work through host, port, authentication, TLS, and ACL issues.
Read guide →FAQ
MQTT Explorer questions, organized like a help dashboard.
Using MQTT Explorer
MQTT Explorer is used to inspect MQTT topic trees, watch message values, review retained information, and work with broker connections from a visual client interface.
Yes, it can be used alongside Home Assistant when both connect to the same MQTT broker. You still need the broker host, port, and credentials configured for your environment.
No. MQTT Explorer is a client for connecting to an MQTT broker. It does not replace broker software such as the service already handling MQTT messages in your setup.
MQTT Explorer is designed around a structured topic view and can help you inspect the latest values visible on connected topics, including retained data when the broker supplies it.
A client workflow can include publishing to topics when your broker permissions allow it. Use care with command topics because publishing can trigger real devices or automations.
Enter the broker hostname or IP address, port, and any required username, password, TLS, or WebSocket settings. Then connect and confirm the topic tree begins populating.
Common causes include the wrong broker or port, authentication failure, missing topic permissions, no current traffic, or subscriptions restricted by the broker.
It can visualize broad hierarchies, but performance depends on message volume, topic count, retained data, and the computer or browser environment running the client.
MQTT client deployments commonly use TLS when supported by the broker. The exact certificate and connection fields depend on the build and broker configuration you are using.
Yes. Watching topic paths and changing payload values can help trace whether a device, bridge, or automation is publishing the data you expect.
Download, Setup & Safety
Use the main Download MQTT Explorer button in the Download section. The configured download retrieves a ZIP archive of the project source from the upstream master branch.
No. The configured ZIP is a source-code archive, not a Windows installer. Building or running source can require development tools and additional setup.
Windows 11 can run compatible desktop builds or development environments, but you should verify the packaging and build path appropriate to the version you intend to use.
This site does not provide an Android APK. For Android workflows, consider browser-accessible deployments or another MQTT client designed for Android if that better matches your device.
Check DNS or IP address, port, protocol, username and password, TLS requirements, firewall rules, and broker ACLs. Testing one variable at a time usually finds the mismatch.
Confirm the credential pair, ensure the account can subscribe to the needed topics, verify you are reaching the intended broker, and review whether TLS or WebSocket settings are required.
Narrow subscriptions when possible, avoid unnecessary wildcard traffic, reduce high-frequency telemetry during diagnosis, and separate extremely noisy topic branches.
Only publish when you understand the topic. Command topics may switch relays, locks, HVAC states, or automations. Prefer isolated test topics before sending values into a live environment.
Alternatives include other desktop, browser, and mobile MQTT clients. Choose based on platform support, TLS needs, payload tooling, topic visualization, and how much message history you need.
The Guides section and blog page include focused articles for Windows 11, Home Assistant, installation, connection errors, performance, Android options, alternatives, and safety.