Frostpunk was built on 11 Bit Studios' own Liquid Engine, then the studio moved to Unreal Engine 5 for Frostpunk 2 and the upcoming Frostpunk 1886 remake. That switch is the whole story: a small proprietary engine that made cold feel personal, replaced by rented blockbuster tech that makes cities bigger and moddable.
Short answer: If you ask what engine Frostpunk uses, the answer is split by year. The original 2018 city-builder runs on proprietary Liquid Engine. Frostpunk's infobox lists Liquid Engine as original engine, with Unreal Engine 5 for the 1886 remake. The sequel runs on Unreal Engine 5. Frostpunk 2's infobox lists Unreal Engine 5 as its engine. The studio confirmed the direction again with later UE5 projects: The Alters, released June 13, 2025, also lists Unreal Engine 5.
Why this engine question keeps getting searched
Players keep typing "what engine is Frostpunk made in" and "Frostpunk 2 Unreal Engine 5" into Google, while Bing adds "how to mod Frostpunk 2," "Frostpunk 2 modding tool," and "Frostpunk 2 cheat engine." That pattern is the niche: it is not just curiosity about graphics, it is about whether the game can be modded, expanded, and run on consoles.
The commercial reason is hot enough to matter. Frostpunk sold over 250,000 copies in its first three days, according to 11 Bit Studios history, and sold over 5 million copies within six years. The studio itself is not a giant factory: founded September 11, 2010 by former CD Projekt and Metropolis Software staff, with about 299 people in 2025. A 60-plus-person team shipping a 5-million-copy survival city-builder on its own tech is exactly why indie developers study it.
This article covers Frostpunk (Windows April 24, 2018; PS4 and Xbox One October 11, 2019; macOS February 24, 2021) and Frostpunk 2 (Windows and macOS September 20, 2024; PS5 and Xbox Series X/S September 18, 2025). Dates and platforms are from Frostpunk and Frostpunk 2. The planned Unreal Engine 5 rebuild Frostpunk 1886 is set for 2027 and may shift; treat that date as announced, not shipped.
What Liquid Engine was good at: heat is the map
Frostpunk is a single-player city-building survival game set in alternate-history 1886 after Krakatoa eruptions trigger volcanic winter. You lead New London around one coal-fired Generator that pushes heat in a circle. All buildings sit on a circular grid around the Generator, whose heat radius can be extended and upgraded.
That circle is my first piece of analysis — the Generator is the map, not the terrain.
Most city-builders sell you land: rivers, harbors, highways. Frostpunk sells you temperature. Where you build matters less than how warm that ring is. Insulation, overdrive, range upgrades, and coal flow are movement, housing, and combat rolled into one number. Liquid Engine did not need to be good at open worlds. It needed to be good at one query, every second: who is freezing right now?
The surrounding systems all feed that query:
- Workers and engineers work daylight hours, with emergency shifts and child labour as trade-offs
- Automatons built with Steam Cores can automate facilities
- A Workshop unlocks research, a Beacon unlocks scouting for survivors and outposts
- Hope and discontent decide revolt; Order and Faith can harden into fanatic totalitarian rule
My take, labeled as opinion: the law book is live patch notes, not morality. Order versus Faith looks like ethics, but it plays like server rules. You pick a ruleset that changes productivity, policing, and healthcare costs, then live with the exploit. That is why Frostpunk is still argued about years later. Players are not debating endings; they are debating builds.
Liquid's advantage was focus. A house engine built from Anomaly through This War of Mine, which sold over 9 million units, to Frostpunk could keep that cold-plus-morale loop tight without carrying features 11 Bit never needed.
What Liquid cost: no mods, no scale, no hiring pool
The same focus became debt.
Frostpunk 1 has deep scenarios and DLC, but it never became a mod platform. Compare that to Frostpunk 2, which shipped with an official mod tool, FrostKit, at launch. That contrast is factual and telling. A proprietary engine can ship a brilliant closed game; it struggles to ship tools strangers can use.
Three costs piled up, in my reading:
- Hiring tax. Every Liquid engineer had to be trained in-house. Every UE5 engineer already exists.
- Porting tax. Frostpunk reached Windows, PS4, Xbox One, macOS, mobile as Beyond the Ice, and Switch over eight years. Each port re-solved problems Epic already solves.
- Scale ceiling. Frostpunk 1 simulates individual buildings around one Generator. Frostpunk 2 simulates districts, factions, and a 100-person Council. You can brute-force the first on a small engine. The second wants an editor, asset pipeline, and console toolchain you do not have to maintain.
That is why I disagree with the common "UE5 for better graphics" summary. Frostpunk 2 is not obviously prettier in the way a shooter is. It is bigger in management scope. 11 Bit did not rent beauty; in my view, it rented throughput and modders.
Why Unreal Engine 5 for Frostpunk 2: districts are gameplay Nanite
Frostpunk 2 is set 30 years after the Great Storm, in 1916 New London, with oil replacing coal and overpopulation replacing the first game's lonely outpost. The mechanical headline is simple: players build districts instead of individual buildings, with specific buildings slotted inside each district.
Here is my deliberately un-rigorous but useful analogy: districts are gameplay Nanite.
Unreal Engine 5's headline features are Nanite virtualized geometry that auto-manages level of detail and Lumen dynamic global illumination. Nanite's idea is to stop drawing every triangle by hand and draw clusters that scale with distance and performance. Frostpunk 2 does the same to management: stop simulating every house, simulate food, shelter, and energy districts that scale with city size.
Other sequel systems follow that compression logic:
- The Idea Tree lets factions propose competing research solutions, so adopting one idea angers another
- The Council Hall holds 100 community votes; most laws need 51 votes, power grabs need two-thirds, with negotiation and promises that punish broken deals
- Time runs in weeks, not hours and days, and radicals grow inside factions if ignored
- Utopia Builder sandbox lets you pick communities, build colonies, or stockpile, with extra objectives that can end the run
My contrarian take: Frostpunk 2 feels less intimate on purpose, and that is the engine talking. When critics say the sequel lost the first game's street-level frostbite, they are right about the feeling and wrong about the cause. It is not laziness. It is a deliberate LOD swap to afford a city ten times larger and a parliament that can overthrow you. You cannot keep per-citizen shivering simulation and add 100 politicians without something giving.
Unreal Engine 5 itself was revealed May 13, 2020, entered early access May 26, 2021, and launched April 5, 2022, written in C++ as source-available commercial software with royalties. For 11 Bit, that maturity matters more than any single rendering feature. Frostpunk 2, The Alters, and Frostpunk 1886 all listing UE5 is not a fashion choice; it is a studio standardizing on one hiring pool and one console pipeline.
Cold as anti-cheat: my most different idea
Here is the idea I have not seen elsewhere, offered as analysis, not fact.
Frostpunk does not need multiplayer anti-cheat because frost is the moderator. Hoarding coal, turtling on research, idling through a storm — all the classic single-player exploits — are punished automatically by temperature dropping and hope collapsing. The weather deletes degenerate strategies the way a good server admin would.
That explains why Liquid lasted as long as it did. If your core balancer is a circle of heat that shrinks when you misbehave, you do not need complex AI or netcode. You need one honest simulation that never lies about who is cold. Liquid was honest about that. UE5 was needed only when honesty had to scale to districts, oil, and votes.
A second small heresy: ugliness is infrastructure. Frostpunk's brown-grey industrial look is often praised as art, but I think it is also budget discipline. Smoke, snow, and dark interiors hide asset reuse the way Frostpunk 1's storm hides the edge of the map. UE5 does not remove that trick; it just lets you hide a bigger city.
What indie developers can steal this week
Do not copy the Generator. Copy the question it asks every tick.
- Make one survival number spatial. Frostpunk's heat radius turns a spreadsheet into a neighborhood. If your resource is global, players optimize math. If it radiates from a point, players build stories.
- Ship laws as patches. Order and Faith work because they have costs, cooldowns in the form of discontent, and irreversible branches. Write your upgrade tree like release notes: what breaks if this ships?
- Compress before you expand. Frostpunk 2 moved from buildings to districts before adding oil and politics. If your sequel lags, do not add content. Add a coarser LOD for old content, then spend the savings.
- Rent tools to buy creators. FrostKit at launch matters more than any lighting upgrade. If your proprietary engine cannot ship documentation and editors strangers tolerate, your content ceiling is your headcount.
Uncertainty to preserve: Liquid Engine internals are not publicly documented in the sources used here beyond the original-engine credit. Do not treat Frostpunk 1's performance or tooling limits as benchmarked facts from this article; the modding and scale gap is inferred from shipped features (no FrostKit versus FrostKit, buildings versus districts), not from engine source code.
Try the loop in your browser before you commit
If Frostpunk sounds interesting but heavy, you can practice its core loops in minutes on lightweight browser games. EasyHub hosts hundreds of HTML5 and Unity WebGL games that load instantly with no downloads.
For cold pressure without a 60-hour campaign, try Antarctica 88. It is a first-person survival horror in a dead Antarctic station where you manage health, scarce ammo, and power puzzles while something moves under the ice. Frostpunk makes you fear the thermometer; Antarctica 88 makes you fear the corridor. Both teach the same habit: search every room, read every log, and never waste a resource you cannot replace.
For the coal-steel-food treadmill, try Adventure Miner. You mine ore veins, haul them to the dock to sell, then buy pickaxe power, carrying capacity, and speed to reach richer islands. That gather-sell-upgrade-push loop is Frostpunk's early game stripped to its skeleton, and the lesson transfers directly: upgrade capacity first, then power, then speed.
For district thinking, try Beaver Builder. You gather resources as a beaver to build dams, rafts, and houses while protecting the village from flooding. It is cute where Frostpunk is bleak, but the planning question rhymes: where does the barrier go, what gets upgraded first, and how many helpers can you afford?
None of these replace Frostpunk. They are five-minute trainers for three separate muscles: dreading cold, feeding an economy, and placing infrastructure before the disaster arrives.
FAQ
What engine was Frostpunk made in?
Original Frostpunk uses Liquid Engine; the 1886 remake uses Unreal Engine 5, and Frostpunk 2 uses Unreal Engine 5. Engine credits are in Frostpunk and Frostpunk 2.
Why did 11 Bit switch from Liquid to Unreal Engine 5?
The shipped evidence points to scale and modding: districts instead of buildings, a 100-vote Council, and FrostKit mod support at launch for the sequel. UE5 standardizes hiring and console ports across Frostpunk 2, The Alters, and 1886. Treat the creative motive as analysis; the shipped feature gap is factual.
How many copies did Frostpunk sell?
Over 5 million within six years, with over 250,000 in the first three days. Sequel sales are not claimed here to avoid inventing a number.
Should indies still build a custom engine?
Only if your core query is as narrow as heat-who-is-freezing and you can afford to never ship mods. Otherwise, the Frostpunk arc suggests renting UE5 to buy time, ports, and creators is the pragmatic default.
Verified November 17, 2026 from primary pages listed below. SearchWebByBing was unusable for this run due to date-field validation rejecting null bounds, so demand was validated via Google/Bing suggestion tips and direct HTTP retrieval of the pages cited.
Top comments (0)