Convert BBCode to Markdown

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

BBCode vs Markdown Format Comparison

Aspect BBCode (Source Format) Markdown (Target Format)
Format Overview
BBCode
Bulletin Board Code

Lightweight markup language used in online forums and bulletin boards. Uses square bracket tags like [b], [i], [url] for formatting. Designed as a safer alternative to HTML for user-generated content on forums such as phpBB, vBulletin, and XenForo.

Forum Standard Markup
Markdown
Markdown Markup Language

Lightweight markup language created by John Gruber in 2004. Uses intuitive symbols like #, *, and - for formatting. Widely adopted for documentation, README files, blogs, and note-taking. Renders to HTML and is the standard on GitHub, GitLab, Stack Overflow, and many CMS platforms.

Documentation Standard Developer Favorite
Technical Specifications
Structure: Tag-based markup with square brackets
Encoding: UTF-8
Syntax: [tag]content[/tag]
Tags: [b], [i], [url], [img], [code], [quote]
Extensions: .bbcode, .bb, .txt
Structure: Symbol-based inline markup
Encoding: UTF-8
Syntax: **bold**, *italic*, # heading
Variants: CommonMark, GFM, MultiMarkdown
Extensions: .md, .markdown, .mdown
Syntax Examples

BBCode uses square bracket tags:

