> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/component-basics/marketplace-components/markdown-renderer.md).
# Markdown Renderer
Bring formatted text into your app for displaying text as bold, italics, headings, strikethroughs, code blocks, or even within tables and lists.
## Before you begin
* Make sure to know the basics of markdown ().
* A full specification of available styling options can be found [here](https://github.com/iamacup/react-native-markdown-display#syntax-support).
* You do not need a paid Adalo plan to use the feature
## Walkthrough
{% tabs %}
{% tab title="Simple" %}
**1.)** While in your Adalo app, click the big plus sign 
in the top left corner
**2.)** Scroll down to the **Marketplace** section and click **Explore Marketplace**
**3.)** Find **Markdown Renderer** in the component list and click **Install**
**4.)** Back in the components list, enter **Markdown Renderer** in the search bar, then click and drag the Markdown Renderer component onto the desired screen
**5.)** In the **Markdown formatted Text** input field, you can enter the markdown text that should be displayed in your app.
{% endtab %}
{% endtabs %}
## Example
## Learn More
* You can also render magic text by clicking the [Magic Text](https://help.adalo.com/component-basics/inserting-dynamic-text) icon.
## Help
If you need additional help with this article, you can always ask in our[ community forum](https://forum.adalo.com/)! Be sure to paste the link to this article in your post as well!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.adalo.com/component-basics/marketplace-components/markdown-renderer.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.