Textile to Word Converter - Legacy Wiki to DOCX

Convert Textile markup to Word DOCX format. Migrate Redmine wikis, legacy content management systems, and old documentation to Word.

Note: First conversion initializes Pandoc WebAssembly (~55MB download). Subsequent conversions are instant and work offline.

Drop Textile file here or click to browse

Accepts .textile, .txt files

Textile Input

Preview (Raw Text)

Enter Textile or upload a file to see preview

Standalone document with metadata

Document Metadata

Title

Author

Date

Subject

Textile Syntax Quick Reference

Textile	Description	Word Output
`h1. Heading`	Level 1 heading	Title style
`h2. Heading`	Level 2 heading	Heading 1 style
`bold`	Bold text	Bold formatting
`_italic_`	Italic text	Italic formatting
`@code@`	Inline code	Monospace font
`bc. code block`	Code block	Monospace paragraph
`* List item`	Bullet list	Bulleted list
`# Item`	Numbered list	Numbered list
`"link":url`	Hyperlink	Blue underlined link
`\|_. Header \|`	Table header	Bold table header
`\| Cell \|`	Table cell	Word table cell
`bq. Quote`	Blockquote	Indented quote

DOCX file downloaded

Security: Only process files from sources you trust. All processing happens locally in your browser.

Related Tools

AsciiDoc to EPUB - Technical Books to Eb…

Word to EPUB Converter - DOCX to Ebook F…

PPTX to ODP Converter - PowerPoint to Op…

RST to LibreOffice - Python Docs to ODT …

LaTeX to EPUB Converter - Academic Paper…

Markdown to RTF Converter - Universal Fo…

View all Document converters →

Frequently Asked Questions

Textile is a lightweight markup language used in Redmine project management, Basecamp Classic, and legacy CMS platforms. Converting to DOCX preserves historical documentation when migrating away from these systems, enabling content to be shared with modern Word users and archived in accessible formats.

Full Textile syntax including headers (h1. h2.), bold (*bold*), italic (_italic_), lists (# and *), tables (|cells|), links ("text":url), blockquotes (bq.), code blocks (bc.), and inline code (@code@). Also supports special characters, subscript (~text~), and superscript (^text^).

Yes. Export Textile content from Redmine wiki pages (copy from edit mode), paste into this tool, and convert to Word. Perfect for archiving project documentation, migrating to modern platforms like Confluence, or preparing content for non-technical stakeholders who need Word format.

Textile tables using |_. header| and |cell| syntax convert to native Word tables with proper borders and cell alignment. Header cells are formatted with bold styling. Complex tables with colspan/rowspan may need manual adjustment after conversion.

Wiki links like [[WikiPage]] are preserved as plain text in Word since cross-wiki references don't translate to standalone documents. External links using "text":http://url syntax become clickable hyperlinks. Attachment references (!filename.png!) need manual image embedding.

Excellent for Basecamp Classic. Export Textile-formatted messages, to-dos, and writeboards, then convert to Word for archival or import to modern project management tools. Preserves formatting while creating portable, shareable documents.

Currently single-file conversion. For batch processing, concatenate Textile files with separators (like horizontal rules using ---), then convert as one document. Each conversion produces a standalone DOCX file that downloads automatically.

Inline code using @code@ converts to monospace text in Word. Block code using bc. becomes monospace paragraphs. Syntax highlighting isn't preserved in DOCX, but code remains readable and properly indented for technical documentation.

Textile footnotes using [1] and fn1. syntax convert to Word footnotes with proper numbering. Perfect for academic papers and technical documentation migrated from legacy systems. Citation formatting depends on your original Textile implementation.

Yes. Enable 'Standalone document' and manually enter title, author, date, and subject from your legacy system. This metadata appears in Word's document properties, maintaining continuity when archiving Redmine, Basecamp, or CMS content for long-term storage.