Free online ASCIIDOC to TEXTILE converter

What the ASCIIDOC format is

AsciiDoc is a lightweight markup format stored as plain text, usually with .adoc or .asciidoc extensions. It supports document titles, sections, admonitions, tables, cross-references, attributes, source-code listings, images, and includes.

Files are created and processed by Asciidoctor, the older AsciiDoc processor, AsciidocFX, Antora, and text editors. Documentation projects, README files, manuals, release notes, and static-site source files commonly use it. AsciiDoc syntax varies between implementations, and Asciidoctor extensions can add features that are not part of the basic format.

What the TEXTILE format is

Textile is a plain-text markup language used by some wikis, content-management systems, publishing tools, and older web applications. Its syntax uses short markers such as h1. Heading for headings, *bold* for bold text, _italic_ for italics, and "link text":https://example.com for links.

Textile remains useful when the destination application has a Textile parser but no AsciiDoc support. Because it is plain text, the converted file can be edited with any text editor and versioned without a binary document format. Textile implementations differ in support for tables, attributes, footnotes, and extended syntax.

How to actually convert ASCIIDOC to TEXTILE

For a quick conversion without installing software, use the converter on 101convert.com: upload the .adoc or .asciidoc file, select TEXTILE as the output format, start the conversion, and download the resulting .textile file.

For local, repeatable conversion, use Asciidoctor to create DocBook XML and Pandoc to create Textile. Pandoc does not reliably parse every AsciiDoc dialect directly, so this two-stage route gives Asciidoctor responsibility for interpreting the source syntax.

1. Install Asciidoctor and Pandoc using the package method appropriate for your operating system.
2. Open a terminal in the directory containing the source file.
3. Run asciidoctor -b docbook5 -o intermediate.xml input.adoc. Replace input.adoc with the actual filename. Use input.asciidoc when that is the source extension.
4. Convert the intermediate document with pandoc -f docbook -t textile intermediate.xml -o output.textile.
5. Open output.textile in a text editor or import it into the target Textile application and inspect the rendered result.

If the source uses local includes, run Asciidoctor from the project directory so relative paths resolve correctly. For example, asciidoctor -b docbook5 -o intermediate.xml chapters/index.adoc may require the project’s include paths and attributes to be available from that working directory.

Quality and compatibility limits

The intermediate DocBook step can change presentation details. AsciiDoc attributes, conditional blocks, custom roles, extensions, admonition styling, unresolved cross-references, and processor-specific macros may be omitted or represented differently in Textile.

Check tables, nested lists, inline formatting, images, footnotes, anchors, source-code blocks, and links after conversion. Images are normally referenced by path rather than embedded, so copy the image files and preserve the relative directory structure. A Textile renderer may not support every feature produced by Pandoc; unsupported constructs can appear as escaped markup or ordinary paragraphs.

Keep the original AsciiDoc file as the authoritative source. Edit the Textile output only when the destination system requires a one-off adjustment, because repeating the conversion will overwrite those changes.