Convert MediaWiki to ORG

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

MediaWiki vs ORG Format Comparison

Aspect MediaWiki (Source Format) ORG (Target Format)
Format Overview
MediaWiki
MediaWiki Markup Language

Wiki markup language created in 2002 for Wikipedia and MediaWiki software. Offers comprehensive syntax for collaborative content creation with templates, links, categories, and table markup. The standard format for the world's largest online encyclopedia and thousands of wikis.

Wiki Format Wikipedia Standard
ORG
Emacs Org-mode Format

Powerful plain text markup format for Emacs, created by Carsten Dominik in 2003. Combines document authoring, task management, time tracking, and literate programming in a single format. Supports hierarchical outlines, TODO items, tables, code blocks, and export to multiple formats.

Emacs Format Outliner
Technical Specifications
Structure: Plain text with wiki markup syntax
Encoding: UTF-8
Format: Human-readable markup language
Compression: None (plain text)
Extensions: .wiki, .mediawiki, .mw
Structure: Plain text with outline-based markup
Encoding: UTF-8
Format: Human-readable outline markup
Compression: None (plain text)
Extensions: .org
Syntax Examples

MediaWiki uses wiki-specific markup:

== Heading Level 2 ==
=== Heading Level 3 ===

'''Bold''' and ''italic''

* Unordered list
# Ordered list

