Horizon is a good fit for older hardware, with honest limits. On the project’s own 2016 test laptop (Core i7-7500U with Intel HD Graphics 620), the official benchmark measured 209 FPS on average against 126 for Java Edition, about half the hitches and 0.8 GB of memory against 2.0 GB, at render distance 12. Real play on the same graphics chip is slower than the benchmark flight, around 61 FPS for a typical frame. Start with the Performance preset, render distance 8 to 12, LOD off and Battery mode, then adjust.
The official low-end benchmark, with its conditions
The Benchmarks page uses three of the project’s machines; the lowest is the “ThinkPad laptop”:
- Hardware: Intel Core i7-7500U (2 cores, 4 threads), Intel HD Graphics 620, 32 GB RAM, Linux with Mesa 26.1.8. Horizon ran on Vulkan, vanilla on OpenGL.
- Method: a fresh creative world (seed 1234), flights over a village, a forest, an ocean and a mountain, 1280×720 window, VSync off, no frame cap, simulation and render distance 12, other settings at vanilla defaults. Java Edition ran as players get it, with the official launcher’s Java options. Medians of the runs.
- When: measured on 22 October 2026 with Horizon v2026.10.22.04. The page notes the laptop no longer runs benchmarks, so it wasn’t re-measured on 4 November.
- Display: the laptop had no screen attached, so both games drew to a compositor on the Intel GPU.
| ThinkPad, render distance 12 | Horizon | Java Edition |
|---|---|---|
| Average FPS | 209 | 126 |
| 1% lows | 39 FPS | 29 FPS |
| Hitches per minute | 242 | 470 |
| Long stutters (under 30 FPS) per minute | 25 | 36 |
| Memory in use (peak) | 0.8 GB (1.0) | 2.0 GB (2.1) |
| Launch to world | 50.8 s | 68.1 s |
| Loading new terrain | 59.7 s | 46.9 s |
The last row is the one place Java Edition did better in these runs. Render distance 32 isn’t shown at all: in five minutes neither game finished loading the spawn on this machine.
What real players on this hardware see
The same page adds a reality check from opt-in telemetry: over the last 30 days of real play, the 480 installs with an HD Graphics 620 had a middle frame of about 16 ms (61 FPS, many with VSync on) and their slowest 1% of frames at about 34 ms (29 FPS), against the 39 FPS 1% low in the benchmark. Across all Intel integrated graphics, about a quarter of all play hours, a third of the hours were under 60 FPS.
Real worlds have more mobs, redstone and builds than a benchmark flight, and many players leave VSync on. Expect smooth-ish 60 FPS play on such a laptop with sensible settings, not the 209 from the table.
Settings that help most on weak machines
- Preset: Performance. Options → Video Settings → Horizon Graphics. Every row shows its frame-time cost, so you can raise what you miss.
- Render distance 8 to 12. It’s the biggest lever, and on 4-thread CPUs chunk generation competes with everything else.
- LOD distance off, or small. Horizon already caps far terrain on integrated graphics and holds it back on computers with four threads. If you want far views, try 64 or 128 chunks with a modest render distance. Newer builds add Far Detail: Reduced, which draws about a quarter of the far quads.
- Battery mode (Advanced Graphics, Performance group): caps 60 FPS in a world and 30 in menus, and uses half the automatic worker threads. Less heat, less throttling, longer battery.
- Windows: if Vulkan is unstable on an older Intel driver, set Graphics API to DirectX 12.
- Shaders: usually skip them. If you must, the authors of Pastel Mystic say they tested it on Intel Iris Xe, and Wisdom Shaders V3 Lite is tagged low cost. Turn shadows off first. More in best Horizon shaders.
To check what helps, turn on the performance overlay or install the FPS Counter mod, and run the built-in benchmark before and after (plugged in). The full tuning guide is how to get more FPS in Horizon.
Memory: why 8 GB machines benefit
The ThinkPad run measured 0.8 GB for Horizon against 2.0 GB for Java Edition while playing; the Benchmarks page points out that Java Edition needing 2.6 times more matters on a computer with 8 GB. There’s no Java heap to tune either: memory isn’t a setting in Horizon, the game uses what it needs.
One caveat for native mods: the launcher’s first native build downloads Rust and compiles the whole game, which the docs put at 20 to 30 minutes and a few GB of disk. On an older laptop, plan for that (and keep it plugged in).
What won’t run
- 32-bit Windows and ARM Linux (no builds).
- Linux without Vulkan drivers, and distributions older than Ubuntu 22.04.
- macOS older than 12. Intel Macs on macOS 12 or later are supported.
The Steam Deck works: Horizon has its own controller support, and Steam’s default layout works with no setup. The project’s Hub lists low-end machines (Steam Deck, old Macs, 8 GB computers) as a planned focus, with measured targets per class of machine still to come. Why Horizon tends to use less memory in the first place is explained in Rust vs Java. Ready to try it? Install Horizon.