Convert Textile to Wiki

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

Uploading progress:

Textile vs Wiki Format Comparison

Aspect	Textile (Source Format)	Wiki (Target Format)
Format Overview	Textile Textile Markup Language Lightweight markup language created by Dean Allen in 2002. Used extensively in Redmine, Textpattern CMS, and other web platforms. Provides a concise, human-readable syntax for generating HTML with support for headings, lists, links, images, and tables. Markup Language Redmine Default	Wiki MediaWiki Markup Markup language used by MediaWiki, the software behind Wikipedia, Fandom, and thousands of other wiki sites. Uses a distinct syntax with double brackets for links, equals signs for headings, and pipe-based tables. The most widely used wiki markup format in the world. Wiki Markup Wikipedia Standard
Technical Specifications	Structure: Plain text with inline markup symbols Encoding: UTF-8 Format Type: Lightweight markup language Generates: HTML output Extensions: .textile, .txt	Structure: Plain text with wiki-specific markup Encoding: UTF-8 Format Type: Wiki markup language Generates: HTML via MediaWiki parser Extensions: .wiki, .mediawiki, .txt
Syntax Examples	Textile syntax: h1. Main Title p. A paragraph with bold and _italic_ text. * Unordered item * Another item "Link text":http://example.com	MediaWiki syntax: = Main Title = A paragraph with '''bold''' and ''italic'' text. * Unordered item * Another item [http://example.com Link text]
Content Support	Headings (h1. through h6.) Bold, italic, underline, strikethrough Ordered and unordered lists Hyperlinks and images Tables with alignment Block quotes and code blocks Footnotes and references	Headings (= through ======) Bold, italic, underline formatting Ordered and unordered lists Internal and external links Complex tables with styling Templates and transclusion Categories and namespaces References and citations
Advantages	Rich formatting in plain text Human-readable source Native support in Redmine Generates clean HTML Compact and expressive syntax Good table support	Powers Wikipedia and thousands of wikis Template system for reusable content Category and namespace organization Built-in citation and reference system Extensive documentation and community Supports complex table layouts
Disadvantages	Less popular than Markdown Limited tooling ecosystem Learning curve for new users Not supported by GitHub/GitLab Fewer parsers available	Complex syntax for advanced features Not widely used outside wiki platforms Steep learning curve for templates Parser-dependent rendering Verbose compared to Markdown
Common Uses	Redmine wiki pages and issues Textpattern CMS content Technical documentation Blog publishing platforms Web content authoring	Wikipedia articles Fandom wiki pages Internal corporate wikis Knowledge base articles Collaborative documentation Encyclopedia entries
Best For	Redmine project management Formatted web content authoring Quick rich text creation CMS-based publishing	Collaborative knowledge bases Wikipedia-style encyclopedias Structured wiki documentation Community-edited content
Version History	Introduced: 2002 (Dean Allen) Current Version: Textile 2 Status: Stable, maintained Evolution: Minor updates, stable spec	Introduced: 2002 (MediaWiki) Current Version: MediaWiki 1.41+ syntax Status: Actively developed Evolution: Continuous updates with MediaWiki
Software Support	Redmine: Native support Textpattern: Native support Ruby: RedCloth library Other: PHP Textile, Python textile	MediaWiki: Native support Wikipedia: Primary markup format Pandoc: Full read/write support Other: Fandom, Wikia, DokuWiki (variant)

Why Convert Textile to Wiki?

Converting Textile to MediaWiki markup is essential when migrating content from Redmine or Textpattern to wiki-based platforms like MediaWiki, Wikipedia, or Fandom. Both are lightweight markup languages, but they use completely different syntax for the same formatting elements, making manual conversion tedious and error-prone.

Textile and MediaWiki markup share conceptual similarities -- both use plain text symbols to express formatting -- but the actual symbols differ significantly. Textile uses *bold* while MediaWiki uses '''bold'''. Textile links use "text":url while MediaWiki uses [url text]. Tables have entirely different syntax. Automated conversion ensures accuracy and saves considerable time.

MediaWiki markup powers the largest encyclopedia in the world (Wikipedia) and thousands of community wikis. Converting your Textile content to wiki format opens up these platforms for your documentation, knowledge bases, and collaborative content. The wiki format also supports advanced features like templates, categories, and transclusion that are not available in Textile.

Key Benefits of Converting Textile to Wiki:

Wiki Platform Ready: Publish directly on MediaWiki, Wikipedia, or Fandom
Syntax Translation: Accurate mapping of Textile elements to wiki equivalents
Content Migration: Move Redmine documentation to wiki-based knowledge bases
Advanced Features: Access MediaWiki templates, categories, and references
Collaboration: Enable community editing on wiki platforms
Table Conversion: Textile tables mapped to MediaWiki table syntax
Bulk Migration: Convert multiple Textile pages efficiently

