Graphics & resolution

Hearth and Hamlet has modest official PC requirements, but a dense late-game town can put more work on the screen than the opening camp. Start at your monitor's native resolution, then reduce rendering load only if frame pacing becomes uneven as the settlement grows.

Best starting point: native resolution, a stable display mode, and conservative background frame rendering. Change one option at a time so you can tell which adjustment helped.

Practical display recommendations
SituationResolutionFrame-rate targetReason
Meets recommended specNative monitor resolutionStable 60 FPS targetKeeps interface text sharp while avoiding unnecessary rendering for an idle session.
Near minimum spec1920×1080 or 1600×90030–60 FPS, favor stabilityLowering resolution reduces GPU load; a consistent frame rate feels better than fluctuating peaks.
Long background sessionKeep the lowest readable resolution60 FPS practical ceilingLimits avoidable heat and power use while the town runs unattended.
Text looks softReturn to native resolutionLower another load source insteadNon-native scaling can make management text harder to read.

Official PC requirements

Requirements below were verified against the official Steam store page on 2026-08-31. Hearth and Hamlet also ships on SteamOS and Linux.

Steam system requirements — Windows
ComponentMinimumRecommended
Operating systemWindows 10 (64-bit)Windows 11
ProcessorIntel Core i3 @ 3.2 GHzIntel Core i5-2400 @ 3.1 GHz
Memory8 GB RAM16 GB RAM (raised in patch 1.0.06)
GraphicsGeForce GTX 650 or Radeon HD 7770 (2 GB VRAM)GeForce GTX 750 Ti or Radeon R7 260X (2 GB VRAM)
DirectXVersion 11Version 11
Storage1 GB available space1 GB available space
Steam system requirements — SteamOS & Linux
ComponentMinimumRecommended
Operating systemUbuntu 20.04+ or SteamOSUbuntu 20.04+ or SteamOS
ProcessorIntel Core i3 @ 3.2 GHzIntel Core i5-2400 @ 3.1 GHz
Memory8 GB RAM16 GB RAM (raised in patch 1.0.06)
GraphicsGeForce GTX 650 or Radeon HD 7770 (2 GB VRAM)GeForce GTX 750 Ti or Radeon R7 260X (2 GB VRAM)
Storage1 GB available space1 GB available space

The 1 GB storage footprint and decade-old baseline GPUs confirm the game's lightweight 2D presentation: almost any desktop PC built in the last ten years clears the minimum, and laptops with integrated graphics are worth testing at 1600×900 if the frame rate dips in dense late-game towns. The one-spec change to know about: patch 1.0.06 (August 29, 2026) raised the recommended memory to 16 GB because leaner asset memory usage still needs headroom. The developer's own framing is that 8 GB “can still work flawlessly, but leaves little room for multitasking” — minimum requirements did not change.

The 60 FPS cap & how to lift it

The 60 FPS ceiling on PC is confirmed build behavior, not a rough guess. An inspection of the v1.0.04 files posted in the game's Steam discussion hub shows application/run/max_fps locked to 60 in the exported engine settings, so the cap holds no matter what the in-game V-Sync toggle says, and Windows players report the identical limit. For idle sessions this is convenient: the game already runs at exactly the pace recommended below, with zero configuration.

Lifting the cap on a high-refresh display

On 120–170 Hz monitors the stock cap leaves visible smoothness behind. The fix that has worked for Linux players (and matches what Windows players report) is a launch option rather than any settings menu: add --max-fps 0 to the game's Steam launch options, then start normally and let V-Sync govern pacing. In your Steam library, right-click Hearth and Hamlet, choose Properties, and type --max-fps 0 into the Launch Options box. The report that established this fix comes from a 170 Hz display running an RX 7800 XT on the Linux native build; results on other GPUs have not been independently verified. The developer said in August 2026 that he is considering adding a frame-rate option to the in-game menu in a future patch; nothing like that has shipped through patch 1.1.0 (October 1, 2026), so the launch option remains the only way to lift the cap.

