Widelands is a free, open source real-time strategy game with singleplayer campaigns and a multiplayer mode. The game was inspired by Settlers II™ (© Bluebyte) but has significantly more variety and depth to it. Still, it is easy to get started through playable tutorials.

For more information read the full description and look at some screenshots. Or you can download the latest release and just try it out for yourself.

This website is the home of the Widelands community. You are invited to visit the forums: discuss strategies, find partners for multiplayer games, help with translations, voice your opinion on graphics, music and much more.

Widelands is currently (and will always be) under development - you can get a feel for what is worked on by looking at the changelog. Everybody is invited to help out too - we need 2D and 3D artists, sound effect creators, composers, map makers, translators, test players, web programmers and C++ coders. All skill levels are welcome - just start working on something or ask in the forums for pointers.

Server Maintenance

There will be a server downtime which affects all services we provide:

• Website
• Metaserver (playing online)
• Add-Ons (up- and download)

The downtime is planned around 2026-10-03 or/and 2026-10-04.

Because the whole server needs an update, including OS and the Website-code, there might be some breakage close after the update has been finished.

Widelands 1.3.1 Released

The Widelands Development Team is proud to announce the immediate availability of the stable point release Widelands 1.3.1.

Windows installer Intel 64 bit · Intel 32 bit · ARM 64 bit
Mac packages (64 bit) MacOS ≥ 12 Intel · MacOS ≥ 12 ARM
Linux (64 bit) AppImage
Source code as .zip · .tar.gz
Checksums and signatures for all downloads
List of all downloads

This point release fixes a severe multiplayer desync found in Widelands 1.3. Note that it is not possible to combine the versions 1.3 and 1.3.1 in a network game.

Widelands is distributed for Windows (Intel 64-bit and 32-bit and Arm), Mac OS X ≥ 12.0 (Intel 64-bit and Arm), Linux (AppImage, 64 bit), and in source code. For Linux users, we also provide a Flatpak package and a Ubuntu PPA and try to make compiling as easy as possible, and most distributions will pick up Widelands 1.3.1 into their repositories very quickly. Both binary and source packages are available under the links below and from our Download page.

If you like what you see, have a look around this site. You may also want to check the forums and our IRC channel, #widelands on LiberaChat, to arrange multiplayer games with other players.

We especially welcome every helping hand: Help us find bugs, translate the game, add new scenarios or features! If you want to get even more involved in the further development of Widelands, you can meet us on the forum at https://www.widelands.org/ or subscribe to widelands-public@lists.sf.net on http://lists.sourceforge.net/mailman/listinfo/widelands-public. Releases are also announced to widelands-announce@lists.sf.net (https://sourceforge.net/projects/widelands/lists/widelands-announce).

Blocking AI-Generated Content

The Widelands Development Team has passed a resolution to reject AI-generated content contributions (code, graphics, music, and others) to the Widelands source code and repositories.

We hold that AI-generated content generally stands on dubious ethical and legal grounds, as it violates the copyright of creators whose work was scraped for the AI's training data set without their permission and without due attribution. Also, we find that it is frequently of low overall quality and/or is overly generic and fails to embrace requirements specific to Widelands.

Pull requests that have been generated by AI may in the future be closed without review.

Widelands is created by people, for people.

The change does not impact add-on uploads, which are each add-on author’s own responsibility, although such add-ons may be moderated more critically by the add-on server maintainers.
Translations are also not in the scope of this policy, and every language team can define its own policy with regard to machine translation.

Read the policy’s discussion thread here.