GZDoom

GZDoom is a feature centric port for all Doom engine games, based on ZDoom, adding an OpenGL renderer and powerful scripting capabilities.

  • Game Servers
  • Home Automation
GZDoom is a feature centric port for all Doom engine games, based on ZDoom, adding an OpenGL renderer and powerful scripting capabilities.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

56/100 Fair

Maintained
100last commit 11 days ago
Popular
176 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 38 days ago

GitHub stars
6
Open issues
0
Last commit
2026-11-10
Latest release
g4.14.2-ls83
License
GPL-3.0
Activity
declining

Checked 10 days ago - source: GitHub (linuxserver/docker-gzdoom)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set PUID/PGID and mount a config volume This LinuxServer.io container follows the usual convention: set PUID and PGID to your user and group IDs so created files are owned correctly, and mount a persistent /config volume so your configuration and WAD files survive container updates. source

Fetched 18 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I reset GZDoom settings if they are broken?

Delete the username.ini file in your GZDoom folder to return to the defaults.

What helped someone identify GZDoom crashing before it started?

Trying UZDoom helped identify the problem, and switching to UZDoom was not necessary.

Where can GZDoom problems be tracked?

Problems can be tracked in the ZDoom/gzdoom GitHub issue tracker.

How do I map user permissions in the linuxserver/gzdoom container?

Use PUID and PGID for easy user mappings.

Answers sourced from forum.zdoom.org, github.com, github.com, www.reddit.com

Community

Collected 53 days ago - public community threads