Official media referenceDirect answer
Warhounds had an official Steam Next Fest demo in February 2026; availability after the full launch must be checked on the live Steam page.
How to use this page
The demo offered more than a single tutorial, but it remains a pre-launch build and should not be used as proof of current balance or save compatibility.
What is verified
- Two tutorial missions and five combat missions were announced.
- Four Veterans and recruitable rookies were playable.
- The ship base and strategic Free Play were included.
- No reliable official promise of demo-to-release save transfer was found.
Evidence scope
Verified against sources on August 14, 2026The Warhounds demo page explains what the public slice was for, what it contained and how to compare it with the released game. Availability and files are version-sensitive, so the Steam store and developer announcements remain the authority.
Documented demo scope
The launch material described a demo with two tutorials and five combat missions across named environments, plus Free Play for replaying the tactical systems. This is a useful onboarding package: tutorials teach the basic vocabulary, missions show different objective pressures and Free Play helps isolate combat experiments. It should be read as a curated slice rather than a promise that every launch mission behaves the same way.
- Use tutorials to learn controls before testing builds.
- Use combat missions to compare objectives and terrain.
- Use Free Play for repeatable tactical experiments.
What the demo cannot answer
A demo cannot establish the full recruitment economy, long-term injury pressure, every base upgrade, or the quality of late campaign missions. It also cannot prove that a mechanic shown in a pre-release build has unchanged values after launch. If a question involves cost, unlock, performance or language, record the exact build and then verify the current store or in-game screen.
- Do not publish demo numbers as universal values.
- Do not infer the entire campaign from five missions.
- Recheck language and platform data on Steam.
How to test the demo responsibly
Start with a clean save and record the build number. Complete both tutorials without rushing, then play missions with different squad compositions. Note which information the UI gives before an action, what changes after the action, and whether the result can be reproduced. When reporting a problem, attach the mission name, objective, platform, save state and a short reproduction path rather than a screenshot alone.
- Record the build before starting.
- Repeat a suspicious result with the same setup.
- Report mission, objective and reproduction steps together.
Demo testing checklist
- Record the demo build and download source.
- Complete both tutorials and note unclear instructions.
- Test at least two squad compositions.
- Separate demo limitations from launch bugs.
- Check the current Steam listing before sharing availability.
Frequently asked questions
How many missions were in the Warhounds demo?
The documented public demo scope was two tutorials and five combat missions, with Free Play also mentioned. Confirm current availability on Steam.
Was the demo the full game?
No. It was a curated tactical slice; the released game adds the broader campaign and strategic management.
Should a demo bug be reported?
Yes, but include the build and label it as demo feedback. A demo issue may already be fixed or may not reproduce in the launch build.
Sources and verification
Official facts are separated from developer estimates and unverified community claims.