Convert AsciiDoc to FB2

Drag and drop files here or click to select.
Max file size 100mb.
Uploading progress:

AsciiDoc vs FB2 Format Comparison

Aspect AsciiDoc (Source Format) FB2 (Target Format)
Format Overview
AsciiDoc
Lightweight Markup Language

Human-readable document format created by Stuart Rackham in 2002 for writing technical documentation, articles, books, and manuals. Uses intuitive plain-text syntax that maps to semantic elements. Widely used in software projects and technical publishing through the Asciidoctor toolchain.

Plain Text Technical Docs
FB2
FictionBook 2.0

XML-based e-book format created by Dmitry Gribov in Russia. Extremely popular in Eastern Europe and the Russian-speaking world. Stores structured content including metadata, chapters, images, and stylesheets in a single XML file. Designed for fiction but suitable for any structured text.

XML-Based Eastern European Standard
Technical Specifications
Structure: Plain text with semantic markup
Encoding: UTF-8
Format: Human-readable markup language
Processor: Asciidoctor (Ruby/Java/JS)
Extensions: .adoc, .asciidoc, .asc
Structure: Single XML document
Encoding: UTF-8 (typical)
Format: Open XML schema
Images: Base64-encoded inline
Extensions: .fb2, .fb2.zip
Syntax Examples

AsciiDoc uses intuitive markup:

= The Story Begins
Author Name
:lang: en

== Chapter One

It was a dark and stormy night.
The *wind* howled through the trees.

[quote, Shakespeare]
____
To be or not to be.
____

FB2 uses structured XML:

<FictionBook>
  <description>
    <title-info>
      <book-title>The Story</book-title>
      <author>
        <first-name>Author</first-name>
      </author>
    </title-info>
  </description>
  <body>
    <section>
      <title><p>Chapter One</p></title>
      <p>Content here...</p>
    </section>
  </body>
</FictionBook>
Content Support
  • Headings and sections (6 levels)
  • Bold, italic, monospace, highlight
  • Source code blocks with syntax highlighting
  • Admonitions (NOTE, TIP, WARNING)
  • Cross-references and anchors
  • Tables with column formatting
  • Block quotes with attribution
  • Ordered and unordered lists
  • Sections and subsections
  • Bold, italic, strikethrough
  • Epigraphs and annotations
  • Poems and stanzas
  • Inline images (Base64)
  • Footnotes and comments
  • Tables (basic)
  • Rich metadata (genre, author, date)
  • Cover images
Advantages
  • Easy to write and maintain
  • Excellent for technical content
  • Version control friendly
  • Multiple output formats
  • Strong toolchain (Asciidoctor)
  • Active open-source community
  • Self-contained single file
  • Rich structured metadata
  • Excellent reader support in Eastern Europe
  • Machine-parseable XML
  • Simple and predictable structure
  • Good for library cataloging
  • Can be compressed as .fb2.zip
Disadvantages
  • Requires processing to view formatted output
  • Less mainstream than Markdown
  • Steeper learning curve for beginners
  • Limited WYSIWYG editing tools
  • Complex syntax for advanced layouts
  • Limited adoption outside Eastern Europe
  • No CSS or custom styling
  • Base64 images increase file size
  • No multimedia support
  • Limited table capabilities
  • Not supported by Apple Books or Kindle natively
Common Uses
  • Technical books and manuals
  • API and project documentation
  • Academic and research papers
  • Knowledge bases and wikis
  • Multi-format publishing pipelines
  • Fiction and non-fiction e-books
  • Russian-language digital libraries
  • Personal e-book collections
  • E-book archival and cataloging
  • Distribution on Litres, Flibusta
  • CoolReader and FBReader content
Best For
  • Technical writing workflows
  • Documentation-as-code projects
  • Collaborative authoring via Git
  • Single-source multi-output publishing
  • Eastern European e-book distribution
  • Structured fiction publishing
  • E-book library management
  • Lightweight e-reader devices
Version History
Introduced: 2002 (Stuart Rackham)
Current Processor: Asciidoctor 2.x
Status: Actively maintained
Evolution: AsciiDoc.py to Asciidoctor
Introduced: 2004 (Dmitry Gribov)
Current Version: FictionBook 2.1
Status: Stable, widely used
Evolution: FB1 to FB2 (XML-based)
Software Support
Asciidoctor: Primary processor (Ruby)
AsciidoctorJ: Java integration
IDE Plugins: VS Code, IntelliJ, Atom
Other: GitHub, GitLab rendering
FBReader: Primary reader (cross-platform)
CoolReader: Full support (Android/desktop)
Calibre: Read, convert, manage
Other: Moon+ Reader, AlReader

Why Convert AsciiDoc to FB2?

Converting AsciiDoc to FB2 opens the door to one of the most popular e-book ecosystems in Eastern Europe. The FictionBook format dominates digital reading in Russia and neighboring countries, with millions of readers using FBReader, CoolReader, and dedicated e-ink devices that prefer FB2 over other formats. If your audience includes Russian-speaking readers, FB2 is often the expected delivery format.

FB2 is an XML-based format that stores the entire book, including metadata, text, and images, in a single file. Unlike EPUB, which is a ZIP container of multiple files, FB2 keeps everything in one parseable XML document. This self-contained nature makes FB2 files easy to manage, catalog, and index. The rich metadata schema supports genre classification, author biographies, publication sequences, and detailed bibliographic information that digital library systems rely on.

AsciiDoc's structured markup translates naturally into FB2's section-based architecture. Chapter headings become FB2 section titles, block quotes convert to epigraph or cite elements, footnotes map to FB2's native footnote system, and inline formatting like bold and italic transfer directly. While FB2 lacks some of AsciiDoc's advanced features like source code highlighting and complex tables, the core textual content and document structure are faithfully preserved.

