Convert AsciiDoc to BBCode

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

AsciiDoc vs BBCode Format Comparison

Aspect AsciiDoc (Source Format) BBCode (Target Format)
Format Overview
AsciiDoc
AsciiDoc Markup Language

Lightweight markup language created by Stuart Rackham in 2002 for writing documentation, books, and technical content. Uses intuitive plain-text syntax with = headings, *bold*, _italic_, listing blocks (----), admonitions (NOTE:, TIP:), include directives, and cross-references. Processed by Asciidoctor.

Markup Language Technical Docs
BBCode
Bulletin Board Code

Lightweight markup language used in online forums and bulletin board systems. Uses square bracket tags like [b]bold[/b], [i]italic[/i], [url]links[/url], and [code]code[/code]. Created in the late 1990s as a safe alternative to HTML for user-generated content in forums like phpBB, vBulletin, and SMF.

Forum Markup User Content
Technical Specifications
Structure: Plain text with markup directives
Encoding: UTF-8
Format: Human-readable markup
Compression: None
Extensions: .adoc, .asciidoc, .asc
Structure: Square bracket tags
Encoding: UTF-8 or ASCII
Format: Tag-based lightweight markup
Compression: None
Extensions: .bbcode, .txt (inline text)
Syntax Examples

AsciiDoc markup:

= Document Title

== Section Heading

This is *bold* and _italic_.

[source,python]
----
print("Hello")
----

NOTE: Important info here.

https://example.com[Link text]

BBCode equivalent:

[size=24][b]Document Title[/b][/size]

[size=18][b]Section Heading[/b][/size]

This is [b]bold[/b] and [i]italic[/i].

[code=python]
print("Hello")
[/code]

[quote]NOTE: Important info here.[/quote]

