⌘ K
headings, lists, links → Textile markup

Convert Markdown to Textile

Translate Markdown to Textile — the markup used by Redmine, Jekyll legacy, and other Ruby tools.

Markdown → Textile
Input
167 B
14 lines
Output
166 B
14 lines
Status
ready
live
Ratio
0.99×
out/in
input · markdown
output · textile
h1. Project Doc

_Bold_ and _italic_ with @code@.

A "link":https://example.com and an !logo.png(image)!.

bq. A quote here.

* One
* Two

bc.. console.log("hi");

p.
Quick Start

How to convert to Textile

Maps every Markdown construct (headings, bold, italic, lists, blockquotes, code) to its Textile equivalent, preserving fenced code as Textile bc.. blocks.

  1. 01

    Paste Markdown

    Standard or GFM input.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    inputGFMmarkedCommonMarklive
    input · markdownmd · GFM
    # Title
    loaded · GFMGFM · ready
  2. 02

    Map syntax

    Headings → h1./h2., bold → *, italic → _.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    mapsoft-breaksoptionsconfiglive
    fix · optionstextile · live
    h1. Title
    options applied · livelive
  3. 03

    Preserve code

    Fenced blocks become bc.. paragraphs.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    codepreviewscoped CSSrenderstable
    code · renderedbc.. · ready
    bc.. code
    rendered · liverendered
  4. 04

    Paste into Redmine

    Or any Textile-aware tool.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    ✓ · exportedtextile · done
    ✓ ready
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsAsciiDocreSTOrg ModeBBCodeConfluenceEditor
Use Cases

When to convert to Textile

Migration into Textile-driven systems.

Redmine wikis

Drop Markdown content into Redmine projects. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Legacy blogs

Convert old Jekyll/Textile content to round-trip. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Ruby docs

Some Ruby project docs still use Textile. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Migration prep

Bulk-convert Markdown drafts for Textile-only systems. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Wiki imports

Preserve formatting when importing into Textile wikis. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Forum software

Some PHP forums accept Textile syntax. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

Mostly — bold/italic/lists/links/code all map cleanly. Exotic GFM (footnotes, task lists) may not have direct Textile equivalents.
Converted to Textile bc.. paragraph code blocks, preserving content verbatim.
![alt](url) becomes !url(alt)! — Textile's image syntax.
Markdown pipe tables aren't converted in this pass. Use the Table tools to reformat them after.
No. Conversion runs locally — nothing is uploaded.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!