The public Wyldheart demo is available from the official Steam page for the coming-soon base game. It is a separate Demo client, AppID 4475270, currently labeled 0.7.2. Download it from the listing for base AppID 3642910, expect a standalone one-shot adventure, and assume that your demo save will not transfer to Early Access or the full release.
Download the right client
- Open Wyldheart on Steam and confirm the developer is Wayfinder Studios.
- Use the Download Wyldheart Demo control. The base game itself remains “Coming soon.”
- After installation, check the version shown by the demo before joining friends or reporting a fault. This guide is scoped to 0.7.2 on October 10, 2026.
- Keep Steam online for the first launch so the client can update and contact Wyldheart’s services.
The public demo does not require a beta key. Do not install Wyldheart Beta AppID 3643050 as a substitute; that Kickstarter client has its own history and was not updated into the public demo. Also avoid search results for WILD HEARTS, AppID 1938010, which is unrelated.
What you can play
Official launch notes also name swords, axes, clubs, spears, bows, and the Paths of Blight, Pyre, Rime, and Storm. They confirm flexible skill trees, but they do not make every exact node, damage value, respec rule, or item source stable enough to treat as launch data.
Prepare before entering The Slurper’s Den
Open the settings screen and learn the actions shown for your device. Prioritize interact, defense, weapon access, quick items, camera, and any search or inspection action. Controller support is still being improved in the demo, and the developer recommends PC with mouse and keyboard for the current experience. Use what is readable on your hardware, but do not copy an old Alpha binding without checking the live menu.
Choose a background for an understandable starting kit rather than an alleged tier ranking. Carry a light source in dark rooms, inspect loot before replacing reliable gear, and watch weapon condition. The opening is easier to read when you change one tool at a time. If you equip every unfamiliar weapon and spell immediately, it becomes hard to tell whether a failure came from range, stamina, durability, or the input layout.
Leave the opening dungeon without assuming a fixed map
The Slurper’s Den uses authored rooms within a layout system that can vary. Navigate by room features and required interactions, not by counting doors from a video. If the exit route seems inactive, clear immediate danger, inspect nearby switches or walls, and finish the injured character’s dialogue all the way through before trying the rope interaction again. Community reports from the current demo repeatedly identify incomplete dialogue as an easy-to-miss exit condition.
That last detail is community-reported rather than a permanent design promise. If 0.7.2 or a later patch changes the sequence, follow the active prompt in your build. Do not force a fixed walkthrough path through a room arrangement that differs from the example you watched.
Save rules can change your decision to play offline
The demo normally relies on online services for saved progress. Hotfix 0.7.2 CL39302 repaired the Online Save checkbox and provided an offline option for sessions blocked by connectivity. The official warning says offline saves are not supported in this demo. If you disable saving, everything from that session is temporary and will be lost when you exit.
Use offline mode only when a disposable practice run is acceptable. If persistence matters, check the official status page, leave saving enabled, and wait for service recovery rather than converting a planned long run into a no-save session. No demo save will transfer to the full game, even when online saving works.
Set up co-op after every player updates
Have the host create or open the intended campaign, then use the Lobby or Roster to read the join code. CL39302 specifically addressed code visibility, so a missing code is a reason to confirm version parity before trying elaborate fixes. Share the code directly with friends; it is not a redeemable reward code.
Agree on a short first goal such as leaving the opening dungeon or reaching Rivermere. Let new players read character and story prompts, share equipment by party need, and regroup before a hex transition. The full game’s advertised cloud-shared campaign vision is broader than the launch-week demo behavior, so verify what the current client actually saves instead of assuming every absent member receives progress.
If the demo will not start
Check official server status first, especially when loading hangs affect many players. Restart Steam and the demo, allow the client to update, and verify the installed files. Remove only unsupported overlays or injectors you knowingly added, one at a time. Do not delete unknown save or configuration folders based on an old guide.
Compare your PC with the current system requirements. The listing requires 64-bit Windows 10 or 11, DirectX 12, 16 GB RAM, broadband internet, and an SSD. A Steam Deck can run the demo according to the official FAQ, but this is not a Deck Verified badge or proof of native Linux support.
What to do after the first run
Use the demo to answer personal questions that published numbers cannot: whether you enjoy the room-to-room rhythm, whether hex travel feels clear, which weapon reach you read well, and whether your group likes the drop-in structure. Then revisit Combat, World, Systems, or Multiplayer with observations tied to Demo 0.7.2.
Keep the experiment scoped. The demo is public evidence of the current slice, not a complete inventory of the coming base game. Recheck all saved-progress, platform, balance, and content claims when Early Access receives an official date and build.