Remember the spiral-bound guide with the fold-out map? Same idea: every item, every boss, every secret room. Except this one gets the patch notes the day they ship.
How it works
Bring what you already have. Spreadsheets, a MediaWiki export or a pile of screenshots all work.
Import a MediaWiki dump, a CSV of items or a shared spreadsheet. Images and page history come along.
Pick page templates for items, characters, bosses and quests, then choose which fields show in each infobox.
Your pages go live with search, maps and threads. Invite editors and set who can approve changes.
“We moved 9,000 pages over a weekend. Page views doubled in a month because people stopped bouncing off the ads.”
Why it works
01 Infoboxes
The Ashen Halberd's infobox shows rarity, damage, attack speed and where it drops, in the same place as every other weapon. Because the stats are data, the weapons table and the build calculator update when the page does.
02 Maps
Pins for chests, vendors and bosses, grouped into regions you can toggle. Click a pin to open its wiki page; filter by layer to find the last three lore notes in the Sunken Quarter.
03 Discussions
Each page carries its own discussion thread. Upvotes push the tested strategy to the top, editors can promote an answer into the page, and moderators see reports in one queue.
Pricing
Fan wikis never pay. Studios pay for official branding, staff tools and support.
$79per month
For studios running an official wiki. Prices in USD. Studio plans can be billed annually for two months free. Cancel any time and export everything.
Choose StudioEverything included:
Testimonials
Sample reviews written for this template. Replace them with your own.
“Patch 2.4 changed 180 weapons. The diff tool updated every infobox in an hour. On our old host that was two weeks of volunteers copy-pasting.”
“The map is what sold our community. People were sharing screenshots of a spreadsheet with coordinates. Now they share a link.”
“New accounts go through the edit queue, so the vandalism after every big streamer mention just doesn't reach readers anymore.”
“We took over the fan wiki officially and kept every editor's history and role. Nobody felt like their work got absorbed by the studio.”
“I play on a cheap phone. The old wiki took eight seconds to load a boss page. This one opens before I finish the loading screen.”
“Threads on each page replaced half our help channel. The best answer gets upvoted and an editor folds it into the guide.”
FAQ
Still unsure? Our support team includes former wiki admins, and they reply within a day.
Yes. Community wikis get unlimited pages, editors, maps and threads. We show at most one sponsor slot per page, never inside the article, never autoplaying, and never on mobile above the infobox.
Upload a MediaWiki XML export and we bring over pages, templates, images and edit history. Most templates map to infoboxes automatically; we flag the ones that need a manual look. A 10,000-page wiki usually takes under an hour.
Your community does. Text is published under the license you choose (CC BY-SA by default), and admins can export the whole wiki as XML, JSON or CSV at any time, including history.
Admins assign roles: admin, editor, trusted contributor and reader. You can require review for edits from new accounts, lock pages during big launches, and roll back a vandal's edits across the wiki in one click.
The studio upgrades the existing wiki rather than starting a new one. Editors keep their accounts, history and roles, and admins decide together with the studio which staff get elevated permissions.
Yes. Mark sections, map pins or whole pages as spoilers. Readers see a blurred block and choose whether to reveal it, and you can lift spoiler tags in bulk a few weeks after a release.
The interface is available in 14 languages and wikis can run several language editions under one domain, with linked pages so a translator can see what changed in the English source.