[[Internal Link]]
[https://example.com External]

{| class="wikitable"
! Header
|-
| Data
|}

Org-mode uses asterisk-based headings:

** Heading Level 2
*** Heading Level 3

*Bold* and /italic/

- Unordered list
1. Ordered list

[[Internal Link]]
[[https://example.com][External]]

| Header |
|--------|
| Data   |
Content Support
  • Section headings (6 levels)
  • Bold, italic, underline formatting
  • Internal and external links
  • Templates and transclusion
  • Complex table markup
  • Categories and namespaces
  • References and citations
  • Mathematical formulas
  • Image galleries
  • Redirect pages
  • Hierarchical outline headings
  • Bold, italic, underline, strikethrough
  • Internal and external links
  • Source code blocks with execution
  • Spreadsheet-capable tables
  • TODO items and task management
  • Time tracking and deadlines
  • LaTeX math formulas
  • Property drawers and metadata
  • Export to HTML, PDF, LaTeX, etc.
Advantages
  • Comprehensive template system
  • Built-in cross-page linking
  • Category organization system
  • Mature collaborative editing
  • Rich reference/citation support
  • Huge user community (Wikipedia)
  • Combines documents and tasks
  • Executable code blocks (Babel)
  • Built-in spreadsheet in tables
  • Agenda views and scheduling
  • Export to many formats
  • Extremely powerful in Emacs
  • Literate programming support
Disadvantages
  • Complex syntax for tables and templates
  • Requires MediaWiki to render
  • Not suitable for task management
  • No code execution capability
  • Limited outside wiki environments
  • Best experience requires Emacs
  • Steep learning curve for full features
  • Limited collaborative editing
  • No built-in web rendering
  • Smaller community than Markdown
Common Uses
  • Wikipedia articles
  • Internal corporate wikis
  • Knowledge base documentation
  • Collaborative content writing
  • Community-driven encyclopedias
  • Personal knowledge management
  • Project planning and task tracking
  • Research notes and papers
  • Literate programming documents
  • Technical documentation
  • Time tracking and reporting
Best For
  • Large-scale collaborative wikis
  • Encyclopedia-style content
  • Structured community knowledge
  • Web-based documentation
  • Personal productivity systems
  • Research and academic writing
  • Technical note-taking
  • GTD (Getting Things Done) workflows
Version History
Introduced: 2002 (Wikipedia/MediaWiki)
Current Version: Evolves with MediaWiki software
Status: Actively maintained
Evolution: Regular updates with MediaWiki releases
Introduced: 2003 (Carsten Dominik)
Current Version: Org 9.x (bundled with Emacs)
Status: Actively developed
Evolution: Regular releases with GNU Emacs
Software Support
MediaWiki: Native format
Pandoc: Full read/write support
Wikipedia: Native editing format
Other: Visual Editor, wiki platforms
GNU Emacs: Full native support (Org-mode)
Pandoc: Read/write support
Vim: vim-orgmode plugin
Other: Logseq, Orgzly (Android), VS Code extensions

Why Convert MediaWiki to ORG?

Converting MediaWiki markup to Org-mode format allows you to bring wiki content into the powerful Emacs Org-mode ecosystem. Org-mode is renowned for combining document authoring with task management, time tracking, and literate programming capabilities. By converting wiki content to Org format, you gain the ability to enrich it with TODO items, scheduling, code execution, and the full suite of Org-mode productivity features.

MediaWiki and Org-mode share the concept of plain text markup with headings and formatting, but they serve different purposes. MediaWiki is optimized for collaborative web content, while Org-mode excels at personal knowledge management and document production. The conversion maps MediaWiki headings (== ==) to Org headings (* asterisks), formatting markers (''' to *, '' to /), links, lists, and tables, creating a well-structured Org document from the wiki source.

Org-mode tables offer capabilities beyond what MediaWiki tables provide. In Org-mode, tables can include spreadsheet-style formulas, automatic calculations, and column alignment. Wiki tables are converted to Org pipe tables, which can then be enhanced with these computational features. This makes Org-mode particularly valuable for technical and scientific content that includes data tables.

The converted Org files can be further exported to multiple output formats including HTML, PDF (via LaTeX), DOCX, and presentation slides, making Org-mode a versatile intermediate format for content publishing. Users of tools like Logseq or Orgzly can also work with Org files on mobile devices, extending the usability of the converted wiki content beyond the desktop Emacs environment.

Key Benefits of Converting MediaWiki to ORG:

  • Emacs Integration: Full Org-mode power for editing, navigation, and export
  • Task Management: Add TODO items, deadlines, and scheduling to wiki content
  • Code Execution: Embed and run code blocks with Org Babel
  • Multi-Format Export: Export to HTML, PDF, LaTeX, DOCX, and slides
  • Spreadsheet Tables: Add calculations and formulas to converted tables
  • Personal Knowledge Base: Organize wiki content in your personal system
  • Plain Text: Version-controllable, lightweight, and future-proof

Practical Examples

Example 1: Wiki Article to Org Document

Input MediaWiki file (language.wiki):

== Python Programming ==

'''Python''' is a high-level [[programming language]].

=== Features ===
* Dynamic typing
* Automatic memory management
* Extensive [[Standard Library|standard library]]

=== Code Example ===

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


[[Category:Programming]]

Output ORG file (language.org):

* Python Programming

*Python* is a high-level [[programming language]].

** Features
- Dynamic typing
- Automatic memory management
- Extensive [[Standard Library][standard library]]

** Code Example
#+begin_src python
def hello():
    print("Hello, World!")
#+end_src

Example 2: Wiki Project Page to Org Task List

Input MediaWiki file (project.wiki):

== Website Redesign ==

=== Phase 1: Planning ===
* Research competitor websites
* Create wireframes
* {{Done}} Define color palette

=== Phase 2: Development ===
* Build responsive layout
* Implement navigation
* Integrate [[CMS]]

{| class="wikitable"
! Task !! Hours !! Assignee
|-
| Design || 40 || Alice
|-
| Frontend || 60 || Bob
|-
| Backend || 80 || Carol
|}

Output ORG file (project.org):

* Website Redesign

** Phase 1: Planning
- [ ] Research competitor websites
- [ ] Create wireframes
- [X] Define color palette

** Phase 2: Development
- [ ] Build responsive layout
- [ ] Implement navigation
- [ ] Integrate [[CMS]]

| Task     | Hours | Assignee |
|----------+-------+----------|
| Design   |    40 | Alice    |
| Frontend |    60 | Bob      |
| Backend  |    80 | Carol    |

Example 3: Wiki Reference to Org Notes

Input MediaWiki file (notes.wiki):

== Meeting Notes ==

'''Date:''' March 9, 2026

=== Attendees ===
* [[User:Alice|Alice Smith]]
* [[User:Bob|Bob Jones]]

=== Decisions ===
# Approve Q2 budget of $50,000
# Launch new product by June
# Hire two additional developers

{{Action|Follow up with HR by March 15}}

=== Next Meeting ===
March 16, 2026 at 2:00 PM

Output ORG file (notes.org):

* Meeting Notes
:PROPERTIES:
:DATE: March 9, 2026
:END:

*Date:* March 9, 2026

** Attendees
- Alice Smith
- Bob Jones

** Decisions
1. Approve Q2 budget of $50,000
2. Launch new product by June
3. Hire two additional developers

** TODO Follow up with HR by March 15

** Next Meeting
March 16, 2026 at 2:00 PM

Frequently Asked Questions (FAQ)

Q: What is MediaWiki markup?

A: MediaWiki markup is the formatting language used by Wikipedia and MediaWiki-powered wikis. Created in 2002, it uses syntax like == headings ==, '''bold''', ''italic'', [[links]], templates, and table markup for collaborative web content creation. It is the most widely used wiki markup language in the world.

Q: Do I need Emacs to use ORG files?

A: While Emacs provides the richest Org-mode experience with features like agenda views, code execution, and live previews, Org files are plain text and can be viewed and edited in any text editor. Tools like Logseq, Orgzly (Android), and VS Code extensions also provide Org-mode support outside of Emacs.

Q: How are MediaWiki headings mapped to Org headings?

A: MediaWiki headings use equals signs (== H2 ==, === H3 ===) while Org-mode uses asterisks (* H1, ** H2, *** H3). The conversion maps each wiki heading level to the corresponding Org heading level, preserving the document hierarchy. Org headings also serve as outline nodes that can be folded and expanded in Emacs.

Q: Can I add TODO items to the converted Org file?

A: Yes! One of the key benefits of Org-mode is task management. After conversion, you can add TODO keywords to any heading (e.g., ** TODO Review section), set deadlines (DEADLINE: date), add scheduled dates, and track progress. This makes Org ideal for turning wiki documentation into actionable project plans.

Q: How are wiki tables converted to Org tables?

A: Wiki tables are converted to Org pipe tables, which use | characters to separate columns. Org tables are aligned automatically in Emacs and support spreadsheet formulas (e.g., #+TBLFM: for calculations). Header rows are separated by |---+---| dividers. The table content and structure are preserved during conversion.

Q: What happens to MediaWiki code blocks?

A: MediaWiki <source> and <syntaxhighlight> blocks are converted to Org source blocks (#+begin_src language ... #+end_src). In Emacs, these blocks support syntax highlighting and can be executed using Org Babel, which supports dozens of programming languages. Inline <code> tags become Org verbatim markers (=code=).

Q: Can I export the Org file to other formats?

A: Yes, this is one of Org-mode's greatest strengths. From Emacs, you can export Org files to HTML, PDF (via LaTeX), DOCX (via ODT), Markdown, plain text, Beamer presentations, and more. This makes Org an excellent intermediate format for publishing wiki content in multiple output formats.

Q: Are MediaWiki links compatible with Org links?

A: Both formats use double brackets for links, which makes the conversion natural. MediaWiki [[target|text]] becomes Org [[target][text]]. External links are also converted: [https://url label] becomes [[https://url][label]]. Org links can point to files, headings, URLs, and custom protocols, providing even more flexibility than wiki links.