Tools
MQTT topic builder
Build topics with UNS or Sparkplug B naming and see subscription filters, QoS/retain guidance and a sample payload.
Generated topic
Subscription filters
Delivery guidance
Sample payload (data contract)
Guidance reflects common practice; verify it against your broker, clients and security policy. Sparkplug payloads are Protobuf-encoded and not generated by this tool.
Topic rules
MQTT topic levels are separated by “/”; “+” and “#” are wildcards for subscription filters only and cannot appear in publish topics. Topics are case-sensitive; avoiding spaces and non-ASCII characters reduces mistakes. Topics starting with “$” are reserved for the broker.
Sparkplug specificationFrequently asked questions
How should MQTT topics be named?
Use a fixed hierarchy from enterprise to metric (for example enterprise/site/area/line/metric), prefer lower-case ASCII and put variable information in the payload. The Unified Namespace article covers the design principles.
When should retain be used?
Retain lets a newly subscribed client receive the last known state immediately; it suits state topics and is usually unnecessary for high-rate telemetry. See the MQTT production guide.
Your inputs and calculations stay in your browser. No account is needed.
Your next step
Let’s talk about the systems you need to connect.
Share your source, destination and intended outcome. We’ll help define the project scope.