Hearth syncs your Valheim world files between players through Google Drive. No more waiting on the host. Anyone in your crew can load the world and pick up right where you left off.
The host owns the .db and .fwl files. When they log off, the mead hall goes dark — no matter how many of your crew are ready to raid.
Your crew wants to push into a new biome, but the person who created the world is busy. The longship sits idle. Every boss fight, every portal, every hour of progress is locked behind one person's schedule.
Valheim and Steam Cloud have a notoriously rocky history. Saves get out of sync, world files disappear, and Steam Cloud has been overwriting local saves since day one. Hearth works entirely outside Steam Cloud — your saves stay on your own Google Drive where you control them.
Valheim worlds require both the .db and .fwl files. Miss one, rename one, or load the wrong version — and your world breaks. One mistake can wipe out dozens of hours of shared progress.
Hearth runs in the background while you raid. When the session ends, it pushes the world automatically. When anyone else opens Hearth, it pulls the latest save before they even reach the main menu.
Hearth handles both save files Valheim requires — the .db (world data) and the .fwl (world metadata) — as a pair. It finds them automatically in %USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_local. You never need to touch the save folder directly.
Right-click Valheim in Steam → Properties → General → uncheck "Keep game saves in the Steam Cloud." Everyone in your group must do this. Steam Cloud and Hearth will conflict if left on.
Valheim doesn't write save files until you've actually entered a world. Create or load your world, get fully in, then exit back to the menu and quit. Hearth will find it after that.
Open Hearth, find your Valheim world in the list, and check the share box. Hearth pushes both the .db and .fwl files to your shared Google Drive folder. Your crew sees the world appear on their end automatically.
Hearth locks the world when Valheim launches, backs it up every 25 minutes mid-session, and pushes it to Drive when you close the game. The next person to open Hearth gets the latest save automatically before they launch.
No monthly server fees. No Discord file juggling. No version confusion. Just your world, always available to whoever is online.
Hearth syncs the .db and .fwl pair together every time. No more broken worlds from missing files or mismatched versions.
When Valheim launches, Hearth locks the shared world. Nobody can accidentally push an older save while someone else is playing.
Local backup every 25 minutes while you play. If Valheim crashes mid-session, you're never losing more than 25 minutes of your saga.
Saves go to your own Google Drive — not our servers. No account with us, no subscription. Google backs it up. You own it.
Every line of code is public. Read exactly what Hearth does with your save files before you ever run it.
No trial. No premium tier. Free because the person who built it just wanted to raid Valheim with friends without scheduling conflicts.
.db and .fwl files to your shared Google Drive folder automatically. Your friends open Hearth on their end and the world appears within seconds. No manual file transfers, no Discord uploads.%USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_local. Each world has two files: a .db and a .fwl — both are required. If you've been using Steam Cloud, your saves may be at ...\Steam\userdata\[SteamID]\892970\remote\worlds instead. Hearth finds the right location automatically..db and .fwl files for your world from the worlds_local folder. Do not rename them — Valheim will not recognize renamed world files. Hearth handles the pairing and transfer cleanly without any renaming risk.Free download. Open source. Takes about five minutes to set up. No account required — just a Google Drive folder your crew shares.
↓ Download Hearth Free