Telegram Markdown and HTML formatting for better messages
Telegram lets you turn a plain message into a scannable announcement, a readable code note or a spoiler-safe event update. You can apply styles from the Format menu in the mobile or desktop app, or send markup through a bot when publishing at scale. Both routes can produce clean typography; they simply use different controls.
MarkdownV2 and HTML are strict, machine-oriented formats. A stray asterisk, square bracket or full stop can change their meaning, and a bot will not silently repair every mistake. This guide explains what to use, how to escape problem characters, and how to build messages that read naturally in Australian group chats.
Choose the formatting route that fits
Start by deciding who controls the message. If a person is posting, the app’s formatting toolbar is usually fastest. If code or a bot sends the content, select MarkdownV2 or HTML through the request’s parse mode.
| Formatting need | Telegram app | Bot API with MarkdownV2 | Bot API with HTML |
|---|---|---|---|
| Bold and italic text | Apply from the Format menu | Use *bold* and _italic_ |
Use <b> and <i> |
| Underlined or struck text | Apply from the Format menu | Use __underline__ and ~strike~ |
Use <u> and <s> |
| Code | Apply inline or block formatting | Use backticks | Use <code> and <pre> |
| Links | Select the text and add a URL | Use Markdown link syntax | Use an anchor tag |
| Automation | Manual selection | Set parse_mode to MarkdownV2 |
Set parse_mode to HTML |
The app represents emphasis as a style rather than visible source code, so recipients see bold text instead of asterisks. That makes it forgiving and ideal for quick updates. A developer sending through the Bot API sees the opposite: markup travels with the request, is parsed by Telegram and disappears from the rendered message when valid.
Use MarkdownV2 for lightweight emphasis and familiar shortcuts. Use HTML when a message contains nested styles, a named code language or a structured quote. Whichever route you choose, inspect the raw formatting in the bot’s test output so a malformed character does not become a production error.
Build a reliable MarkdownV2 message
MarkdownV2 uses compact punctuation to mark emphasis, links and code. A basic announcement can look like this before Telegram renders it:
*Important update*
_The venue has changed._
__Registration closes Friday.__
~This session is cancelled.~
`Bring your camera`
Plain text needs extra care because MarkdownV2 reserves a broad set of characters: underscores, asterisks, brackets, parentheses, tildes, greater-than signs, hashes, plus and minus signs, equals signs, pipes, braces, full stops and exclamation marks. Escape them with a backslash when they should appear literally:
The session starts at 7 pm.
This is a dash-separated note.
A literal backslash itself requires two backslashes. Escaping may look untidy in the source, but it lets punctuation appear naturally after processing. Remember that an apostrophe does not require escaping, although escaping it remains valid.
MarkdownV2 also supports spoiler markers, inline links and fenced code blocks. It works well for event notices, short guides and routine announcements, but strict escaping becomes cumbersome when a message contains several URLs or lots of mathematical notation. Check the complete message rather than testing only its first line.
Use HTML for precise control and rich blocks
HTML gives developers clearer boundaries between style and content. It is particularly useful for generated messages, nested emphasis and code samples that need a language label. Bot API methods such as sendMessage accept an HTML parse_mode value.
<b>Event update</b>
<i>Saturday, 18 May, 7 pm AEST</i>
<u>Central Station</u>
<s>Old venue</s>
<tg-spoiler>Bring your camera</tg-spoiler>
<a href="https://example.com">Open the guide</a>
HTML also handles code blocks more explicitly. Put the code inside <pre> and add a language class when you want syntax highlighting:
<pre><code class="language-python">print("Hello, Australia")</code></pre>
Escape ampersands as &, less-than signs as < and greater-than signs as > when they represent content rather than markup. Quote every attribute value and close every tag correctly. Telegram may reject a request containing an unsupported element, malformed nesting or an invalid entity.
Most people will never need to type HTML by hand in the Telegram app; they select formatting from its menu instead. HTML is primarily useful for bots, automated alerts and publishing systems. Do not mix raw Markdown and HTML in the same message, as the parser may interpret the unexpected characters in ways you did not intend.
Make messages fit Australian communities
Australian hobby clubs and creator communities often use compact Telegram groups for meetups, recommendations and file sharing. Reusable announcement patterns then save time and make the group look more organised. Most people in Sydney, Melbourne and Brisbane encounter these messages on a phone, so the most important information should appear before any long explanation.
Local conventions can also prevent confusion. Australian dates are commonly written day first, so 08/05 means 8 May rather than 5 August. Include the month name when a date matters. Time zones vary from Perth’s AWST to the eastern states’ AEST and AEDT, and daylight-saving changes affect scheduled posts. Casual language such as “no worries” or “see ya” can suit a friendly community update, although formal notices benefit from a neutral tone.
For a Brisbane photography club announcing a members’ night, a creative community guide can help admins find a suitable community and adopt a consistent welcome-message format.
Use these message patterns for recurring updates:
- Use
*Event:* Board meet, 18 May, 7 pm AEST. - Use
*RSVP:* Reply by 15 May. - Use
*Reminder:* Doors open at 6:30 pm. - Use
*Venue change:* Meeting at Central Station. - Use
*Code note:* Run python3 app\.py.
Run a quick check before sending anything to a busy group:
- Choose one parse mode and use it consistently throughout the bot.
- Escape every reserved MarkdownV2 character that should appear literally.
- Preview the rendered message at phone width before publication.
- Write important dates as “18 May” instead of relying on numeric order.
- Add the relevant Australian time zone and check daylight-saving timing.
- Confirm that links open correctly and that spoilers hide the intended detail.
Turn formatting into a repeatable publishing routine
Treat each bot format as a separate publishing channel. Create a test chat, send one short message with MarkdownV2 and another with HTML, then inspect both on a phone. Keep a small library of approved snippets for announcements, reminders and corrections so volunteers do not have to reconstruct the formatting each time.
Time-sensitive communication needs the same discipline. For channels covering United States civic news alongside Australian issues, a presidential election explainer shows why naming the election and date is clearer than saying “the next election”. Apply that precision to club deadlines, ticket releases, public holidays and event reminders.
Open Telegram now, create a private test group and publish one event update using a saved template. Add the group’s Australian time zone, check the result on another phone and use the finished version in the next announcement.