Markdown reference for show notes
You can format episode show notes with the toolbar or Markdown. Markdown uses characters such as ** for bold text and * for italic text.
The tables show Markdown input and example output. They do not show the result in every podcast app. Examine your show notes in the preview and in the apps that your listeners use.
Keep the blank lines and indentation in examples with more than one line. Use your own correct URLs in place of the example addresses.
Text, lists and links
| Markdown input | Example output |
|---|---|
|
First-level heading |
|
Second-level heading |
|
italic |
|
bold |
|
Inline code and code with a ` character |
|
|
|
|
|
|
|
2011. This is not a list item |
|
|
|
https://example.com |
|
address@example.com |
|
Link text |
|
Link text |
|
Source |
|
A quotation with italic text.A quotation inside it. |
Images
Images can look different or be missing in some apps. Make sure that you can open the image URL without an account login.
| Markdown input | Example output |
|---|---|
|
Use the full public image URL in place of IMAGE-URL. |
|
Use your image URL in place of IMAGE-URL. |
Advanced syntax
The examples below show Kramdown syntax for section links, footnotes and definition lists. The editor, preview and podcast apps can give different results. Do not use these examples as a promise of support in each app.
Examine the saved result before you use these features. If a section link or footnote does not work, use plain text or a full website URL.
| Markdown input | Example output |
|---|---|
|
Go to section
Example |
|
Text with a footnote.1
1. Footnote text. Back |
|
|
See the Kramdown syntax documentation for more examples. The result in a podcast app can be different.
Advanced formatting: Footnotes and definition lists do not render consistently across Podigee previews. The published output can differ from the editor preview. Use ordinary paragraphs and links for essential information, and check heading links in the destination player or podcast app.