Image Converter Video Converter Audio Converter Document Converter
Pricing Guides Formats API
Log In
ADOC file
adoc
File format

About ADOC Files

AsciiDoc

Released 2002 By Stuart Rackham

AsciiDoc is a human-readable markup language designed for writing technical documentation, articles, and books. It supports rich formatting including tables, admonitions, cross-references, and can be converted to HTML, PDF, EPUB, and DocBook.

Family

Documents & Text

Extension

.adoc

MIME Type

text/asciidoc

Can Use As

Input Output
The story

HOW ADOC
CAME TO BE.

2002
2013

AsciiDoc was created in 2002 by Stuart Rackham, an Australian developer who wanted a plain-text documentation format that could express everything DocBook XML could — complex documents with chapters, tables, cross-references, bibliographies — but without the XML verbosity. The original AsciiDoc toolchain (Python) compiled .adoc files into DocBook, then used DocBook\u2019s stylesheets to generate HTML, PDF, EPUB, and man pages.

In 2013 Dan Allen rewrote the processor in Ruby as Asciidoctor, reaching rough parity with the original AsciiDoc while running 100× faster. Asciidoctor became the de-facto AsciiDoc engine and the toolchain for GitLab\u2019s native rendering, Eclipse documentation, O\u2019Reilly\u2019s book production, and many large open-source projects (Spring Framework, Arquillian, Hibernate). AsciiDoc Working Group at Eclipse Foundation now maintains the language spec — a rare case of a grassroots format achieving formal standardization.

CURIOSITIES &
TRIVIA.

01

Dan Allen's 2013 Ruby rewrite (Asciidoctor) runs 100× faster than the original Python AsciiDoc — which is why AsciiDoc adoption accelerated after 2013.

02

O'Reilly Media publishes many technical books with AsciiDoc as the canonical source format.

03

GitLab renders .adoc files natively in repository views — one of the few non-Markdown formats with first-class GitLab support.

04

Eclipse Foundation adopted AsciiDoc for its official documentation in 2018 and now hosts the AsciiDoc Working Group.

05

The AsciiDoc Language spec reached 1.0 RC status at Eclipse in 2024 — formal standardization of a grassroots 2002 project.

STRENGTHS &
LIMITATIONS.

Strengths

  • Expressiveness of DocBook in plain text.
  • Cross-references, tables, bibliographies, math, and metadata native.
  • Multi-output: HTML, PDF, EPUB, man pages, DocBook XML.
  • Faster parsing than LaTeX, richer than Markdown.
  • Eclipse Foundation stewardship.

Limitations

  • Steeper learning curve than Markdown.
  • Smaller ecosystem than Markdown despite being more capable.
  • Most CI tools default to Markdown, not AsciiDoc.
  • Authoring WYSIWYG tools are limited.

Typical Sizes & Weights

Short technical article

2-20 KB

Book chapter

20-150 KB

Full book source

500 KB - 5 MB

Technical Specifications

MIME type
text/asciidoc
Extensions
.adoc, .asciidoc, .asc
Processors
AsciiDoc (Python), Asciidoctor (Ruby)
Stewardship
Eclipse AsciiDoc Working Group
Output targets
HTML, PDF, EPUB, DocBook, man page

CONVERT FROM
ADOC

Common Use Cases

Technical documentation, software manuals, O'Reilly book publishing

Popular ADOC conversions

The most-requested destinations when starting from ADOC.

Frequently Asked Questions about ADOC

Frequently Asked Questions

ADOC (AsciiDoc) is a document format used to store paginated text, with optional formatting, tables, images, hyperlinks, headers and footers. It sits in the documents & text family and is typically associated with a specific office suite or publishing pipeline that defined the format and ships the canonical reader.

Modern office suites — Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages — open most ADOC files with reasonable fidelity. If your installed software does not support ADOC, convert to DOCX or PDF first using KaijuConverter; both open in virtually every reader, including free online viewers.

Upload the ADOC to KaijuConverter and pick DOCX, PDF, ODT, RTF, HTML, Markdown, or plain text. Our pipeline runs LibreOffice headlessly plus pandoc for text formats — the same engines behind professional document pipelines. Styles, tables, images, and hyperlinks survive the conversion intact.

Yes, to a high degree. Standard fonts, headings, lists, tables, images, hyperlinks and page structure transfer cleanly. Custom fonts substitute to the closest match if not embedded; obscure layout features unique to ADOC (frames, legacy macros) may flatten to static content in the target format.