Keep the stock 60 cap for idle play. Extra frames do not speed up townsfolk or taxes; an uncapped overnight session just burns GPU power rendering a picture nobody is watching.

Lift the cap only for active play on a high-refresh display, and consider removing the launch argument again before long AFK sessions.

For idle play: target a steady 60 FPS or lower, keep the game at a readable resolution, and avoid leaving other GPU-heavy applications running beside it.

If temperatures or fan noise stay high, test a 30 FPS driver cap. Progress does not benefit from rendering extra frames.

Troubleshooting stutter or high GPU use

  1. Restart and retest the same town. This separates a long-session issue from a consistently heavy scene.
  2. Return to stock launch options. If you added --max-fps 0 while chasing high-refresh smoothness, take it out again before troubleshooting idle load. Once the built-in 60 cap is restored, a driver-level 30 FPS limit is the next lever for unattended sessions near minimum-spec hardware.
  3. Reduce resolution one step. Test 1920×1080, then 1600×900 on hardware near the minimum graphics specification.
  4. Close overlays and background GPU workloads. Video, recording, and animated desktop tools can compete with the game.
  5. Update the graphics driver. Confirm the game is using the dedicated GPU on dual-GPU laptops.

Crash & VRAM fixes

Since release, some players have hit startup failures, crashes during loading, or graphical glitches — white squares and textures failing to load are the visible signature. Two official threads plus a string of patches define the current state of play. The pinned Bug Reports post establishes the first fix: switching the renderer to Vulkan resolves or greatly improves these problems in 95% of cases, by the developer's own count. The developer's August 25 Ongoing Development Update then diagnosed the remaining source as systems whose VRAM is exhausted, or which rely on shared video memory — mostly laptops and, less often, the Steam Deck — and the promised fix wave has now shipped: patch 1.0.05 (August 27) rebuilt “hundreds of assets” to be leaner as the “first wave of VRAM optimisation,” patch 1.0.06 (August 29) trimmed audio memory use on top, and patch 1.0.07 (September 5, 2026) is “focused entirely on reducing the game's memory footprint” — by the developer's count, “hundreds of changes” have cut VRAM usage by about 1.1 GB, which “should improve stability, especially on lower-spec hardware.” The developer's Known Issues list, updated August 29, rated the low-RAM/VRAM crashes “greatly improved” before that patch, and 1.0.07 continued the same effort rather than changing any gameplay. Patch 1.1.0 (October 1, 2026) went further still: its notes state that “memory usage has been greatly optimised, further reducing RAM requirements beyond the improvements in previous patches,” alongside significantly improved load times.

With that patch installed, treat the steps below as fallbacks rather than first-line fixes. They matter most on the profile the developer keeps describing: 8 GB machines, GPUs with 2 GB of VRAM, and systems that share main memory with the graphics chip.

What to try first

  1. Update to 1.1.0 or later before anything else. If you last played on an earlier build, this alone may clear the symptom — the VRAM-optimisation wave (1.0.05–1.1.0) specifically targets VRAM-related crashes and the white-square/missing-texture glitches, 1.0.07 alone cut VRAM use by roughly 1.1 GB, and 1.1.0 further reduced memory use.
  2. Relaunch in Vulkan mode. Use Steam's launch-option dialog (the selection window that appears when you press Play, or Set Launch Options in Properties) and pick the Vulkan entry. This is the developer-recommended first move and the one with the strongest public track record.
  3. Verify game files. In Steam, open Properties → Installed Files → Verify integrity. This catches corrupted installs after failed patches.
  4. Free up video memory before launching. Close hardware-accelerated browsers, video editors, and other games; shared-VRAM laptops are the hardest-hit category per the developer's own diagnosis.
  5. Report persisting cases upstream. The Known Issues pin treats this as an actively worked problem rather than user error, and the developer has been repairing affected saves directly via Discord. Use the pinned Bug Reports thread or Discord with your save file if crashes survive all of the above.