Practical Examples

Example 1: Documentation Page Migration

Input Textile file (guide.textile):

h1. Installation Guide

h2. System Requirements

p. Before installing, ensure your system meets
the *minimum requirements*:

* Operating System: Linux, macOS, or Windows
* Memory: 4 GB RAM minimum
* Disk: 10 GB free space

h2. Installation Steps

# Download the installer from "our site":http://example.com
# Run the installer
# Follow the on-screen _instructions_

Output Wiki file (guide.wiki):

= Installation Guide =

== System Requirements ==

Before installing, ensure your system meets
the '''minimum requirements''':

* Operating System: Linux, macOS, or Windows
* Memory: 4 GB RAM minimum
* Disk: 10 GB free space

== Installation Steps ==

# Download the installer from [http://example.com our site]
# Run the installer
# Follow the on-screen ''instructions''

Example 2: Table Content Migration

Input Textile file (comparison.textile):

h2. Feature Comparison

|_. Feature |_. Free |_. Pro |
| Storage | 5 GB | 100 GB |
| Users | 3 | Unlimited |
| Support | Email | 24/7 Phone |

Output Wiki file (comparison.wiki):

== Feature Comparison ==

{| class="wikitable"
! Feature !! Free !! Pro
|-
| Storage || 5 GB || 100 GB
|-
| Users || 3 || Unlimited
|-
| Support || Email || 24/7 Phone
|}

Example 3: Formatted Content Conversion

Input Textile file (article.textile):

h1. Introduction to Web Development

p. Web development encompasses *front-end*,
_back-end_, and -full-stack- approaches.

bq. "The web is for everyone."
-- Tim Berners-Lee

h2. Key Technologies

# HTML for structure
# CSS for styling
# JavaScript for interactivity

Output Wiki file (article.wiki):

= Introduction to Web Development =

Web development encompasses '''front-end''',
''back-end'', and full-stack approaches.


"The web is for everyone."
-- Tim Berners-Lee


== Key Technologies ==

# HTML for structure
# CSS for styling
# JavaScript for interactivity

Frequently Asked Questions (FAQ)

Q: What is MediaWiki markup?

A: MediaWiki markup (also called wikitext or wiki markup) is the markup language used by MediaWiki software, which powers Wikipedia, Fandom, and thousands of other wikis. It uses symbols like equals signs for headings (== Heading ==), triple apostrophes for bold ('''bold'''), double apostrophes for italic (''italic''), and pipe-based syntax for tables.

Q: How does Textile syntax map to Wiki syntax?

A: The key mappings are: Textile h1. becomes Wiki = Heading =, *bold* becomes '''bold''', _italic_ becomes ''italic'', "text":url becomes [url text], and Textile pipe tables become MediaWiki {| |} table syntax. Lists use similar symbols in both formats (*, #), so those translate directly.

Q: Can I use the output on Wikipedia?

A: Yes, the converted wiki markup is compatible with Wikipedia and all MediaWiki-based platforms. You can paste the output directly into the wiki editor. Note that Wikipedia has specific style guidelines and policies, so you may need to adjust formatting to match their conventions.

Q: How are Textile tables converted to Wiki tables?

A: Textile tables using pipe syntax (|_. Header | Cell |) are converted to MediaWiki table format using {| class="wikitable" for the table start, ! for headers, | for cells, |- for row separators, and |} for the table end. This produces properly formatted wiki tables with all content preserved.

Q: Does the converter handle Textile code blocks?

A: Yes, Textile inline code markers (@code@) are converted to MediaWiki <code> tags, and Textile block code sections (bc.) are converted to <pre> or <source> tags in wiki format. This ensures code examples are properly formatted on the wiki page.

Q: Can I migrate an entire Redmine wiki to MediaWiki?

A: Our converter is perfect for individual page conversion during migration. For a complete Redmine-to-MediaWiki migration, convert each Textile wiki page to wiki format. You can process multiple files by uploading them in batch. Internal Redmine links may need manual adjustment to match your new MediaWiki page structure.

Q: What happens to Textile images in the conversion?

A: Textile image syntax (!image_url!) is converted to MediaWiki image syntax ([[File:image_name]] or [image_url]). Note that MediaWiki typically uses uploaded files rather than external URLs, so you may need to upload images separately to your wiki and adjust the file references.

Q: Are Textile block quotes supported?

A: Yes, Textile block quotes (bq.) are converted to MediaWiki <blockquote> tags or indented text using the colon (:) prefix. The content within the block quote is preserved with proper formatting applied in the wiki syntax.