MQTT Topics, Wildcards, & Best Practices – MQTT Essentials: Part 5

MQTT Topics, Wildcards, & Best Practices – MQTT Essentials: Part 5

author HiveMQ Team

Written by HiveMQ Team

Category: MQTT Essentials MQTT

Published: August 20, 2019

Updated: June 20, 2023

MQTT Topics are crucial in the MQTT ecosystem as the broker relies on them to determine which clients receive specific messages. Here’s Part 5 of MQTT Essentials, where we will focus on MQTT topics, MQTT Wildcards, and explore best practices for their usage in detail. In this article, we will also examine SYS-topics, which offer insights into the broker itself.

Table of Contents

If you are exploring to understand publishing, subscribing, and unsubscribing in MQTT, check out Part 4 of this series. Else, let’s dive in.

What Are MQTT Topics and Their Role in MQTT Message Filtering?

In MQTT, Topic refers to a UTF-8 string that filters messages for a connected client. A topic consists of one or more levels separated by a forward slash (topic level separator).

Learn MQTT Topic Basics

Learn MQTT Topic Basics

In comparison to a message queue, MQTT topics are very lightweight. The client does not need to create the desired topic before they publish or subscribe to it. The broker accepts each valid topic without any prior initialization.

Understand MQTT Topics, Wildcards and much more. Get MQTT Essentials Guide today.

Examples of MQTT Topics

Here’re some examples of MQTT Topics:

  1. myhome/groundfloor/livingroom/temperature: This topic represents the temperature in the living room of a home located on the ground floor.
  2. USA/California/San Francisco/Silicon Valley: This topic hierarchy can track or exchange information about events or data related to the Silicon Valley area in San Francisco, California, within the United States.
  3. 5ff4a2ce-e485-40f4-826c-b1a5d81be9b6/status: This topic could be used to monitor the status of a specific device or system identified by its unique identifier.
  4. Germany/Bavaria/car/2382340923453/latitude: This topic structure could be utilized to share the latitude coordinates of a particular car in the region of Bavaria, Germany.

Best Practices for Using MQTT Topics

Here’re some best practices for using MQTT Topics:

  • Each topic must contain at least one character.
  • Topic strings can include empty spaces to allow for more readable or descriptive topics.
  • Topics are case-sensitive, meaning "myhome/temperature" and "MyHome/Temperature" are considered as two different topics.
  • The forward slash alone is a valid topic and can be used to represent a broad topic or serve as a wildcard for subscribing to multiple topics simultaneously.

MQTT topics are key in establishing communication between MQTT clients and brokers. They enable efficient filtering and routing of messages based on their content. Properly defining and structuring topics is crucial in ensuring effective data exchange and handling within MQTT-based systems.

What Are MQTT Wildcards and How to Use Them With Topic Subscriptions?

In MQTT, wildcards provide a powerful mechanism for subscribing to multiple topics simultaneously. When a client subscribes to a topic, it can either subscribe to the exact topic of a published message or utilize wildcards to broaden its subscription. It’s important to note that wildcards can only be used for subscription and not for publishing messages. There are two types of wildcards: single-level and multi-level.

MQTT Wildcard – Single Level: +

The single-level wildcard is represented by the plus symbol (+) and allows the replacement of a single topic level. By subscribing to a topic with a single-level wildcard, any topic that contains an arbitrary string in place of the wildcard will be matched.

Example of how to use MQTT Wildcard Single Level +

Example of how to use MQTT Wildcard Single Level +

For example, a subscription to myhome/groundfloor/+/temperature can produce the following results:

MQTT Topic wildcard plus example

MQTT Wildcard – Multi Level:

