Can I open FB2 files on my Kindle?

Not directly. Kindle doesn't support FB2. Convert to EPUB using ChangeThisFile or Calibre, then send the EPUB to your Kindle via Send-to-Kindle (email to your @kindle.com address). Alternatively, convert to AZW3 for direct sideloading. Both conversions preserve text, images, and metadata.

What's the difference between FB2 and EPUB?

FB2 is a single XML file with semantic tags and Base64-encoded images. EPUB is a ZIP archive of HTML files, CSS, images, and XML metadata. EPUB is the global standard supported everywhere; FB2 is dominant in Eastern Europe. Content-wise they're equivalent — both store reflowable text with metadata and images. The structural difference is that FB2 has richer semantic markup (explicit poem, epigraph, citation tags) while EPUB relies on CSS-styled HTML.

Why are FB2 files larger than EPUBs of the same book?

Base64 encoding. FB2 embeds images as Base64 text inside the XML, which adds 33% overhead per image. A 1MB JPEG becomes 1.33MB in Base64. EPUB stores images as binary files in a ZIP archive, which compresses them further. For text-only books, the difference is minimal. For image-heavy books, FB2 can be 30-50% larger. Distributing as .fb2.zip compensates for this.

Is FB2 still actively developed?

The FB2 specification (FictionBook 2.0) has been stable since the mid-2000s. There was a FB3 proposal that added more features, but it never gained significant adoption. The ecosystem (readers, libraries, conversion tools) is actively maintained, but the format spec itself is frozen. This isn't necessarily a problem — FB2 does what it needs to do for its primary use case of storing literary fiction.

Can Calibre create and edit FB2 files?

Yes. Calibre can convert to FB2 from virtually any ebook format, preserving metadata, structure, and images. It can also read and display FB2 files natively. Calibre's metadata editor works with FB2's title-info, genre, series, and author fields. For batch conversion of an FB2 library to EPUB, Calibre's bulk conversion feature is the standard tool.

How do footnotes work in FB2?

FB2 uses a separate body section for notes: <body name="notes"> . Inline footnote links use <a type="note" l:href="#note1"> , pointing to note sections by ID. Reading apps display these as pop-up footnotes or endnotes depending on the app. This explicit footnote structure converts well to EPUB's popup footnote patterns.

FB2: The FictionBook Format for Ebooks

If you've never encountered an FB2 file, you probably don't read Russian-language ebooks. FictionBook 2 is the dominant ebook format in Russia, Ukraine, and much of Eastern Europe, supported by a rich ecosystem of libraries, readers, and conversion tools. It barely registers in Western markets, where EPUB rules, but in its territory it's the standard that millions of readers use daily.

FB2 is technically interesting because it took a fundamentally different approach from EPUB. Where EPUB is a ZIP of HTML files mimicking a website, FB2 is a single XML document with strict semantic markup. Every structural element — chapter, section, epigraph, poem stanza, author annotation — has its own XML tag. Images are Base64-encoded and embedded directly in the XML. The result is a format that's verbose but remarkably clean to parse, transform, and index.

FB2 XML Structure

An FB2 file is a single XML document with a root <FictionBook> element containing two main sections: <description> (metadata) and <body> (content), followed by optional <binary> elements for images.

<?xml version="1.0" encoding="utf-8"?>
<FictionBook xmlns="http://www.gribuser.ru/xml/fictionbook/2.0">
  <description>
    <title-info>...</title-info>
    <document-info>...</document-info>
    <publish-info>...</publish-info>
  </description>
  <body>
    <section>...</section>
  </body>
  <binary id="cover.jpg" content-type="image/jpeg">/9j/4AAQ...</binary>
</FictionBook>

The namespace URI (gribuser.ru) reflects the format's origins — it was created by Dmitry Gribov (gribuser) and the Russian ebook community in the early 2000s. The spec has been stable since FictionBook 2.0; there's no FB3 in widespread use.

Metadata: Richer Than You'd Expect

FB2's <description> section contains three metadata blocks, each serving a different purpose:

title-info: About the Book

<title-info> describes the literary work itself: genre (using a fixed taxonomy like sf_fantasy, detective, prose_classic), author (with structured name: first, middle, last, nickname), book-title, annotation (a brief description/blurb as formatted text), keywords, date, cover image reference, language, source language (for translations), and sequence (series name + number).

The genre taxonomy is notably specific — FB2 defines genres like sf_history (alternate history), prose_military (war novels), religion_rel (religious literature), and home_cooking (cookbooks). This granularity enables precise library filtering that EPUB's freeform dc:subject doesn't match.

document-info and publish-info

<document-info> describes the FB2 file itself (not the book): who created the digital version, when, from what source, the program used, and a version number. This is metadata about the metadata — tracking the digitization provenance. <publish-info> records the print publication details: publisher name, city, year, and ISBN. Having separate metadata for the literary work, the digital file, and the print edition is more structured than EPUB's single Dublin Core block.

Body Structure: Semantic Markup

FB2's content model uses semantic tags rather than generic HTML. The <body> contains <section> elements (chapters), which contain:

