Timberborn left Early Access on March 12, 2026, landing on Steam Deck as “Playable” — accurate, but underspecified. Two things prevent a Verified rating: controller icons display incorrectly, and the virtual keyboard doesn’t appear automatically when text input is needed. Neither breaks the game.
What does break the experience is launching without the right Proton version and Steam Input configuration. Out of the box, building placement is imprecise, camera rotation requires a missing right mouse button, and large colonies stutter even on Low graphics. This guide fixes all three. The control remaps come first — without them, the settings table doesn’t matter.
Verified on Timberborn 1.0, Steam Deck LCD and OLED, April 2026. Settings may shift with future patches.
Get Running in 5 Steps
Do these before adjusting any graphics setting:
1. Force Proton Experimental. Right-click Timberborn in your Steam library → Properties → Compatibility → check “Force the use of a specific Steam Play compatibility tool” → select Proton Experimental. This version includes the Proton 10.0-3 fix that resolved Timberborn’s drag-select bug on Steam Deck — without it, area selection for marking trees and zones doesn’t work.
2. Check UI Scale. In-game Settings → Interface. The game auto-sets an increased UI scale on Steam Deck after a post-1.0 patch, but verify it’s at 130–140%. Below that threshold, the colony resource panels are unreadable at arm’s length.
3. Apply a Steam Input layout. Steam button (hold) → Controller Settings → Browse Community Layouts. Search “DexDearborn” for a tested community configuration, or apply the three manual remaps below.
4. Set Graphics to Custom and apply the values in the table in the next section before starting your first colony.
5. Plan your first district for no more than 100 beavers. This constraint is easier to build around from day one than to retrofit later when performance degrades mid-session.
The 3 Control Remaps That Make Timberborn Work on Deck
Timberborn has no native controller support — it runs keyboard-and-mouse internally, which means Steam Input is doing all the work on Deck. The default layout for an unverified game tends to configure the right trackpad as a joystick analog, which accelerates too fast for precise building placement. These three changes fix the core input problems documented by the Steam Deck community.
Remap 1: Right Trackpad → Trackpad as Mouse
This is the most critical change. “Trackpad as Mouse” mode makes the right trackpad behave like a laptop touchpad — the cursor moves proportionally to finger movement rather than accelerating like a joystick. Building placement on Timberborn’s dense colony grid requires this level of precision.
How to set it:
- Steam button (hold) → Controller Settings → Edit Layout → Right Trackpad
- Set Trackpad Behavior: Mouse (not Joystick Move)
- Sensitivity: Medium — at High, the cursor overshoots small building footprints before you can tap to confirm placement
Clicking the trackpad surface registers as left mouse click, handling building placement, UI buttons, and selection throughout.
Remap 2: R2 → Right Mouse Button (Hold)
Timberborn rotates the camera by holding and dragging the right mouse button. Without mapping this to a trigger, you’re stuck at a fixed camera angle for the entire session. Community configurations consistently resolve this by mapping a trigger to right mouse hold.
- Right Trigger (R2) → Mouse Button → Right Mouse Button
- Activation style: Hold (active while trigger is pressed, releases on release)
Hold R2 and drag the right trackpad to rotate the camera view — the same motion as on PC. This is the control that makes scanning large colony districts practical on a handheld screen.
Remap 3: Right Stick Vertical → Scroll Wheel
Camera zoom requires a scroll wheel. Without remapping, zoom defaults to Page Up/Page Down keyboard shortcuts, which interrupt building workflow. Map the right stick’s vertical axis to scroll wheel output in Steam Input — the option appears under the right stick Behavior settings (exact label varies with Steam client version). Set up: push up to zoom in, push down to zoom out.
With these three remaps in place, the left stick handles WASD camera panning, A handles building placement clicks, B cancels or deselects, and the bumpers cycle through building categories — the full game loop covered.
Best Graphics Settings for Steam Deck
Timberborn is CPU-bound rather than GPU-bound. The Steam Deck’s RDNA 2 GPU handles the game’s art style without strain — the bottleneck is the water physics simulation running on a single Zen 2 CPU core. According to a 2026 performance analysis, reducing shadow quality or texture resolution has minimal FPS impact compared to the water simulation slider, which is the setting that actually determines late-game performance.
| Setting | Value | Reason |
|---|---|---|
| Graphics Preset | Custom | Built-in presets enable effects you don’t need for top-down play |
| Resolution Scaling | 100% | Dynamic scaling causes visible stutter during colony growth events |
| VSync | Off | Adds input lag; use TDP limit for frame pacing instead |
| Shadow Quality | Medium | High shadows have negligible visual gain at top-down camera angle |
| Anti-Aliasing | FXAA | TAA is blurrier and heavier; FXAA is the better trade-off at this resolution |
| Water Simulation | Medium (under 100 beavers) / Low (100+) | Primary FPS factor post-1.0; Low vs High gives 15–20% FPS difference |
| Ambient Occlusion | Off | CPU cost with minimal visual improvement at colony-zoom level |
| Foliage Density | Low | 10–15% FPS gain; foliage invisible at management zoom distance |
| Level of Detail | 60% | Prevents high-polygon models from rendering at distance |
If your Steam Deck runs warm during extended sessions, try setting TDP Limit to 12W via the Quick Access menu (three-dot button → Performance). In GPU-light, CPU-heavy workloads like large Timberborn colonies, this can help stabilize CPU clock speeds by reducing thermal throttle events. Test with and without — results vary by colony size and ambient conditions.
Once your colony exceeds 200 total beavers, lock FPS to 40 via Quick Access. A stable 40fps is more comfortable than fluctuating between 30 and 55fps as the water simulation spikes during events.
Colony Performance: What Matters More Than Graphics
Two design decisions affect Steam Deck performance more than any graphics slider — and both are in your control from the first session.
Keep Each District Under 100 Beavers
Pathfinding in Timberborn runs on a single thread. When a major colony event fires — a flood, a building demolition, a bad tide onset — every beaver in a district simultaneously recalculates their route. At 150+ beavers in one district, this causes visible frame stutters lasting several seconds. At 70–100 beavers, the recalculation completes fast enough to be imperceptible.
The district planning guide covers efficient layouts for keeping colony growth manageable within this limit for both Folktails and Iron Teeth — the architectural differences between factions affect how quickly you approach the 100-beaver ceiling and what buffer space you have before performance degrades.
Terrace Every Significant Waterfall
A 10-tile-high waterfall puts more load on Timberborn’s water simulation than a full industrial district. The physics engine tracks each unit of water through every tile of its fall, and tall single drops give water more air-time to simulate. Splitting a 10-tile drop into five 2-tile terraces substantially reduces CPU cost — water settles on each ledge before falling again, breaking the calculation into smaller, faster chunks rather than one long continuous fall.
This matters most during bad tide events, which push extra load onto the simulation at exactly the moment your waterfalls are most active. Design water systems flat from the start rather than retrofitting after performance problems appear mid-colony.
Gate Active Water Flow During Drought
Once you have reservoir storage, use sluice gates to restrict active waterways during drought seasons. Fewer live water tiles means fewer simulation calculations per tick, which smooths out the planning phases between tides. This is the late-game equivalent of the Water Simulation Quality slider — you’re reducing live simulation load at the source rather than telling the engine to approximate it.
Settings by Player Type
| Player type | Do this first | Safe to defer |
|---|---|---|
| New player | Complete Quick Start checklist; one district, cap at 80 beavers initially | Foliage density and LOD tweaks — apply once colony scales up |
| Casual | Apply settings table; Medium water sim throughout; play naturally | Waterfall terracing — address it if performance dips mid-game |
| Optimiser | Full settings table from session 1; terraced waterfalls only; 70-beaver district cap | Nothing — every setting matters once colonies scale |
| Completionist | Plan a performance budget around Wonder construction — CPU and GPU-intensive builds | High foliage density or ambient occlusion at any game stage |
Frequently Asked Questions
Is Timberborn Steam Deck Verified?
No — it holds “Playable” status as of April 2026, per Steam Deck HQ. The two documented issues are incorrect controller icons (the game uses generic icons rather than Steam Deck button labels) and the virtual keyboard not triggering automatically when a text field is selected. Neither prevents play: bring up the keyboard manually via Steam button → Keyboard when text input is needed. The developer added UI auto-scaling on Steam Deck in a post-1.0 patch, addressing the most disruptive usability gap.
Will Timberborn hit 60fps on Steam Deck?
Early-game colonies under 50 beavers hold 60fps comfortably with the settings in this guide. Mid-game with 70–100 beavers per district averages 45–60fps in community testing. Late-game with 200+ beavers across multiple districts, expect 30–45fps during active bad tide seasons — this ceiling is set by single-core CPU performance, not graphics settings. No graphics adjustment fixes it; the levers are district size management and waterfall design. Locking to 40fps via Quick Access gives a more consistent experience than chasing 60fps in late game.
Can I play without using the trackpad?
Not effectively. Building placement requires cursor precision that right-joystick mouse emulation doesn’t reliably provide — Timberborn’s building toolbar and colony grid are dense enough that joystick acceleration causes consistent misclicks. The right trackpad in Mouse mode is the core input that makes the game functional on Deck. If you want to reduce trackpad use, keyboard shortcuts (Q/E for camera rotation, WASD for panning, number keys for building categories) cover navigation, but UI interaction and building selection still require the trackpad.
Further Reading
For a full foundation in Timberborn’s water management, faction progression, and colony survival systems, the Timberborn Beginner’s Guide covers the complete system from first colony through Wonders. For applying Steam Deck performance principles to other CPU-bound games, the PC Game Settings Optimization guide explains TDP limits, resolution scaling, and frame pacing in depth.
Sources
- Steam Deck HQ — “Timberborn Gets Small Patch To Fix Dragging Issue On Steam Deck”
- PixelNitro — “Timberborn Low FPS Fix 2026: Guide to Optimizing Water, Waterfalls, and High-Pop Colonies”
- Steam Community — Timberborn Controller Compatibility Discussion (Feedback and Suggestions)
- Steam Community — Steam Deck Controls Change Help (General Discussions)
- BoilingSteam — “New Steam Games Playable on the Steam Deck, 2026-03-14 Edition”
- GamingOnLinux — “Proton 10.0-3 Released Bringing Lots of Improvements for Gaming on Linux and SteamOS”
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.