BBCode to HTML

BBCode to HTML is a free tool that converts BBCode snippets into raw HTML for use outside forum editors.

What problem does BBCode conversion solve?

BBCode conversion turns forum-style markup into HTML that browsers, content management systems and web templates can interpret. BBCode uses square-bracket tags such as [b], [i] and [url] rather than HTML elements.

This is useful when migrating posts from a forum, debugging content returned by a third-party API, or preparing an old knowledge base for a platform that accepts HTML but not BBCode. It can also help before deployment when imported text must be checked separately from the surrounding application code.

BBCode is not one formally standardised language. Forum packages and plug-ins can define their own tags, attributes and nesting rules. A conversion that works for common formatting may therefore need adjustment when the source contains platform-specific constructs such as spoiler boxes, attachment references or custom media tags.

How do I convert BBCode to HTML?

Enter or paste the source markup into the BBCode field, then read the converted code in the HTML field. Copy that HTML into the destination only after checking that the elements and links match the intended content.

1. Copy the complete BBCode snippet, including opening and closing tags.
2. Place it in the BBCode field without replacing square brackets.
3. Inspect the raw result in the HTML field.
4. Check links, images, lists and nested formatting against the original post.
5. Sanitise untrusted output before rendering it on a public page.

The conversion runs on the server. Your input travels to the server over HTTPS and is not stored.

How should I read the returned HTML?

Read the result as source code rather than as a visual preview. The returned HTML should contain elements representing the structure and formatting expressed by the source BBCode.

A simple conceptual example is:

BBCode input: [b]Release note[/b]

HTML output: a bold or strong HTML element containing the text "Release note".

Another common pattern is:

BBCode input: [url=https://example.org/docs]Read the docs[/url]

HTML output: an anchor element whose destination is https://example.org/docs and whose visible text is "Read the docs".

The exact element names can differ between converters because BBCode dialects are not standardised. For example, bold text may be represented by either a b element, which draws attention without conveying extra importance, or a strong element, which indicates strong importance. Check the actual value in the HTML field rather than assuming a particular mapping.

This tool is a converter, not a substitute for an HTML validator or security sanitiser. Treat unexpected literal BBCode, missing content or oddly nested elements as signs that the source contains malformed or unsupported syntax. Common source problems include an unclosed tag, a closing tag in the wrong order, a malformed attribute and forum-specific tags that have no general HTML equivalent.

Awkward input and dialect differences

Spaces, punctuation, numbers, accented letters and non-Latin writing are ordinary text unless they occur inside tag syntax or attributes. They should remain content rather than becoming separate markup. URLs require more care: characters that are part of the URL, such as spaces, may need percent-encoding, while characters with a special meaning in the surrounding HTML attribute syntax, such as ampersands and quotation marks, may need HTML escaping.

• Incorrect nesting: [b][i]Text[/b][/i] closes the tags in the wrong order. Correctly nested markup closes the inner tag first.
• Missing closing tags: [quote]Text has no closing counterpart when the final tag is omitted.
• Custom tags: [spoiler], [video] and attachment tags can have different meanings across forum software.
• Existing HTML: HTML mixed into BBCode may be escaped, retained or treated as text depending on the parser. Inspect it carefully rather than relying on a universal rule.
• Very long input: large migrations are usually easier to process in batches so that failed records can be identified and corrected.

An empty input has no formatting structure to convert. If the source is plain text with no BBCode tags, conversion may add little value, although downstream HTML handling may still need to escape characters such as <, > and &.

When is conversion not worth doing?

Conversion is not worth doing when the content will only be read by a system that already understands its original BBCode dialect. Changing formats introduces another transformation step and can lose custom forum behaviour.

It is also unnecessary when a machine stores BBCode unchanged for later rendering by the same forum engine. Similarly, prettifying or manually rearranging generated HTML provides little benefit when only a machine will read it, unless formatting is needed for version-control reviews or debugging.

For bulk migrations, a scripted parser may be a better fit because it can apply the same dialect rules to every record and log failures. Regular expressions alone are risky for nested markup. Use a parser that understands nesting, attributes and malformed input, then validate and sanitise the resulting HTML separately. If converted content contains embedded JSON configuration, JSON validator & beautifier can help inspect that data, but it does not validate the surrounding HTML.

Frequently asked questions

Is converted BBCode safe to publish directly?

No. HTML produced from untrusted forum posts should pass through an allow-list HTML sanitiser before it is rendered. This is especially relevant for links, images, embedded media and any source that may already contain HTML-like text.

Will line breaks become HTML paragraphs?

Line-break handling depends on the BBCode parser and the source platform's rules. Some systems treat blank lines as paragraphs, while others insert line-break elements or preserve plain whitespace. Compare a multiline sample with the original forum rendering before migrating a large collection.

Does BBCode support Unicode characters?

BBCode can contain Unicode text, including accented characters, emoji and non-Latin scripts, because those characters are content rather than tag syntax. The destination page must also use an appropriate character encoding, normally UTF-8, or the text may display incorrectly after conversion.

Can I convert BBCode inside a CSV or database export?

Convert the field values rather than the entire export file. CSV quoting, delimiters and database escape sequences belong to the container format and can be damaged if they are passed through a markup converter. Keep an unchanged backup and process a small batch before applying the conversion to every row.

What should I check before importing the HTML?

Check a sample containing nested formatting, a link, a list, an image reference and any custom tags used by the source forum. Confirm that the destination accepts those HTML elements and attributes, then run its required sanitisation or validation step before the full import.