<title> — Chapter title (can contain multiple <p> elements for multi-line titles)
<epigraph> — Chapter epigraph with optional <text-author>
<p> — Paragraphs (the basic content unit)
<poem> — Poetry with <stanza> and <v> (verse line) elements
<cite> — Block quotations with optional <text-author>
<subtitle> — Section dividers
<empty-line/> — Explicit blank lines (scene breaks)
<table> — Basic tables
<image> — Image references (linking to <binary> elements)

Inline markup includes <strong>, <emphasis>, <strikethrough>, <code>, <sup>, <sub>, and <a> for links and footnotes. Footnotes use a separate <body name="notes"> section, with inline <a type="note"> links pointing to note sections by ID.

This semantic richness is FB2's strongest feature. A poem in FB2 is tagged as a poem, not a styled <div>. An epigraph is an epigraph, not an italic paragraph. This makes FB2 files excellent sources for format conversion — the converter knows exactly what each content element is, not just how it looks.

Binary-Encoded Inline Images

FB2 embeds images directly in the XML as Base64-encoded <binary> elements at the end of the file:

<binary id="cover.jpg" content-type="image/jpeg">
/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof
Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/...
</binary>

Content within the document references images by ID: <image l:href="#cover.jpg"/>. This single-file architecture means an FB2 is entirely self-contained — no external references, no ZIP archive, no directory structure. You can email an FB2 as a single attachment and the images come with it. The downside is file size: Base64 encoding adds ~33% overhead. A 500KB JPEG becomes ~667KB in Base64. For image-heavy books, FB2 files can be significantly larger than equivalent EPUBs.

Some FB2 files are distributed as .fb2.zip — a standard ZIP containing a single FB2 file. This recovers the Base64 overhead and then some, since XML compresses well. Most FB2 readers handle .fb2.zip transparently.

Why FB2 Dominates Eastern Europe

FB2's dominance in Russian-language markets isn't a technical accident — it's a cultural one. The format emerged from Russia's ebook community in 2004, predating widespread EPUB adoption. Libraries like Flibusta (the largest Russian ebook library, legally gray) and Litres (the legitimate counterpart) standardized on FB2. Russian-made e-readers like PocketBook and ONYX BOOX have native FB2 support. FBReader, originally developed for Russian-language ebooks, is one of the most popular ebook apps globally and handles FB2 natively.

The format's rich metadata and genre taxonomy were designed for the needs of these large libraries. FB2's structured author/series/genre information enables sophisticated library management — browsing by series, filtering by genre, sorting by publication date — that works better than EPUB's loosely defined Dublin Core metadata in practice.

In Western markets, you'll encounter FB2 files from: Russian-language ebook sources, users of FBReader and similar apps, and occasionally from academic or technical sources that use FB2 for its structured markup. For most Western users, the immediate action is conversion: convert FB2 to EPUB for universal reader compatibility.

Converting FB2

FB2 converts exceptionally well to other formats because of its semantic markup. The converter doesn't have to guess what a section is — the XML tags are explicit.

FB2 to EPUB — Clean conversion. FB2 sections map to EPUB chapters, poems and epigraphs get appropriate CSS, metadata transfers fully. Convert here
FB2 to MOBI/AZW3 — Good results via Calibre. MOBI loses some semantic structure; AZW3 preserves it better. FB2 to MOBI | FB2 to AZW3
FB2 to PDF — Renders fixed pages from the reflowable content. Good for printing. Convert here
FB2 to TXT — Strips all formatting, keeps the text. Useful for plain-text readers or text analysis. Convert here
EPUB to FB2 — Works, but EPUB's looser structure means some semantic information is inferred rather than explicit. Convert here

Calibre is the gold standard for FB2 conversion, and it's what ChangeThisFile uses for all ebook format transformations on the backend.

FBReader and Other FB2 Apps

FBReader is the canonical FB2 reading application. Originally created for Linux in 2005, it now runs on Android, iOS, Windows, macOS, and Linux. Despite its name, FBReader supports EPUB, MOBI, RTF, plain text, and HTML in addition to FB2. It's one of the most downloaded ebook apps on Android with over 10 million installs on Google Play.

Other readers with strong FB2 support: PocketBook devices (native hardware support), ONYX BOOX devices (native), CoolReader (open source, popular in Russian-speaking countries), Moon+ Reader (Android), and Calibre (cross-platform library manager with full FB2 read/write/convert support). If you use any of these, FB2 works as well as EPUB. If you use Apple Books, Kindle, or Kobo, convert to EPUB first.

FB2 is a well-designed format that solved real problems for a specific community. Its semantic markup is arguably superior to EPUB's generic HTML for literary content — knowing that something is a poem stanza versus a styled paragraph matters for rendering, accessibility, and conversion fidelity. The single-XML-file architecture is elegantly simple, even if the Base64 image encoding is wasteful.

If you have FB2 files and use a Western reading ecosystem, convert to EPUB for the best compatibility. If you're in the FB2 ecosystem already (FBReader, PocketBook, ONYX BOOX), there's no reason to leave — the format works well and has strong tooling support.