DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing “Edit this page”. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too.

DokuWiki supports bold, italic, underlined and monospaced texts. Of course you can combine all these.

DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
Of course you can **__//''combine''//__** all these.

Note that the formatting markers have to directly enclose the text, so ** bold ** with spaces inside the markers will not be formatted.

You can use _subscript and ^superscript, too.

You can use <sub>subscript</sub> and <sup>superscript</sup>, too.

You can mark something as deleted as well.

You can mark something as <del>deleted</del> as well.

Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line.

This is some text with some linebreaks
Note that the two backslashes are only recognized at the end of a line
or followed by
a whitespace \\this happens without it.

This is some text with some linebreaks\\ Note that the
two backslashes are only recognized at the end of a line\\
or followed by\\ a whitespace \\this happens without it.

You should use forced newlines only if really needed.

DokuWiki supports multiple ways of creating links.

External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too.

DokuWiki supports multiple ways of creating links. External links are recognized
automagically: http://www.google.com or simply www.google.com - You can set
link text as well: [[http://www.google.com|This Link points to google]]. Email
addresses like this one: <andi@splitbrain.org> are recognized, too.

Internal links are created by using square brackets. You can either just give a pagename or use an additional link text.

Internal links are created by using square brackets. You can either just give
a [[pagename]] or use an additional [[pagename|link text]].

Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

You can use namespaces by using a colon in the pagename.

You can use [[some:namespaces]] by using a colon in the pagename.

For details about namespaces see namespaces.

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section.

This links to [[syntax#internal|this Section]].

Notes:

• Links to existing pages are shown in a different style from nonexisting ones.
• DokuWiki does not use CamelCase to automatically create links by default, but this behavior can be enabled in the config file. Hint: If DokuWiki is a link, then it's enabled.
• When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki.

DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].

Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet.

Windows Shares like [[\\server\share|this]] are recognized, too.

Notes:

• For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the “local zone”).
• For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization):

  conf/lang/en/lang.php

  <?php
  /**
   * Customization of the english language file
   * Copy only the strings that needs to be modified
   */
  $lang['js']['nosmblinks'] = '';

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this:

[[http://php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

You can add footnotes ¹⁾ by using double parentheses.

You can add footnotes ((This is a footnote)) by using double parentheses.

You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document.

==== Headline Level 3 ====
=== Headline Level 4 ===
== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:

You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height²⁾:

Resized external image:          

Real size:                        {{wiki:dokuwiki-128.png}}
Resize to given width:            {{wiki:dokuwiki-128.png?50}}
Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
Resized external image:           {{https://www.php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment.

{{ wiki:dokuwiki-128.png}}
{{wiki:dokuwiki-128.png }}
{{ wiki:dokuwiki-128.png }}

You can also set the alignment explicitly with a ?left, ?right or ?center parameter. This takes precedence over the whitespace alignment above and can be combined with a size.

{{wiki:dokuwiki-128.png?100&right}}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

{{ wiki:dokuwiki-128.png |This is the caption}}

For linking an image to another page see Image Links above.

DokuWiki can embed the following media formats directly.

If you specify a filename that is not a supported media format, then it will be displayed as a link instead.

By adding ?linkonly you provide a link to the media without displaying it inline

{{wiki:dokuwiki-128.png?linkonly}}

dokuwiki-128.png This is just a link to the image.

Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.

For example consider this embedded mp4 video:

{{video.mp4|A funny video}}

When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.

Additionally DokuWiki supports a “poster” image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work.

Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones.

• This is a list
• The second item
  • You may have different levels
• Another item

1. The same list but ordered
2. Another item
   1. Just use indention for deeper levels
3. That's it

  * This is a list
  * The second item
    * You may have different levels
  * Another item

  - The same list but ordered
  - Another item
    - Just use indention for deeper levels
  - That's it

Also take a look at the FAQ on list items.

DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.

The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.

DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:

• 8-)
• 8-O
• :-(
• :-)
• =)
• :-/
• :-\
• :-?
• :-D
• :-P
• :-O
• :-X
• :-|
• ;-)
• ^_^
• m(
• :?:
• :!:
• LOL
• FIXME
• DELETEME

Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ® “He thought 'It's a man's world'…”

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
"He thought 'It's a man's world'..."

The same can be done to produce any kind of HTML, it just needs to be added to the pattern file.

There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and “double quotes”. They can be turned off through a config option.

Some times you want to mark some text to show it's a reply or comment. You can use the following syntax:

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn't

Well, I say we should

Really?

Yes!

Then lets do it!

DokuWiki supports a simple syntax to create tables.

Table rows have to start and end with a | for normal rows or a ^ for headers.

^ Heading 1      ^ Heading 2       ^ Heading 3          ^
| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
| Row 2 Col 1    | some colspan (note the double pipe) ||
| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

As you can see, it's the cell separator before a cell which decides about the formatting:

|              ^ Heading 1            ^ Heading 2          ^
^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
^ Heading 4    | no colspan this time |                    |
^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect.

Apart from the rowspan syntax those cells should not contain anything else.

^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
| Row 2 Col 1    | :::                        | Row 2 Col 3        |
| Row 3 Col 1    | :::                        | Row 2 Col 3        |

You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.

This is how it looks in the source:

^           Table with alignment           ^^^
|         right|    center    |left          |
|left          |         right|    center    |
| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

Note: Vertical alignment is not supported.

If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it. The same is true for //__this__ text// with a smiley ;-).

<nowiki>
This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
</nowiki>
The same is true for %%//__this__ text// with a smiley ;-)%%.

You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code> or <file>.

This is text is indented by two spaces.

This is preformatted code all spaces are preserved: like              <-this

This is pretty much the same, but you could use it to show that you quoted a file.

Those blocks were created by this source:

  This is text is indented by two spaces.

<code>
This is preformatted code all spaces are preserved: like              <-this
</code>

<file>
This is pretty much the same, but you could use it to show that you quoted a file.
</file>

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. <code java> or <file java>.

/**
 * The HelloWorldApp class implements an application that
 * simply displays "Hello World!" to the standard output.
 */
class HelloWorldApp {
    public static void main(String[] args) {
        System.out.println("Hello World!"); //Display the string.
    }
}

The following language strings are currently recognized: 4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic

There are additional advanced options available for syntax highlighting, such as highlighting lines or adding line numbers.

When you use the <code> or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this:

<file php myexample.php>
<?php echo "hello world!"; ?>
</file>

myexample.php

<?php echo "hello world!"; ?>

If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: <code - myfile.foo>.

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort.

Example:

{{rss>http://slashdot.org/index.rss 5 author date 1h }}

• Xbox Manager: AI Already Being Used In Xbox Game Development - And Throughout the Game Industry by EditorDavid (2026/11/01 05:34)
• Binance Replenishes 90% of Stolen $6.3B, Pledges They'll Cover It All, Reopen Sunday by EditorDavid (2026/11/01 02:34)
• Computer Simulations Suggest Building Blocks of Life Didn't Arrive on Prehistoric Comets by EditorDavid (2026/10/31 22:50)
• Recycling ANSI Art: Tracing the Origins of BBS Logon Screens by EditorDavid (2026/10/31 21:50)
• French Lawmakers Back Per-Gigabyte Internet Traffic Tax by EditorDavid (2026/10/31 20:50)

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:

DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:

• Motorpsycho Collector Discography 2026-10-26 by Christian / OpenAI prototype
  Motorpsycho collector discography with Discogs integration, stable MP-REL IDs, purely visual restyling of the five free-text "===== Heading =====" sections every MP-REL wiki page is scaffolded with - Om denne utgaven, Collector-notater, Cover og emballasje, Historikk / merknader and Kilder, plus any hand-added custom heading a collector has written beyond those five - grouped into colour-coded, styled cards right after the page is rendered, with any section that has no actual content under it dropped from the page entirely instead of showing as clutter; nothing about how or where this text is stored changes, so DokuWiki's own search and page history keep working on it exactly as before, a form-based editor ("Rediger bilder og sideinnhold", reached from any release page) for the same five free-text sections (with its own image upload straight into the page for "Cover og emballasje", no more manual Media Manager + hand-typed wiki syntax, and "Kilder" auto-prefilled with a Discogs link when one applies) - instead of hand-editing the page's raw wikitext section by section, safely refusing to touch any page whose heading structure has been hand-restructured rather than guessing, local releases with user-contributed photo uploads (at submission and afterwards, credited to the original submitter; images on any release can now be managed by any @collector member, not just the original submitter, or by an admin; several images can be selected and uploaded in one go, whether registering a new Samleobjekter item or adding more to an existing one; upload hint text and error messages now reflect the server's own real PHP upload-size limits, not just the plugin's own setting, so a photo that is too large for the server explains why in plain language instead of the whole submission silently doing nothing) shown automatically on the standard MP-REL release pages via an in-page image lightbox (browse between all of a release's or a Samleobjekter item's photos, including straight from the Samleobjekter overview-table thumbnail, in a plugin-controlled overlay that stays centered and consistent across desktop, iPhone and Android instead of falling back to the browser's own native full-image viewer), an admin "create local release directly" quick form with the same optional photo upload, a public registration form (motorpsycho:registrer) with a repeatable matrix/runout fieldset so a multi-disc or multi-side pressing can be registered with one matrix reading per side/disc in a single submission, matrix catalogue/manual comparison, a discography view toggle ({{mpdiscography}}) letting visitors switch between grouped-by-master (default) and a full flat list without a page reload, with the last choice remembered per browser, per-user MP-REL collections with structured per-copy condition/price/date/location fields, an admin-only one-time personal Discogs collection CSV import into "Min samling" (matches only against releases already in the MP-REL base, never overwrites an already-filled field - only fills in what is blank, auto-detects a comma or semicolon delimiter and both ISO and Norwegian day.month.year "Date Added" formatting so a copy that was opened and re-saved through Excel still imports correctly), a {{mpquicklinks}} tag for prominent button-style shortcuts to a centrally-defined set of "most important" pages, now including the Samleobjekter overview alongside the discography and matrix list by default (or a custom ref|label list), placeable on any page, memorabilia (non-release collectibles) with optional group-restricted submission, an admin-configurable Type list (memorabilia_types), a grouped-by-type overview with a full-list toggle for pages with many items, a collapsible registration/edit form, per-item photo uploads with overview-table thumbnails and owner/admin editing across pages, one-click 90° image rotation (either direction) for already-uploaded memorabilia and MP-REL photos so a sideways phone photo can be fixed in place without re-uploading, an optional read-only memorabilia view for pages that should not expose editing, client-side sortable/filterable data tables, moderated contributions, release/title search, local-to-master relationships, a one-click discography update that refreshes already-known masters/releases (picking up Discogs-side edits, not just new items) without letting a master or release credited to more than one scope artist have an already-known field blanked out by a later, less complete listing pass, and auto-chains the matrix update, a rolling discography changelog ({{mpdiscographychangelog}}) recording new/changed masters and releases, a "for sale now" Discogs Marketplace view ({{mpforsale}}) kept converging by the same unattended update (with a guaranteed time slice of its own so a busy discography sync can't starve it), always freshly re-verified for whatever is currently listed while staying at zero extra API cost for the rest of the discography, labeled with a configurable currency (forsale_currency) and a per-row "last confirmed" timestamp, an optional token-secured cron endpoint for unattended scheduled updates, incremental matrix indexing, safe local deletion, collector variants and canonical wiki pages, and, on narrow (mobile) screens only, the shared data tables (Samleobjekter, diskografi, matrix-katalog, "Min samling", "til salgs" and endringslogg) now switch to a stacked card layout with each column's label shown above its value instead of a horizontally-scrolling wide table, with desktop/tablet rendering completely unaffected, and Samleobjekter (memorabilia) no longer tracks or displays a purchase price, currency or purchase date at all - unlike the Discogs-synced "Min samling" collection where value still matters, Samleobjekter is not synced against Discogs, so its per-item "Pris"/"Kjøpt" columns and its aggregate registered-value summary line have been dropped (where an item was possible to buy is still kept and shown, just not what it cost), and Samleobjekter items can now be deleted directly from the public add/edit form ({{mpmemorabiliaadd}}) itself, not only via the admin panel - restricted to the item's original creator or an admin (the same permission check that already gates editing), shown as a separate button with its own client-side confirmation prompt so it can't be triggered or confused with saving edits, and local MP-REL releases (not linked to Discogs) now have a collapsible "Rediger metadata" form straight on their own release page - the same local metadata fields as the admin panel (artist, title, year, country, format, label, catalogue number, related Discogs release, master, relation, source note), available to admins, any @collector member and the original submitter, touching only those fields, refusing to overwrite a change someone else saved in the meantime, keeping a per-field change history, and keeping the page's auto-generated title heading in step with a changed title, and a public marketplace ("Torget": {{mpmarket}}, {{mpmarketadd}}) for buying, selling and trading - release listings must link to an existing MP-REL, memorabilia listings may link to an MP-ITEM, trade wishes may optionally link to a specific release or item, prices always in NOK, listings auto-hide 14 days after the owner last confirmed them (never auto-deleted), seller name and e-mail contact shown to logged-in visitors only, posting limited to marketplace_contributor_groups (default medlem,collector), and an admin moderation section; each listing shows the release format (as in the discography) or memorabilia type in its own filterable column and as a badge, "My listings" and the post form can live on their own page (marketplace_mine_page) linked from the top of the marketplace, and several listings can be confirmed at once (checkboxes, "confirm selected", "confirm all active"); Samleobjekter (MP-ITEM) now get the same "Torget" box as MP-REL pages (sell this / want to buy / trade away, opening the form prefilled with the item, plus the item's active listings), and the Samleobjekter overview ({{mpmemorabilia}} / {{mpmemorabiliaview}}) shows a compact per-row marketplace line with active listings and quick Sell / Buy / Trade links.
• Info Plugin 2020-06-04 by Andreas Gohr
  Displays information about various DokuWiki internals
• Wrap Plugin 2026-06-02 by Anika Henke
  Universal plugin which combines functionalities of many other plugins. Wrap wiki text inside containers (divs or spans) and give them a class (choose from a variety of preset classes), a width and/or a language with its associated text direction.