Free online ASCIIDOC to TYP converter

Typst requires source documents in its .typ markup format, while many documentation projects are authored as .adoc or .asciidoc files. Converting between them lets you reuse structured documentation in a Typst publishing workflow without recreating every heading, list, and reference manually.

What the ASCIIDOC format is

AsciiDoc is a plain-text markup format for technical documentation, manuals, README files, books, and web pages. Files commonly use .adoc or .asciidoc; Asciidoctor and Asciidoctor.js create and process them. The format supports headings, lists, tables, source-code blocks, cross-references, attributes, includes, admonitions, images, and document metadata.

What the TYP format is

In the Text files category, .typ denotes Typst source markup. Typst is a typesetting system whose compiler turns source files into PDF and other rendered outputs. TYP files combine readable source syntax with layout instructions for headings, figures, tables, citations, page settings, and reusable functions. They are useful when the destination workflow uses the Typst compiler rather than an AsciiDoc renderer or LaTeX toolchain.

How to actually convert ASCIIDOC to TYP

The most reliable automated route is Asciidoctor to DocBook XML, followed by Pandoc to Typst. Install Asciidoctor and a current Pandoc release, then run:

asciidoctor -b docbook5 -o document.xml document.adoc
pandoc -f docbook -t typst -o document.typ document.xml

Replace document.adoc with the source filename. The first command expands the AsciiDoc structure into DocBook; the second maps DocBook elements to Typst markup. Compile the result with:

typst compile document.typ

For an AsciiDoc file that depends on attributes, set them during conversion, for example:

asciidoctor -a revnumber=2.0 -a showtitle -b docbook5 -o document.xml document.adoc

You can also use the free converter on 101convert.com without installing software: select the ASCIIDOC source format, upload the file, choose TYP, and save the converted result.

Quality and compatibility limitations

This is a markup translation, not a byte-level format change. Basic headings, paragraphs, emphasis, lists, tables, code blocks, and many links usually transfer well, but AsciiDoc attributes, conditional content, custom roles, macros, extensions, includes, and diagram blocks may require manual rewriting in Typst.

Resolve includes and generate external assets before conversion when possible. Check image paths, table widths, citations, page settings, and cross-references in the generated .typ file. Pandoc may preserve content while changing layout semantics, so compile the file with Typst and inspect the rendered PDF rather than relying only on the converted source.