The conversion is particularly valuable for authors who write technical or educational content for Eastern European markets. By maintaining your source in AsciiDoc, you can produce FB2 for Russian-speaking readers, EPUB for international distribution, and PDF for print, all from a single document. This multi-format workflow ensures consistency across editions while reaching the widest possible audience.

Key Benefits of Converting AsciiDoc to FB2:

  • Eastern European Reach: Access millions of FB2 readers in Russia and CIS countries
  • Self-Contained Format: Single XML file with embedded images and metadata
  • Rich Metadata: Genre, series, author bio, and bibliographic data preserved
  • Reader Compatibility: Works with FBReader, CoolReader, PocketBook, and more
  • Library Integration: Ideal for digital library catalogs and collections
  • Compact Size: Can be compressed as .fb2.zip for efficient storage
  • Structural Fidelity: Chapter and section hierarchy preserved from AsciiDoc

Practical Examples

Example 1: Fiction Book Conversion

Input AsciiDoc file (novel.adoc):

= The Last Algorithm
Alex Petrov
:doctype: book
:lang: en

== Prologue

[quote, Alan Turing]
____
We can only see a short distance ahead,
but we can see plenty there that needs to be done.
____

The server room hummed with quiet intensity.

== Chapter One: The Discovery

Dr. Ivanova stared at the terminal output.
Something was *different* this time.

Output FB2 file (novel.fb2):

FictionBook e-book containing:
✓ Title and author metadata in <title-info>
✓ Epigraph from block quote with attribution
✓ Sections for prologue and chapters
✓ Bold formatting preserved (<strong>)
✓ Valid FB2 XML structure
✓ Ready for FBReader and CoolReader
✓ Compatible with .fb2.zip compression

Example 2: Educational Material

Input AsciiDoc file (textbook.adoc):

= Introduction to Physics
Prof. Maria Sokolova
:toc:

== Mechanics

=== Newton's Laws

. Every object persists in its state of rest
   unless acted upon by an external force.
. Force equals mass times acceleration.
. For every action there is an equal
   and opposite reaction.

NOTE: These laws form the foundation
of classical mechanics.

Output FB2 file (textbook.fb2):

Educational e-book:
✓ Nested sections (Mechanics > Newton's Laws)
✓ Numbered list items preserved
✓ Annotation from NOTE admonition
✓ Author and title metadata
✓ Structured XML for easy parsing
✓ Suitable for PocketBook e-readers
✓ Optimized for mobile reading

Example 3: Documentation with Footnotes

Input AsciiDoc file (guide.adoc):

= Travel Guide: St. Petersburg

== The Hermitage Museum

The Hermitage footnote:[Founded in 1764
by Catherine the Great] houses over
3 million items in 6 buildings.

The Winter Palace serves as the main
building of the museum complex.

image::hermitage.jpg[The Hermitage]

Output FB2 file (guide.fb2):

Travel guide e-book:
✓ Footnotes as FB2 <a> notes section
✓ Image embedded as Base64 binary
✓ Section structure maintained
✓ Metadata for cataloging
✓ Self-contained single XML file
✓ Perfect for offline reading
✓ Compatible with all FB2 readers

Frequently Asked Questions (FAQ)

Q: What is FB2 format?

A: FB2 (FictionBook 2.0) is an XML-based e-book format created in Russia. It stores the entire book, including text, images (Base64-encoded), and rich metadata in a single XML file. FB2 is the dominant e-book format in Eastern Europe, supported by readers like FBReader, CoolReader, and PocketBook devices.

Q: Will AsciiDoc tables be preserved in FB2?

A: FB2 has limited table support compared to AsciiDoc. Simple tables with basic rows and columns are converted, but advanced features like column spans, header rows, and cell alignment may not transfer perfectly. For table-heavy documents, consider EPUB or PDF as alternative output formats.

Q: Can I read FB2 files on Western e-readers?

A: While FB2 is less common in Western markets, it is supported by cross-platform apps like FBReader (available for Android, iOS, Windows, Mac, and Linux) and Calibre. You can also convert FB2 to EPUB using Calibre for use on Kindle, Apple Books, or Kobo devices.

Q: How are images handled in the conversion?

A: Images referenced in your AsciiDoc document are embedded directly in the FB2 XML file as Base64-encoded binary data. This makes the FB2 file completely self-contained but increases file size. For large image-heavy documents, consider using the compressed .fb2.zip variant.

Q: Does FB2 support source code blocks?

A: FB2 does not have native syntax highlighting for code blocks. AsciiDoc source code blocks are converted to monospace text sections in the FB2 output. The code content and indentation are preserved, but language-specific coloring is not available. For code-heavy documents, EPUB3 or HTML may be better choices.

Q: What metadata is preserved during conversion?

A: FB2 has an extensive metadata schema. The conversion preserves document title, author name, language, and annotation (from AsciiDoc preamble). FB2 also supports genre classification, publication date, series information, and cover images, though some of these may need manual specification in the AsciiDoc attributes.

Q: Can I compress the FB2 output?

A: Yes. FB2 files are commonly distributed as .fb2.zip archives, which significantly reduce file size, especially for documents with Base64-encoded images. Most FB2 readers can open .fb2.zip files directly without manual decompression. You can simply ZIP the output .fb2 file after conversion.

Q: Is FB2 suitable for technical documentation?

A: FB2 works well for text-heavy technical content but has limitations for highly structured technical documentation. It lacks advanced table support, code syntax highlighting, and mathematical notation. For technical books targeting Eastern European readers, consider producing both FB2 (for reading) and PDF (for reference) from your AsciiDoc source.