How to use the Markdown to HTML Converter.
Rendering Markdown should preserve structure and handle embedded HTML deliberately. Sanitize untrusted content before displaying the resulting markup.
Make the workflow fit your task.
State the Markdown flavor and how embedded HTML should be handled. Render headings, lists, links and code using a compatible parser. If displaying untrusted input, sanitize the generated HTML and inspect both the source structure and browser rendering.
- What you provide
- Markdown and rendering options.
- What you get
- Sanitized HTML with equivalent document structure.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Markdown: ## Setup followed by a paragraph reading Open the app.
Completed example
<h2>Setup</h2> <p>Open the app.</p>
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does Markdown conversion automatically make embedded HTML safe?
No. Rendering and sanitizing are separate steps, and the destination's allowed elements and attributes must be considered.
Why does a table render as plain text in the destination?
Tables may require a Markdown extension. Match the source flavor to the parser rather than assuming every renderer supports identical syntax.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