New · Interactive maps
Game wiki hosting
Ditch the ad wall. Keep the lore.
Your community wrote 9,000 pages for free. They deserve better than autoplay video and six banner slots. Spawnpoint Wiki is fast, clean and free for fan wikis.
Why it works
Made for the way players actually look things up
Game wikis are databases wearing a costume. Spawnpoint Wiki treats them that way.
Infoboxes
Every item, one consistent card
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.
Maps
Maps players can actually search
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.
Discussions
Arguments about builds, finally organized
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.
- Infoboxes from data. Define an item or character schema once.
- Interactive maps. Upload a map, drop pins for loot, bosses and secrets, group them into layers.
- Patch-note diffs. Paste a patch's data sheet and see every stat that changed.
- Discussion threads. Every page gets its own thread for builds, theories and corrections, with upvotes so the useful answer sits on top.
- Roles and moderation. Admins, editors, trusted contributors and readers.
- Your own domain. Run the wiki on wiki.
Features
Built for wikis with 4,000 items and a patch every month
Game wikis are databases wearing a costume. Spawnpoint Wiki treats them that way.
Infoboxes from data
Define an item or character schema once. Every page gets a consistent infobox, and stats feed sortable tables across the wiki.
Interactive maps
Upload a map, drop pins for loot, bosses and secrets, group them into layers. Hide late-game pins behind a spoiler toggle.
Patch-note diffs
Paste a patch's data sheet and see every stat that changed. Approve the diff and 300 pages update together.
Discussion threads
Every page gets its own thread for builds, theories and corrections, with upvotes so the useful answer sits on top.
Roles and moderation
Admins, editors, trusted contributors and readers. Page locks, edit queues for new accounts and one-click rollback.
Your own domain
Run the wiki on wiki.yourgame.com with free SSL. Community wikis can use any domain they already own.
How it works
From pinned messages to a real wiki in a weekend
Bring what you already have. Spreadsheets, a MediaWiki export or a pile of screenshots all work.
- 1
Bring your data
Import a MediaWiki dump, a CSV of items or a shared spreadsheet. Images and page history come along.
- 2
Shape your templates
Pick page templates for items, characters, bosses and quests, then choose which fields show in each infobox.
- 3
Publish the wiki
Your pages go live with search, maps and threads. Invite editors and set who can approve changes.
Testimonials
Editors and studios who moved in
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.”
Nadia PetrovaWiki Admin, Hollowdeep“The map is what sold our community. People were sharing screenshots of a spreadsheet with coordinates. Now they share a link.”
Owen GallagherCommunity Lead“New accounts go through the edit queue, so the vandalism after every big streamer mention just doesn't reach readers anymore.”
Yuki TanakaModerator“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.”
Samuel OseiProducer, Tidebreaker“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.”
Lucía RomeroPlayer and editor“Threads on each page replaced half our help channel. The best answer gets upvoted and an editor folds it into the guide.”
Ravi KapoorChat Server Admin
Pricing
Free for communities. Fair for studios.
Fan wikis never pay. Studios pay for official branding, staff tools and support.
Community
For fan-run wikis of any size.
$0forever
Start a free wiki- Unlimited pages and editors
- Interactive maps
- Discussion threads
- One sponsor slot per page
Studio
Most popularFor studios running an official wiki.
$79per month
Choose Studio- No ads at all
- Official studio badge
- Patch-note diff tool
- Staff roles and audit log
- Priority support
Publisher
For publishers with several games.
$349per month
Talk to sales- Up to 10 wikis
- SSO for staff
- Data API access
- Dedicated success manager
Prices in USD. Studio plans can be billed annually for two months free. Cancel any time and export everything.
FAQ
Questions from wiki admins
Still unsure? Our support team includes former wiki admins, and they reply within a day.
Is it really free for fan communities?
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.
Can we move our existing wiki?
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.
Who owns the content?
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.
How does moderation work?
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.
What happens if a studio wants to make our fan wiki official?
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.
Can we use spoiler protection?
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.
Do you support our language?
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.