[b]Bold text[/b]
[i]Italic text[/i]
[url=https://example.com]Link[/url]
[img]https://example.com/pic.jpg[/img]
[code]print("Hello")[/code]
[quote]Quoted text[/quote]
[list]
[*]First item
[*]Second item
[/list]

Markdown uses intuitive symbols:

**Bold text**
*Italic text*
[Link](https://example.com)
![Image](https://example.com/pic.jpg)
`print("Hello")`
> Quoted text
- First item
- Second item
Content Support
  • Bold, italic, underline, strikethrough
  • Hyperlinks with [url] tags
  • Images with [img] tags
  • Code blocks with [code] tags
  • Quoted text with [quote] tags
  • Lists with [list] and [*] tags
  • Font colors with [color] tags
  • Font sizes with [size] tags
  • Bold, italic, strikethrough
  • Inline and reference-style links
  • Images with alt text
  • Fenced and inline code blocks
  • Blockquotes with > prefix
  • Ordered and unordered lists
  • Headings (levels 1-6)
  • Tables (GFM extension)
  • Task lists (GFM extension)
Advantages
  • Explicit tag syntax is unambiguous
  • Safe alternative to HTML on forums
  • Supports font colors and sizes
  • Familiar to forum users worldwide
  • Nesting is straightforward
  • No injection risk for web content
  • Clean, readable plain text
  • Industry standard for documentation
  • Native support on GitHub and GitLab
  • Easy to learn and write
  • Renders beautifully in many tools
  • Extensible with flavors (GFM, etc.)
  • Wide tooling ecosystem
Disadvantages
  • Verbose tag syntax
  • Limited to forum platforms
  • No heading hierarchy
  • Not used in modern dev workflows
  • No table support in standard BBCode
  • No native color or font size support
  • Multiple incompatible flavors
  • Limited complex layout options
  • No underline syntax in standard Markdown
  • Whitespace sensitivity can be confusing
Common Uses
  • Forum posts and discussions
  • Bulletin board signatures
  • Online community content
  • User-generated messages
  • Gaming community forums
  • README files and documentation
  • GitHub/GitLab content
  • Blog posts and articles
  • Technical writing
  • Note-taking applications
  • Static site generators
Best For
  • Forum discussions and posts
  • Safe user-generated content
  • Online community interactions
  • Bulletin board formatting
  • Software documentation
  • Technical writing and blogs
  • Version-controlled content
  • Cross-platform text formatting
Version History
Introduced: 1998 (Ultimate Bulletin Board)
Standard: No formal specification
Status: Widely used, community-driven
Variations: Platform-specific extensions
Introduced: 2004 (John Gruber)
Standard: CommonMark (2014+)
Status: Active development, widely adopted
Variants: GFM, MultiMarkdown, Pandoc MD
Software Support
phpBB: Full support
vBulletin: Full support
XenForo: Full support
Other: MyBB, SMF, Discord (partial)
GitHub: Native GFM support
VS Code: Built-in preview
Pandoc: Full conversion support
Other: Obsidian, Notion, Jekyll, Hugo

Why Convert BBCode to Markdown?

Converting BBCode to Markdown bridges the gap between traditional forum content and modern documentation platforms. BBCode was designed for bulletin board systems in the late 1990s, while Markdown has become the universal standard for writing on the web, powering GitHub, Stack Overflow, blogs, and countless documentation sites. If you have content originally written for forums that you want to repurpose for documentation, blogs, or repositories, converting BBCode to Markdown is the logical first step.

The key advantage of Markdown over BBCode is readability. While BBCode uses verbose tags like [b]bold[/b] and [url=https://example.com]link text[/url], Markdown achieves the same results with **bold** and [link text](https://example.com). This makes Markdown documents far easier to read in their raw form, which is critical for version control systems like Git where diffs are reviewed in plain text.

Our converter intelligently maps BBCode tags to their Markdown equivalents: [b] becomes **, [i] becomes *, [url] becomes inline links, [img] becomes image syntax, [code] becomes fenced code blocks, [quote] becomes blockquotes, and [list] items become bullet or numbered lists. Tags without direct Markdown equivalents (like [color] and [size]) are handled gracefully to preserve content while maintaining clean Markdown output.

This conversion is especially valuable for migrating forum knowledge bases to wikis, converting archived forum posts into blog articles, or transferring community content to platforms like GitHub Discussions or GitLab. With Markdown, your content gains compatibility with hundreds of tools and platforms that have adopted this format as their standard.

Key Benefits of Converting BBCode to Markdown:

  • Modern Standard: Markdown is the de facto standard for documentation and web writing
  • Readable Source: Markdown is far more readable as raw text than BBCode tags
  • GitHub Compatible: Directly usable in README files, issues, and pull requests
  • Blog Ready: Works with Jekyll, Hugo, Gatsby, and other static site generators
  • Version Control Friendly: Clean diffs in Git and other VCS systems
  • Wide Ecosystem: Supported by VS Code, Obsidian, Notion, and hundreds of tools
  • Portable Content: Easily converts further to HTML, PDF, DOCX, and more via Pandoc

Practical Examples

Example 1: Forum Post to Blog Article

Input BBCode file (post.bbcode):

[b]Getting Started with Python[/b]

[i]A beginner's guide to Python programming[/i]

Python is a versatile language. Here are key features:
[list]
[*]Easy to learn syntax
[*]Large standard library
[*]Cross-platform support
[/list]

[code]
def hello():
    print("Hello, World!")
[/code]

Visit [url=https://python.org]Python.org[/url] for more.

Output Markdown file (post.md):

**Getting Started with Python**

*A beginner's guide to Python programming*

Python is a versatile language. Here are key features:
- Easy to learn syntax
- Large standard library
- Cross-platform support

```
def hello():
    print("Hello, World!")
```

Visit [Python.org](https://python.org) for more.

Example 2: Forum FAQ to Documentation

Input BBCode file (faq.bbcode):

[b]Frequently Asked Questions[/b]

[quote]How do I install the software?[/quote]
Download the installer from our website and follow the setup wizard.

[quote]What are the system requirements?[/quote]
[list=1]
[*]Windows 10 or later
[*]4 GB RAM minimum
[*]500 MB free disk space
[/list]

[img]https://example.com/screenshot.png[/img]

Output Markdown file (faq.md):

**Frequently Asked Questions**

> How do I install the software?

Download the installer from our website and follow the setup wizard.

> What are the system requirements?

1. Windows 10 or later
2. 4 GB RAM minimum
3. 500 MB free disk space

![Image](https://example.com/screenshot.png)

Example 3: Forum Guide to README

Input BBCode file (guide.bbcode):

[b]Project Setup Guide[/b]

[i]Last updated: March 2026[/i]

[b]Prerequisites[/b]
[list]
[*]Node.js v18+
[*]npm or yarn
[*]Git
[/list]

[b]Installation[/b]
[code]
git clone https://github.com/example/project.git
cd project
npm install
npm start
[/code]

For issues, visit [url=https://github.com/example/project/issues]our issue tracker[/url].

Output Markdown file (guide.md):

**Project Setup Guide**

*Last updated: March 2026*

**Prerequisites**
- Node.js v18+
- npm or yarn
- Git

**Installation**
```
git clone https://github.com/example/project.git
cd project
npm install
npm start
```

For issues, visit [our issue tracker](https://github.com/example/project/issues).

Frequently Asked Questions (FAQ)

Q: What is BBCode?

A: BBCode (Bulletin Board Code) is a lightweight markup language used on internet forums since the late 1990s. It uses square bracket tags like [b]bold[/b] and [url]link[/url] to format text. BBCode was designed as a safe alternative to HTML, preventing script injection while allowing rich text formatting in user-generated content on forum platforms like phpBB, vBulletin, and XenForo.

Q: How are BBCode tags mapped to Markdown?

A: The converter maps BBCode tags to their closest Markdown equivalents: [b] becomes ** (bold), [i] becomes * (italic), [url] becomes [text](link) syntax, [img] becomes ![alt](url), [code] becomes fenced code blocks with ```, [quote] becomes > blockquotes, and [list][*] items become - bullet points or numbered lists. Tags without direct Markdown equivalents are handled gracefully.

Q: What happens to [color] and [size] tags?

A: Standard Markdown does not support font colors or sizes. During conversion, the content within [color] and [size] tags is preserved as plain text, but the styling information is removed. If you need color support, some Markdown flavors allow inline HTML, which can be used to add color styling manually after conversion.

Q: Are nested BBCode tags handled correctly?

A: Yes, the converter properly handles nested tags like [b][i]bold italic[/i][/b], converting them to the correct Markdown equivalent ***bold italic***. The converter parses the BBCode tag hierarchy and generates properly nested Markdown formatting, preserving the intended structure of the original content.

Q: Which Markdown flavor does the output use?

A: The converter generates CommonMark-compatible Markdown that also works with GitHub Flavored Markdown (GFM). This means the output is compatible with GitHub, GitLab, VS Code, Obsidian, Jekyll, Hugo, and virtually every tool that supports Markdown. Fenced code blocks use triple backticks, which is the most widely supported syntax.

Q: Can I convert BBCode forum archives to Markdown?

A: Yes, this converter is ideal for migrating forum content to Markdown-based platforms. Upload your BBCode files and get clean Markdown output suitable for documentation wikis, static site generators, or knowledge bases. For bulk conversions of entire forum archives, you can process multiple files sequentially.

Q: How are BBCode lists converted?

A: BBCode [list] tags with [*] items are converted to Markdown unordered lists using - prefix. Ordered lists created with [list=1] are converted to numbered Markdown lists (1., 2., 3.). Nested lists are also supported, with proper indentation applied in the Markdown output to maintain the hierarchical structure.

Q: Is the converted Markdown compatible with GitHub?

A: Absolutely. The output uses GitHub Flavored Markdown (GFM) compatible syntax, making it perfect for README files, issues, pull requests, wiki pages, and discussions on GitHub. Links, images, code blocks, lists, and all standard formatting will render correctly when viewed on GitHub.