The multi-level wildcard covers multiple topic levels. It is represented by the hash symbol (#) and must be placed as the last character in the topic, preceded by a forward slash.

Example of how to use MQTT Wildcard Multi Level #

Example of how to use MQTT Wildcard Multi Level #

When a client subscribes to a topic with a multi-level wildcard, it receives all messages of a topic that begins with the pattern before the wildcard character, regardless of the length or depth of the topic. If the topic is specified as “#” alone, the client receives all messages sent to the MQTT broker.

MQTT Topic wildcard hash example

MQTT Topic wildcard hash example

However, it’s important to consider that subscribing with a multi-level wildcard alone can be an anti-pattern if high throughput is expected. Subscribing to a broad topic can result in a large volume of messages being delivered to the client, potentially impacting system performance and bandwidth usage. Follow best practices to optimize topic subscriptions and avoid unnecessary message overload.

Why and When to Use MQTT Topics Beginning with $

In MQTT, topic naming flexibility is vast, allowing you to choose names that suit your needs. However, there is one important exception to be aware of: topics that start with a $ symbol have a distinct purpose. These topics are not included in the subscription when using the multi-level wildcard (#) as a topic. Instead, topics beginning with $ are reserved for internal statistics of the MQTT broker, providing valuable insights into its operation.

Publishing messages to topics starting with $ is not permitted, as these topics serve as a means for the MQTT broker to expose internal information and statistics to clients. While there is currently no official standardization for these topics, it is common to use the prefix $SYS/ to denote such information, although specific implementations of brokers may vary.

One recommended resource for understanding $SYS topics is available in the MQTT GitHub wiki.

Here are a few examples of $SYS topics and the information they can provide:

  1. $SYS/broker/clients/connected: Indicates the number of clients currently connected to the MQTT broker.
  2. $SYS/broker/clients/disconnected: Shows the number of clients that have disconnected from the MQTT broker.
  3. $SYS/broker/clients/total: Represents the total count of clients, both connected and disconnected, that have interacted with the MQTT broker.
  4. $SYS/broker/messages/sent: Provides the count of messages sent by the MQTT broker.
  5. $SYS/broker/uptime: Reflects the duration the MQTT broker has been running.

These $SYS topics offer valuable insights into the internal workings and performance of the MQTT broker, enabling administrators and developers to monitor and analyze crucial statistics.

By understanding the purpose and significance of topics starting with $, you can effectively leverage this convention to gain deeper visibility into the behavior and performance of their MQTT infrastructure.

Exploring the Dynamic Nature of MQTT Topics

These are the basics of MQTT message topics. As you can see, MQTT topics are dynamic and provide great flexibility. When you use wildcards in real-world applications, there are some challenges you should be aware of. We have collected the best practices that we have learned from working extensively with MQTT in various projects and are always open to suggestions or a discussion about these practices. Use the comments to start a conversation, Let us know your best practices or if you disagree with one of ours!

MQTT Best Practices

Avoid Leading Forward Slash

While MQTT allows a leading forward slash in topics (e.g., /myhome/groundfloor/livingroom), it introduces an unnecessary topic level with a zero character at the front. This can cause confusion (having a zero character at the front) without providing any benefit. Hence, it’s recommended to exclude the leading forward slash.

Never use spaces in an MQTT Topic

A space is the natural enemy of every programmer. Spaces in topics can hinder readability and debugging efforts, particularly during troubleshooting scenarios. Moreover, UTF-8 has many different white space types. We advise against using spaces and uncommon characters altogether in MQTT topics.

Keep MQTT topics short and concise

Remember that each topic is included in every message in which it is used. To optimize network traffic and conserve valuable resources, strive to make your topics concise. This is especially crucial when dealing with resource-constrained devices, where every byte counts.

Use only ASCII characters, and avoid non-printable characters

To ensure consistent and accurate representation of topics, it’s advisable to stick to ASCII characters. Non-ASCII UTF-8 characters may display incorrectly, making identifying typos or character set-related issues challenging. Unless essential, refrain from using non-ASCII characters in your MQTT topics.

Embed a unique identifier or the Client Id in topics

To enhance message identification and enforce authorization, consider embedding a unique identifier or the client ID of the publishing client in the topic. This allows you to determine the message sender and control publishing permissions. For example, a client with the client1 ID can publish to client1/status but not to client2/status.

Avoid Subscribing to Wildcards (#)

Sometimes, it is necessary to subscribe to all messages that are transferred over the broker. For example, to persist all messages into a database. Do not subscribe to all messages on a broker by using an MQTT client and subscribing to a multi-level wildcard. Frequently, the subscribing client is not able to process the load of messages that results from this method (especially if you have a massive throughput). Our recommendation is to implement an extension in the MQTT broker. For example, with the HiveMQ extensions, you can hook into the behavior of HiveMQ and add an asynchronous routine to process each incoming message and persist it to a database.

Embrace Extensibility

Topics in MQTT provide inherent flexibility, allowing for future expansion and new features. Consider how your topic structure can accommodate future enhancements or the addition of new sensors or functionalities. Design your topics to facilitate extensibility without substantially changing the overall topic hierarchy. For example, if your smart-home solution adds new sensors, it should be possible to add these to your topic tree without changing the whole topic hierarchy.

Use specific topics, not general ones

Differentiate your topics to reflect specific data streams or entities. Avoid the temptation to use a single topic for multiple types of messages. For instance, if you have three sensors in your living room, create topics like myhome/livingroom/temperature, myhome/livingroom/brightness, and myhome/livingroom/humidity instead of using a generic topic like myhome/livingroom. This practice promotes clarity and enables the utilization of advanced MQTT features such as retained messages. To learn more, read our article on MQTT retained messages.


Maintain comprehensive documentation detailing your MQTT topics, including their purpose, expected message payload, and any associated conventions or guidelines. This aids in onboarding new team members and fosters better collaboration.

Continuous Improvement

Regularly review and optimize your topic structure based on evolving requirements and feedback from your MQTT ecosystem. Embrace a continuous improvement mindset to ensure efficient and scalable MQTT communication.

Security Considerations:

Ensure that your topic structure and naming conventions don’t inadvertently expose sensitive information. Implement proper access controls and authentication mechanisms to protect your MQTT communications.


That brings us to the end of Part 5 of our MQTT Essentials series. To summarize, MQTT topics serve as the backbone of flexible and efficient message communication in MQTT. By understanding the intricacies and applying best practices, you can optimize your MQTT implementations for maximum performance and scalability.

Throughout this article, we explored the dynamic nature of MQTT topics, delving into wildcard usage, technical considerations, and recommended strategies. We discussed the importance of avoiding leading forward slashes and spaces in topics, keeping topics concise, utilizing ASCII characters, and embedding unique identifiers or client IDs. We also emphasized the significance of not subscribing to all messages using wildcards and the value of extensibility in topic design.

By following these best practices, you can enhance your MQTT infrastructure’s readability, maintainability, and security. We hope this article has provided valuable insights and actionable information to elevate your MQTT projects. T hank you for joining us on this journey through the intricacies of MQTT topics. We hope you found this article valuable and informative.

In Part 6 of this series, we will go deeper in Quality of Service (QoS) levels in MQTT. We’ll explain why this is an essential feature and how you can leverage it.

Stay curious, stay innovative, and together let’s shape the future of MQTT.

Are you enjoying our content? Then sign up for our newsletter below. If you prefer RSS, you can subscribe to our RSS feed here. Do check out MQTT Glossary to know all the key MQTT terminologies. Watch the video below that complements the concepts discussed in this article.

FAQs About MQTT Topics

The MQTT sender (Publisher) and the receiver (Subscriber) communicate via MQTT Topics. The MQTT Topics are UTF-8 strings that allow MQTT clients to share information.

An MQTT Topic is created as a UTF-8 string with one or more topic levels.Each Topic levels are seperated by a forward slash.

MQTT topic name is a simple UTF-8 string that is hierarchically structured with forward slashes as delimiters. For example, “myhome/livingroom/temperature.

MQTT topic is UTF-8 encoded strings, and it should not be more than 65535 bytes. Using shorter MQTT Topic names results in less resource consumption.

Yes. You can use MQTT wildcards to subscribe to multiple topics simultaneously. A wildcard can only be used to subscribe to topics, not to publish a message.

When a client subscribes to a topic, it can subscribe to the exact topic of a published message or it can use MQTT wildcards to subscribe to multiple topics simultaneously. A wildcard can only be used to subscribe to topics, not to publish a message. There are two different kinds of wildcards: single-level and multi-level.

+ Symbol represents a single-level wildcard in a MQTT topic and # symbol represents the multi-level wild card in a MQTT Topic.

Topics are strings that messages are published to and subscribed to. Topics are hierarchical and can contain multiple levels separated by slashes, like a file path. Here’s an example of MQTT Topic name – myhome/kitchen/smartdishwasher

author HiveMQ Team

About HiveMQ Team

We love writing about MQTT, IoT protocols and architecture in general. Our experts are here to help, so reach out to us if we can help!

mail icon Contact HiveMQ
newer posts HiveMQ ESE 1.3 released
HiveMQ ESE 1.2 released older posts