Save-file safety: none of the crash reports link this problem to town data corruption, so keep playing your save once the game starts reliably. Store backups locally as described on our save file location page.

Steam Deck notes

Hearth and Hamlet is a light native SteamOS title: the store lists SteamOS (Ubuntu 20.04+) among its supported systems, so the Deck runs the native Linux build rather than a compatibility layer, and the Deck's hardware sits far above the game's decade-old minimum specification. One top-rated player review sums the current experience up as “Runs perfectly” on Deck — a single report, but consistent with how modest the requirements are.

The one Deck-specific history worth knowing is the VRAM crash wave: the developer's August 25 Ongoing Development Update named the Steam Deck, alongside laptops, among the shared-memory systems most affected by the startup crashes and missing-texture glitches. That diagnosis is what patches 1.0.05 and 1.0.06 shipped fixes for, and patch 1.0.07 (September 5, 2026) is the same story continued: its roughly 1.1 GB VRAM cut lands hardest on shared-memory systems like the Deck, where every gigabyte of video memory is borrowed from system RAM; patch 1.1.0 (October 1, 2026) continued the effort with further memory optimisation. The Known Issues list rated the problem “greatly improved” before 1.0.07. Practically: make sure the game is updated to 1.1.0 or later, and if white squares or texture glitches still appear, launch with the Vulkan renderer selected in Steam's launch dialog — the same first fix recommended for Linux desktops above.

For settings on the Deck's 1280×800 screen, the same guidance applies with two adjustments: keep the built-in 60 FPS cap, since extra frames only cost battery during idle sessions, and use Auto UI Scaling if any menu overflows the smaller display — it is the official fix for cut-off interfaces at non-standard resolutions.

Accessibility & input checks

One input feature is developer-confirmed: the game has a built-in auto-click function. Answering a player on the Steam forums (August 22), the developer said, “I have a built-in auto-click function. You can turn on ‘Hover to Click’ in the options menu” — the supported way to cut down repetitive clicking while gathering. Beyond that, a complete, version-verified list of accessibility and input toggles is not available in the official public material we reviewed. Check the current in-game Options menu before relying on features such as hold-to-gather, interface scaling, or remapping.

For a more comfortable management setup, prioritize readable native resolution, Windows display scaling that keeps text legible, and an input posture that does not require prolonged repetitive clicking. These are setup recommendations, not claims about built-in toggles.

The expedition interface showing a map, destinations, goods, and transport options
The expedition screen is a management interface, not the settings menu; use it here only as an example of information density and text readability.

FAQ

What are the best settings for Hearth and Hamlet?

Begin at native resolution and aim for stable frame pacing. A 60 FPS ceiling is a sensible practical target for normal and idle play; lower resolution or use a 30 FPS driver cap if a large town causes high GPU load.

Does Hearth and Hamlet have a built-in FPS cap?

Yes. The frame rate is fixed at 60 through the engine's exported settings (verified in the v1.0.04 files), the V-Sync toggle cannot override it, and no patch through 1.1.0 has touched the cap. High-refresh-display owners can remove it temporarily with --max-fps 0 in Steam launch options, as covered above.

Hearth and Hamlet keeps crashing. How do I fix it?

First, update — patches 1.0.05 through 1.1.0 shipped a memory optimisation wave (1.0.07, September 5, 2026, alone cut VRAM use by about 1.1 GB, and 1.1.0 further reduced memory use) that the developer credits with greatly improving the low-memory crashes. If you are current and still crashing, try the Vulkan renderer next: pick it in Steam's launch dialog before the game starts; the developer reports this alone clears most crash and glitch cases, especially on Linux. Remaining failures concentrate on systems out of VRAM, laptops sharing main memory with the GPU, and some Steam Decks. Verify files, close VRAM-hungry apps, and use the pinned Bug Reports thread or the official Discord for persistent cases — the developer has been repairing affected saves there directly.

