DokuWiki to Textile Converter
FileFlip converts DokuWiki to Textile entirely inside your browser, using Pandoc compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert a DokuWiki file to Textile?#
- Drop your DokuWiki file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to Textile and the conversion starts on its own. FileFlip downloads 65.8 MB of WebAssembly the first time and nothing after that, then runs Pandoc on your own machine.
- Save the Textile file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting DokuWiki to Textile lose quality?#
Not in the sense of pixels or samples. Converting DokuWiki to Textile rebuilds the file in Textile's own model rather than re-encoding it, so everything Textile can represent comes through exactly and anything it cannot has to be dropped. Expect the words to come through exactly and the page breaks to move.
Is it safe to convert DokuWiki files online?#
Yes, because nothing is uploaded. FileFlip converts DokuWiki files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What DokuWiki to Textile actually does to the file#
Converting DokuWiki to Textile runs on Pandoc, downloads 65.8 MB of WebAssembly the first time and nothing after that, rebuilds the file in the target's own model, keeps selectable text and page layout.
| Engine | Pandoc |
|---|---|
| Conversion path | One step: DokuWiki → Textile |
| Downloaded to your browser | 65.8 MB, once, then cached by your browser |
| Quality | Rebuilt in the target's model |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Selectable text | Kept | Carried through into the converted file. |
| Page layout | Kept | Carried through into the converted file. |
What is a DokuWiki file?#
A DOKUWIKI file holds a page written in DokuWiki syntax, the plain-text markup that DokuWiki itself stores as a .txt file on disk rather than in a database.
Keep pages in DokuWiki syntax while the wiki is actually running DokuWiki, since that's the renderer every construct is written for.
Convert DokuWiki syntax to another format when retiring the wiki or moving its content onto a different platform.
What is a Textile file?#
A TEXTILE file holds Textile markup, Dean Allen's 2002 lightweight syntax for the Textpattern content management system, using punctuation like *bold*, _italic_ and bq. for a blockquote to generate HTML.
Use Textile when working inside a system that already expects it, such as a Redmine wiki or a long-running Textpattern site.
Convert Textile to Markdown when moving content to a modern platform, since almost everything built in the last decade expects Markdown instead.
DokuWiki to Textile questions people ask#
What program opens a DokuWiki file?
A DokuWiki page is a plain-text file, so any text editor opens it, but the markup only renders as a formatted page inside a running DokuWiki install. Viewing it as intended means either running DokuWiki or converting the file to a format like HTML or Markdown first.
Why does DokuWiki store pages as text files instead of a database?
DokuWiki was built to skip a database entirely, storing every page as a plain-text file in this syntax on the server's filesystem. That makes a DokuWiki install easy to back up with a plain file copy and easy to read even without the software running.
Can I convert a DokuWiki page to Word or PDF?
Yes, DokuWiki syntax converts to formats like DOCX or PDF by first turning the markup into a structured document, which renders headings, links, and tables. Syntax that comes from a specific DokuWiki plugin may not convert, since only DokuWiki itself with that plugin installed knows how to render it.
What is a Textile file used for?
A Textile file holds plain text written in Textile markup, a lightweight syntax from the early blogging era that's still the default markup in Redmine's wikis and issue tracker. Textile source is written to be converted to HTML, either by Textpattern, Redmine or a standalone library like RedCloth.