[url=https://example.com]Link text[/url]
Content Support
  • Section headings (= through =====)
  • Bold, italic, monospace formatting
  • Source code blocks with highlighting
  • Admonitions (NOTE, TIP, WARNING)
  • Tables with complex layouts
  • Cross-references and anchors
  • Include directives
  • Images, links, footnotes
  • Bold, italic, underline, strikethrough
  • Font size and color
  • Code blocks ([code] tags)
  • Quote blocks ([quote] tags)
  • URLs and images
  • Lists (ordered and unordered)
  • Simple tables (some forums)
  • Spoiler tags (some forums)
Advantages
  • Rich feature set for documentation
  • Powerful include and modular system
  • Multiple output formats
  • Professional publishing quality
  • Version control friendly
  • Extensive tooling ecosystem
  • Widely supported in forums
  • Simple and easy to learn
  • Safe (no XSS vulnerabilities)
  • Familiar to forum users
  • Visual preview in most forums
  • No complex syntax rules
Disadvantages
  • Not supported in forums directly
  • Requires conversion for web posting
  • Steeper learning curve
  • Overkill for simple forum posts
  • Limited formatting options
  • No standardized specification
  • Varies between forum software
  • No table of contents support
  • No cross-references
  • No include directives
Common Uses
  • Technical documentation
  • Software project documentation
  • Book manuscripts
  • API references
  • Knowledge base articles
  • Online forum posts
  • Bulletin board discussions
  • Gaming community forums
  • Technical support forums
  • Community discussions
  • User-generated content
Best For
  • Structured technical content
  • Multi-format publishing
  • Professional documentation
  • Book authoring
  • Forum and bulletin board posts
  • Quick formatted messages
  • User-generated web content
  • Community discussions
Version History
Introduced: 2002 (Stuart Rackham)
Modern Processor: Asciidoctor (2013)
Status: Active, widely adopted
Evolution: Asciidoctor 2.x (current)
Introduced: Late 1990s (Ultimate Bulletin Board)
Popularized: phpBB, vBulletin (2000s)
Status: Stable, widely supported
Evolution: No formal versioning
Software Support
Asciidoctor: Full support (Ruby/JVM/JS)
GitHub: Native rendering
VS Code: AsciiDoc extension
Other: IntelliJ, Atom, Sublime Text
phpBB: Full BBCode support
vBulletin: Extended BBCode
Discourse: Limited BBCode support
Other: SMF, XenForo, MyBB

Why Convert AsciiDoc to BBCode?

Converting AsciiDoc to BBCode allows you to share your technical documentation, tutorials, and structured content on online forums and bulletin board systems. Many developer communities, gaming forums, and technical support boards use BBCode as their primary formatting language. By converting your AsciiDoc content to BBCode, you can post well-formatted articles, code snippets, and guides on platforms like phpBB, vBulletin, XenForo, and SMF.

AsciiDoc's rich markup features -- including headings, bold/italic text, source code blocks with syntax highlighting, admonitions, tables, and links -- can be mapped to their BBCode equivalents. AsciiDoc headings become [size] and [b] tags, code blocks become [code] tags, admonitions become [quote] blocks, and links are converted to [url] tags. While BBCode is simpler than AsciiDoc, the conversion preserves the essential structure and formatting of your content.

This conversion is particularly useful for developers and technical writers who maintain documentation in AsciiDoc but need to share portions of it on community forums. Rather than manually reformatting your content, automated conversion ensures consistent formatting and saves time. The converted BBCode can be directly pasted into any forum that supports standard BBCode syntax.

It is important to note that BBCode has no formal specification and varies between forum software implementations. Some advanced AsciiDoc features like complex tables, include directives, cross-references, and admonitions may need to be simplified during conversion. The core formatting (bold, italic, code, links, images, lists) translates directly, while more complex elements are adapted to BBCode's simpler feature set.

Key Benefits of Converting AsciiDoc to BBCode:

  • Forum Publishing: Post formatted content on phpBB, vBulletin, XenForo forums
  • Code Sharing: AsciiDoc code blocks become [code] tags for forum display
  • Time Saving: Automatic conversion instead of manual reformatting
  • Consistent Formatting: Reliable translation of markup elements
  • Wide Compatibility: BBCode works on thousands of forum platforms
  • Community Sharing: Share technical documentation in community spaces
  • Safe Content: BBCode prevents XSS while allowing rich formatting

Practical Examples

Example 1: Tutorial Post for a Forum

Input AsciiDoc file (tutorial.adoc):

= Getting Started with Docker

== Prerequisites

You need to install *Docker Engine* and _Docker Compose_.

[source,bash]
----
sudo apt-get install docker.io
docker --version
----

NOTE: Docker requires Linux kernel 3.10+.

Output BBCode for forum post:

[size=24][b]Getting Started with Docker[/b][/size]

[size=18][b]Prerequisites[/b][/size]

You need to install [b]Docker Engine[/b] and [i]Docker Compose[/i].

[code=bash]
sudo apt-get install docker.io
docker --version
[/code]

[quote]NOTE: Docker requires Linux kernel 3.10+.[/quote]

Example 2: Technical Guide with Links

Input AsciiDoc file (guide.adoc):

== Useful Resources

* https://docs.docker.com[Docker Documentation]
* https://kubernetes.io[Kubernetes]
* https://github.com[GitHub]

TIP: Bookmark these links for reference.

image::screenshot.png[Screenshot of the dashboard]

Output BBCode:

[size=18][b]Useful Resources[/b][/size]

[list]
[*] [url=https://docs.docker.com]Docker Documentation[/url]
[*] [url=https://kubernetes.io]Kubernetes[/url]
[*] [url=https://github.com]GitHub[/url]
[/list]

[quote]TIP: Bookmark these links for reference.[/quote]

[img]screenshot.png[/img]

Example 3: Code Comparison Post

Input AsciiDoc file (comparison.adoc):

== Python vs JavaScript

=== Python Example

[source,python]
----
def greet(name):
    return f"Hello, {name}!"
----

=== JavaScript Example

[source,javascript]
----
function greet(name) {
    return `Hello, ${name}!`;
}
----

WARNING: These languages have different scoping rules.

Output BBCode:

[size=18][b]Python vs JavaScript[/b][/size]

[size=14][b]Python Example[/b][/size]

[code=python]
def greet(name):
    return f"Hello, {name}!"
[/code]

[size=14][b]JavaScript Example[/b][/size]

[code=javascript]
function greet(name) {
    return `Hello, ${name}!`;
}
[/code]

[quote][b]WARNING:[/b] These languages have different scoping rules.[/quote]

Frequently Asked Questions (FAQ)

Q: What is BBCode?

A: BBCode (Bulletin Board Code) is a lightweight markup language used in online forums and bulletin boards. It uses square bracket tags like [b]bold[/b], [i]italic[/i], [url]link[/url], and [code]code[/code] to format text. BBCode was created as a safe alternative to HTML for user-generated content, preventing XSS attacks while allowing basic formatting.

Q: Are all AsciiDoc features supported in BBCode?

A: No. BBCode is simpler than AsciiDoc and does not support all features. Core formatting (bold, italic, links, images, code blocks, lists, quotes) translates well. However, AsciiDoc features like include directives, cross-references, complex tables, admonition types, and document attributes have no direct BBCode equivalent and must be simplified.

Q: Which forums support BBCode?

A: Most traditional forum software supports BBCode, including phpBB, vBulletin, XenForo, SMF (Simple Machines Forum), MyBB, Invision Power Board, and many others. Some modern platforms like Discourse offer limited BBCode support alongside Markdown. Always check your target forum's supported BBCode tags.

Q: How are AsciiDoc code blocks converted?

A: AsciiDoc source code blocks ([source,language]....) are converted to BBCode [code=language]...[/code] tags. The language identifier is preserved when the forum supports syntax highlighting. If the forum does not support language-specific code tags, a generic [code] tag is used instead.

Q: What happens to AsciiDoc admonitions in BBCode?

A: AsciiDoc admonitions (NOTE:, TIP:, WARNING:, CAUTION:, IMPORTANT:) are typically converted to [quote] blocks in BBCode with the admonition type as a label. Since BBCode has no native admonition support, this is the closest equivalent that preserves the visual distinction of the content.

Q: Can I copy-paste BBCode directly into a forum?

A: Yes! The converted BBCode output can be directly pasted into any forum's post editor that supports BBCode. Make sure the forum's editor is in BBCode mode (not WYSIWYG mode) so the tags are interpreted correctly. Preview your post before submitting to verify formatting.

Q: Is BBCode the same across all forums?

A: No, BBCode has no formal specification and varies between forum software. Core tags like [b], [i], [url], [code], [img], and [list] are nearly universal. However, advanced tags like [table], [spoiler], [color], and language-specific [code] vary. The converter uses the most widely supported standard BBCode tags.

Q: Why use AsciiDoc instead of writing BBCode directly?

A: AsciiDoc is far more powerful and is designed for maintaining documentation at scale. By writing in AsciiDoc, you can produce multiple output formats (HTML, PDF, EPUB, BBCode) from a single source. This is ideal for maintaining tutorials, guides, or documentation that you want to publish both on your website and on community forums.