Hearth and Hamlet won't launch with “An Application Control policy has blocked this file” (error 0x11C7). How do I fix it?

This is Windows Smart App Control blocking the game's executable, not a broken install. The full message reads “Failed to start process for this game: ‘An Application Control policy has blocked this file.’” The developer confirmed the cause in the Steam thread — the game comes from a publisher Windows has no track record for yet. In his words, “It seems windows is still trying to figure out if i'm dodgy.”

  1. Verify the game files. In Steam, open Properties → Installed Files → Verify integrity. This fixed the original poster, it is the fix Steam Support itself suggests, and the developer endorsed it.
  2. Just try launching again. One player reports the game started normally after three or four attempts.
  3. Last resort: exempt or disable Smart App Control. Windows Security → App & browser control → Smart App Control settings — add an exclusion for the game, or turn the feature off. Many players refuse the off switch because it is effectively one-way: Windows offers no simple way to turn Smart App Control back on.

Running the game as administrator alone does not clear the block. Some players also stay blocked even after reinstalling and verifying — most recently reported in September 2026 — and the developer has not yet answered those reports, so the exclusion route above is the known remaining fix for now. Answering a different launch-block report on September 10, 2026, the developer also looked past Smart App Control to the wider class of blockers: “It could also be some security software you have conflicting with it.” Once the game starts, keep local save backups as described on our save file location page.

Which launch option should I pick: Normal, DirectX 12, or Vulkan?

The selection window that appears when you press Play offers three ways to start the game: Normal, DirectX 12, and Vulkan. Start with Normal. The developer's pinned guidance treats problems as the exception — Vulkan is the remedy he points to once crashes or graphical glitches actually appear, not the everyday default, so a Normal start is the expected path for most systems.

If the game does crash or show white squares and missing textures, relaunch with the Vulkan entry selected: the pinned Bug Reports guidance credits Vulkan with resolving or greatly improving stability issues “in 95% of cases,” and the crash section above has the full fix sequence. DirectX 12 is not singled out anywhere in the developer's public guidance, so treat it as an alternative renderer rather than a fix. And keep Vulkan's track record in scope: it is a remedy for crashes and graphical glitches specifically, not a general fix for unrelated problems.

Does Hearth and Hamlet run well on Steam Deck?

It runs natively on SteamOS, and the Deck comfortably exceeds the game's minimum requirements; one top-rated player review calls it “Runs perfectly” on Deck. The one Deck-relevant history: the developer named the Deck among the systems hit by the VRAM crash wave, which patches 1.0.05 through 1.1.0 specifically addressed — 1.0.07 (September 5, 2026) cut VRAM use by about 1.1 GB and 1.1.0 further reduced memory use, changes that matter most on shared-memory systems like the Deck — so update first, and pick the Vulkan renderer in the launch dialog if texture glitches appear. For the 1280×800 screen, keep the 60 FPS cap for battery life and enable Auto UI Scaling if menus overflow.

Why are my menus cut off or buttons unclickable?

This is the documented UI-scaling overflow: the UI Scaling setting is too high for your resolution, so elements render outside the screen and dialogs cannot be closed. The official fix from the Known Issues list is to either lower UI Scaling or enable Auto UI Scaling, which fits the interface to your resolution automatically.

Why is the Incoming Enemy Tracker in the wrong place?

The Known Issues list confirms the tracker can end up misplaced in the bottom-right after a resolution change. Saving and exiting, then reloading, puts it back where it belongs.

Can my PC run Hearth and Hamlet?

The Steam minimum lists Windows 10, 8 GB RAM, a GeForce GTX 650 or Radeon HD 7770 (2 GB VRAM), DirectX 11, and 1 GB of available storage. Since patch 1.0.06, the recommended spec is Windows 11, 16 GB RAM, and a GTX 750 Ti or Radeon R7 260X — the developer notes 8 GB still works, just with little headroom for multitasking.

Sources