If you're running a Garry's Mod server, you need a loading screen. The question is: which one should you use? Do you download a free GitHub template, build one from scratch, or pay for a hosted service like Lumescreen? This guide compares every option available in 2026 so you can decide based on facts, not marketing.
The landscape: what's available in 2026
GMod loading screen solutions fall into four categories. Each has different trade-offs:
- Self-hosted open-source templates — free GitHub projects you download and run on your own web server. Examples: CodeBrauer, MetroLoad, GoulpLoader, Lyr-7D1h.
- Self-hosted DIY — you write the HTML/CSS/JS yourself and host it anywhere (GitHub Pages, Netlify, your own VPS). Total control, total responsibility.
- Hosted SaaS (Lumescreen) — a managed service. You configure the screen in a dashboard, get a URL, and paste it into server.cfg. Nothing to host or maintain.
- Steam Workshop 'loading screens' — images and models that replace the default GMod background. These are NOT real loading screens; they don't use sv_loadingurl and can't show server info or progress. We'll clarify why they don't belong in this comparison.
The contenders at a glance
We analyzed 10 solutions in depth. Here's the summary:
| Solution | Type | Price | Progress Bar | Analytics | Maintained? |
|---|---|---|---|---|---|
| Lumescreen | SaaS | Free / €25/yr / €50 lifetime | ✅ Real CEF | ✅ Dashboard | ✅ Active |
| CodeBrauer | Self-hosted | Free (MIT) | ❌ No | ❌ No | ❌ Archived 2021 |
| MetroLoad | Self-hosted | Free | ❌ No | ❌ No | ❌ Abandoned |
| GoulpLoader | Self-hosted | Free (CC BY-NC) | ✅ Animated | ❌ No | ❌ 2017 |
| Lyr-7D1h | Self-hosted | Free (GPL-3.0) | ❌ No | ❌ No | ✅ 2024 |
| DIY (your own code) | Self-hosted | Free | Your call | Your call | Up to you |
Deep dive: what each option actually gives you
Lumescreen
Lumescreen is a hosted service. You pick a theme, customize it in a visual editor (no coding), and get a URL to paste into sv_loadingurl. The screen is served from Lumescreen's infrastructure, so there's nothing to host, update, or secure yourself.
- What's included: 15 themes (free + premium), real progress bar via CEF engine callbacks, background music (auto-compressed, CDN-hosted), staff list with avatars, live server info via GameDig query, analytics dashboard (connections, success rate, devices, peak hours), and a mute button (the only clickable element in-game).
- Pricing: Free tier: 1 screen, free themes, essential stats. Premium: €25/year or €50 one-time (lifetime) for unlimited screens, all themes, advanced analytics.
- Hosting: Handled by Lumescreen — no server, no HTTPS setup, no maintenance.
- When it's the right choice: You want something that works immediately, you don't want to maintain a web server, and you care about analytics and player retention data.
CodeBrauer Loading Screen
Once the gold standard of free GMod loading screens, CodeBrauer was archived in 2021. It's a PHP-based template with image slideshows, random OGG music, and Steam name display via URL parameters.
- What's included: Image slideshow, OGG music, Steam name/map display, rules page (MOTD), Bootstrap-based responsive layout.
- What's missing: Real progress bar (no CEF callbacks), no analytics, no live server info, no staff display.
- Hosting requirements: A web server with PHP 5.3+ and allow_url_fopen enabled. You need HTTPS for modern browsers.
- When it might still work: You already have a PHP server running, you just want something basic to replace the default screen, and you're comfortable fixing PHP deprecation issues yourself.
GoulpLoader
One of the few open-source templates with an animated progress bar. GoulpLoader is fully static (HTML/JS, no PHP), which makes it easy to host. However, its progress display is visual-only — it doesn't use real CEF engine callbacks.
- What's included: Animated progress bar, file download list display, rules panel, customizable banner and colors, music player, JSON config, responsive layout.
- What's missing: Real CEF callbacks (the progress bar is cosmetic, not driven by the engine), no analytics, no live server data, no staff/team display.
- Hosting requirements: Any static host (GitHub Pages, Netlify, VPS). No PHP needed.
- When it might still work: You want a free, easy-to-host option and don't need real progress or analytics. The fake progress bar at least looks better than nothing.
Lyr-7D1h/gmod-loadingscreen
The only open-source project with a 2024 commit. It's a modern, dark-themed static template with JavaScript configuration. Clean design, but functionally very basic.
- What's included: Customizable dark theme, responsive design, easy JS config file, demo page.
- What's missing: No progress bar at all (not even a fake one), no music player, no analytics, no server info.
- Hosting requirements: Static hosting. Trivial to deploy.
- When it might still work: You literally just want to replace the default background image with something that shows your server name. Nothing more.
DIY: building your own from scratch
If you're a web developer, you might prefer total control. Building your own loading screen gives you exactly what you want — at the cost of your time. Here's what's involved:
- You need to build: HTML/CSS/JS for the UI, plus the engine callback handlers (GameDetails, SetFilesTotal, SetFilesNeeded, DownloadingFile, SetStatusChanged). You'll need to test in GMod's CEF, which is more limited than desktop Chrome.
- You need to host: A public HTTPS web server. GitHub Pages works for static files. For dynamic features (live server queries), you need a backend or a third-party API.
- On the plus side: Total creative freedom, no recurring cost (beyond hosting), and you learn a lot about web development and GMod internals.
- The hidden cost: Time. Getting CEF callbacks right, handling edge cases (zero-file loads, Workshop downloads, fast cache loads), and maintaining compatibility across GMod updates is genuinely hard. Our progress bar deep-dive covers what you're signing up for.
The features that actually matter: a checklist
Use this checklist when evaluating any loading screen solution:
- Real progress bar — does it use GMod's CEF engine callbacks, or is it a fake CSS animation? Players can tell the difference: a bar that moves when nothing is happening feels dishonest.
- No click dependencies — the player can't click during loading. If your screen requires a click to start music or reveal content, it's broken in-game.
- HTTPS out of the box — mixed content (HTTP assets on an HTTPS page) causes the screen to render blank. You need everything served over HTTPS.
- Responsive at any resolution — players use everything from 1366×768 laptops to 3440×1440 ultrawides. Test your layout at both extremes.
- Bottom-right safe zone — GMod draws its native download box (~300×40 px) in the bottom-right corner. Essential content placed there gets covered.
- Analytics — do you know how many players make it through loading vs. drop off? Without data, you're guessing.
Cost comparison: real total cost of ownership
| Solution | Setup time | Monthly cost | Maintenance | Skill required |
|---|---|---|---|---|
| Lumescreen (free) | 5 minutes | €0 | None | None |
| Lumescreen (premium) | 5 minutes | ~€2/mo or €50 lifetime | None | None |
| CodeBrauer | 1-2 hours | €3-10 (hosting) | You fix PHP issues | PHP + server admin |
| GoulpLoader | 30 min | €0-5 (hosting) | You update if it breaks | Basic static hosting |
| DIY from scratch | 4-20 hours | €0-10 (hosting) | You maintain everything | Full-stack web dev |
The free open-source options have a zero dollar price tag but a real time cost. If your time is worth anything, the SaaS option often ends up cheaper once you factor in setup, debugging, and ongoing maintenance.
Security: the hidden risk of self-hosted templates
Self-hosted loading screens, especially PHP-based ones like CodeBrauer, introduce real security risks that most server owners don't consider:
- Steam API key exposure — many templates require a Steam Web API key stored in a config file. If that file is publicly accessible (common with misconfigured PHP), anyone can use your key.
- Outdated PHP dependencies — abandoned templates run on PHP libraries with known vulnerabilities. If your host automatically updates PHP, the template may break entirely.
- XSS via player names — a player with a malicious Steam name containing script tags can inject code into poorly-sanitized templates. Lumescreen handles sanitization server-side.
The final verdict: which one should you pick?
Here's the honest recommendation based on your situation:
- You just want it to work. Use Lumescreen. Five minutes of setup, zero maintenance, real progress, analytics, music, and live server data. The free plan covers one server. Premium is €25/year, or €50 once for lifetime access.
- You're a hobbyist who loves tinkering. Try GoulpLoader for a static template, or build your own. You'll learn a lot, but expect to spend an evening on it. And you'll still lack analytics and real CEF callbacks unless you implement them yourself.
- You already have a PHP server and want something free. CodeBrauer can work, but it's been archived since 2021. Expect PHP compatibility issues and zero support. Don't expose it to the web without auditing the code first.
- You want a comparison for your own DIY project. Read our sv_loadingurl complete guide and our progress bar tutorial — they cover everything you need to implement the engine callbacks correctly.
Whichever option you pick, test in-game before launch day. Desktop Chrome and GMod's CEF are not the same browser. If something breaks, our troubleshooting guide covers the most common causes.