Skip to content
Toolars
Explore

Markdown & HTML Workspace

Convert between Markdown and sanitized HTML in both directions — scripts and remote media stripped — with visible notices for lost structure.

Task path / input to outcome

Choose the direction

Report bug

Local processing

Processing details

Tool inputs are processed on your device.

Resources may be downloaded to run this tool. Account services are separate.

Preparing offline use…

Privacy information

Task path / input to outcome

How to convert between Markdown and HTML

  1. 01

    Choose the direction

    Set Conversion direction to Markdown to HTML or HTML to Markdown. The input pane relabels itself to Source Markdown or Source HTML to match, so the expected source is always visible before you paste.

  2. 02

    Paste the source

    Paste into the selected range. The clipboard button captures your selection before reading; a late read cannot overwrite a subsequent edit, reset or direction change. Input is measured as raw UTF-8 bytes before trimming.

  3. 03

    Convert and inspect the preview

    Scripts, remote media, forms and active attributes are removed. Preview links are inactive; exported safe links remain. Preview renders the converted output, including any lost structure.

  4. 04

    Read the safety notices

    Tables or complex lists were converted to separated plain text in code blocks. Their original layout is not preserved. Only http, https, mailto and in-page # targets survive in exports; relative, protocol-relative and active destinations lose their link target. The isolated preview removes all link targets, so clicking it cannot navigate. Exported safe links remain active when used elsewhere.

  5. 05

    Copy or download the output

    Copy the converted text or download toolars-clean.html / toolars-clean.md. Editing, clearing or switching direction removes the previous result; convert again before exporting. Review the actual downloaded text before publishing it elsewhere.

Tool facts

Processing
In your browser
Input leaves this device
Never
Retention
Nothing is stored
Price
Free

Your input stays in the browser.

Markdown & HTML Workspace uses its verified local execution path and does not create a hidden input or output history.

Local execution

Runs inside the current browser tab.

No hidden processing

Active tool data never becomes a Toolars document record.

No account required

Use the core workflow without creating a profile. Favorites sync to your account after you sign in.

Immediate reset

Clear the tab and the active working data is gone.

What Markdown & HTML Workspace actually does

A README written in Markdown has to render inside a help center that only accepts HTML; an HTML announcement page from the marketing site needs to become Markdown for the documentation repository; a support article mixes both and nobody knows which parts will survive the trip. Markdown & HTML Workspace converts in either direction in the browser: Markdown to HTML for publishing, HTML to Markdown for editing, with the preview showing exactly what the exported file will contain — including the parts that could not be preserved. Tables and complex lists become separated plain-text code blocks with a visible notice rather than silently mangled; scripts, remote media, and active attributes are stripped, and only http, https, mailto, and in-page link targets survive in the export, so the result is safe to paste into a CMS. Check the code fences and link targets in the preview, then copy or download the clean file. Because the conversion never leaves the tab, draft documentation and unreleased announcements stay off the network until you publish them yourself.

Common questions

Which Markdown features are supported?
Subset: headings, paragraphs, flat lists, quotes, emphasis, links and fenced code. Raw HTML in Markdown is shown as text. Images are omitted; tables and complex HTML lists become plain-text code blocks with a warning. Not full CommonMark/GFM. Limits: 256 KiB input, 512 KiB output/preview in UTF-8, 20,000 nodes and 48 levels.
Is the HTML preview safe to look at?
Scripts, remote media, forms and active attributes are removed.
How does HTML become Markdown?
Headings, paragraphs, emphasis, safe links and simple lists map to the supported Markdown subset. Code uses delimiters longer than its internal backticks. Literal Markdown punctuation is escaped. HTML tables and complex lists become separated plain-text code blocks and trigger a loss notice; their original layout is not preserved.
What happens to links?
Only http, https, mailto and in-page # targets survive in exports; relative, protocol-relative and active destinations lose their link target.
What are the limits?
Limits are 256 KiB raw input and 512 KiB output/preview in UTF-8, 20,000 parsed nodes and 48 levels. Repeated delimiter scans also have a work budget. Parsing is synchronous in this tab; a rejected document must be simplified. These limits are not a performance guarantee on every device.
Is the content I paste uploaded anywhere?
No. Conversion and sanitization run entirely inside the current browser tab, input is never sent or retained, and no account is required.

Keep reading

Guides

Related tasks, not a dead end.

Move into another focused workspace without returning to the full index.

URL Workbench

Clean URL lists with signed-link protection and per-line reasons. Compare components and export sitemaps.

Edit

JSON Explorer

Query JSONPath, extract fields and round-trip JSON Pointer records without losing large-number precision.

Inspect

JSON Schema Validator

Validate Draft 7 or 2020-12 locally with exact error paths; infer schemas from multiple observed samples.

Inspect

HTML Publishing

Clean pasted HTML for publishing while preserving lists, links and table semantics; preview changes safely.

Publish