If you've had a UE 5.7 prep checklist pinned in your server's Discord since spring, bin it: that upgrade isn't happening. ARK: Survival Ascended is going to Unreal Engine 5.8 instead, on 30 September, alongside the Therizinosaurus TLC, Cerberax and Gargantar, and I'd rather you heard the correction from someone willing to admit we published the wrong version number back in April ourselves.
So this is the do-over. What's actually landing, what an ASA engine upgrade has genuinely done to dedicated servers and mods before, and the short list of things worth doing between now and the end of the month.
The version you were told to prepare for quietly stopped existing
Worth walking the timeline, because the shape of it tells you something about how to plan.
Wildcard's 2025 year-in-review put UE 5.7 in "early 2026", which is about the vaguest a date can be while still being a date. Community Crunch 490 on 10 January tightened that to April and put numbers on it: roughly 30-40% more performance across CPU and GPU, stacked on top of an ASA that already ran 40-50% better than it did at its October 2023 launch. Jeremy Stieglitz spent the spring calling it about as close to a magic bullet as performance work gets. Our April write-up took that at face value, which at the time was reasonable enough.
Then Community Crunch 505 landed on 2 May, and the tone changed. Wildcard said they'd "decided to prioritize stability over speed to protect the upcoming launch of Genesis Ascended Part 1 and ARK Tides of Fortune", pushed the target out to late Q3, and mentioned they'd hired a batch of senior Unreal Engine veterans (always a sign that something has been harder than expected) to get it over the line.
After that, sixteen weeks of silence on the engine. And then Community Crunch 520 on 22 August announced "the Unreal Engine 5.8 upgrade" for 30 September, with no mention of 5.7 anywhere in it and no explanation of the jump.
What's actually in the 30 September drop
Four things at once. The engine upgrade, the Therizinosaurus TLC (an Extra Life vote winner, so the Tickle Chicken finally gets its overhaul), Cerberax as the second creature in Fantastic Tames Season 1, and Gargantar, a Dragontopia dragon that Expansion Pass owners get early. Cerberax has three heads that apparently behave semi-independently, and does something extra when tribemates ride along, which is exactly the sort of thing I'd want to watch on a populated server before making any claims about it.
Read Wildcard's engine wording carefully though, because it's doing a lot of quiet work: "tangible performance improvements, platform-specific fixes, and stronger technical foundations for everything still ahead."
No percentage. Not one, anywhere in that announcement. In January they were happy to say 30-40%, and now they aren't saying anything numeric at all. That's a studio that learned something from quoting a figure eight months before shipping, and honestly, good. Plan for "faster", not for a number.
Why 5.8 is the better landing spot anyway
Epic shipped UE 5.7 in November 2025, and Nanite Foliage (the exact feature ARK cared about) shipped as experimental. Betting your live game's headline performance win on an experimental rendering path, on a game this size with this many mods hanging off it, is a very normal way to end up delaying twice. I suspect that's most of what "prioritize stability over speed" was actually about, though Wildcard have never said so and I'm reading tea leaves there.
UE 5.8 arrived on 17 June 2026, and Epic have described it as the last planned major Unreal Engine 5 release before the team moves on to UE6. So skipping straight there parks ASA on the terminal UE5 branch rather than on a waypoint it would only have to leave again in a year. For a game with a roadmap running well into 2027, that's the sensible place to sit.
What an engine upgrade actually did to ASA last time
Here's the part worth your attention. ASA has been through exactly one of these, it's thoroughly documented, and the documentation is far more useful than any amount of speculation about 5.8.
On 2 June 2025, the v66 patch moved ASA from Unreal Engine 5.2 to 5.5. (Our April piece said 5.4 to 5.5. It was 5.2: the patch notes are unambiguous about it.) Wildcard labelled the release "Major version for Servers and Clients", which is the phrase that should matter most to you. Clients update themselves the moment Steam pushes the build. Servers don't. Not unless you tell them to. Everybody caught in that gap gets a connection failure with nothing useful in the message, and if you run a community of any size, that gap is where your entire day goes.
Mods took the real damage, and Wildcard were unusually specific about it beforehand:
- Mod cooking stopped for about two weeks. The exact wording, from a Community Bite on 13 May 2025: "In preparation for ASA's Unreal Engine 5.5 update, we will temporarily pausing all new mod cooks/updates from the 20th of May. After that date, no new mods or mod updates will be possible until the 5.5 engine update patch releases." That freeze began thirteen days before the patch shipped. Nobody could push a fix during it, including the authors of whichever mods your server happens to depend on.
- Every ASA mod was recooked automatically by Overwolf (rather than each author rebuilding by hand), which was genuinely the good news. Wildcard said they'd verify every Premium Mod plus a sample of the most popular free ones, while warning plainly that "some of the thousands of mods may potentially have new functional issues".
- The recook wasn't a choice. In their words, the "Material system underwent such an overhaul from UE 5.1 to UE 5.5 that using the old precompiled cooked shaders was not an option."
They also said they'd try to avoid recooks on future upgrades, and that they wouldn't do full engine upgrades more than once a year. Whether they pulled off the first half of that for 5.8 is the biggest open question going into 30 September, and there's been no word either way. Treat "my mods will be fine because they said they'd try" as a hope rather than a plan.
One detail from 5.5 that people forget: the packaging changed too, with DLC maps becoming separately installable downloads. Engine upgrades move things on disk, not only in memory.
Saves are probably fine. Back them up anyway
The 5.2 to 5.5 jump was a major version bump for servers and clients and it did not touch save data. Nothing in the 30 September announcement mentions a save format change either. So the honest answer (and it is an answer, not a hedge) is that your world is very likely to come through untouched.
I still wouldn't run this without a copy sitting somewhere else. Before the patch, take the whole ShooterGame\Saved\SavedArks directory plus both files from ShooterGame\Saved\Config\WindowsServer (GameUserSettings.ini and Game.ini), and put them on something that isn't the server. A backup living on the box you're about to upgrade isn't a backup, it's a second copy of the same risk, and we've written at length about how that particular assumption tends to end.
The short list before the end of the month
Write your mod list down now. IDs and load order, in a plain text file you'll still be able to open if the server won't boot, which is precisely when you'll want it. You would be surprised how many admins can't reconstruct a twelve-mod stack from memory at midnight.
Turn off unattended auto-updates for the last week of September. You want to pick the moment this happens, rather than discover it at four in the morning from a player's DM.
Baseline something measurable while you're still on 5.5: tick rate through a normal busy evening, memory at peak, cold start time. Skip that and you'll come out the other side with opinions about whether 5.8 helped, instead of numbers.
Watch for a cook freeze announcement. Wildcard gave seventeen days' notice last time, so if the pattern repeats, something around mid-September is your cue to finish any mod business early rather than late.
If you're self-hosting, the dedicated server is its own Steam tool, app ID 2430930, and it's Windows only:
steamcmd +login anonymous +app_update 2430930 validate +quit
There's a public_test_realm branch on both the game and the server app. Worth knowing it exists, but I checked on 24 August and the server app's PTR build was sitting well behind its own public branch, so it isn't a preview channel you can lean on right now. Check again nearer the date. If you've never stood one of these up from scratch, our ARK dedicated server guide walks through the shape of it, though note that one's written for Survival Evolved, so the app ID and the launch arguments differ.
What day one will probably look like
Slow, then fine, in that order. A drop this size hits PC, Xbox and PlayStation together, and the first few hours are mostly Steam's CDN buckling under everyone downloading at once, which reads exactly like your server being broken and isn't.
Your mods will lag behind the client. Assume a few days of a partially broken list even in the good case, and resist the urge to reinstall things to fix it: a mod that hasn't been recooked yet does not become recooked because you reinstalled it. Run vanilla for an evening if you have to. That's far less painful than debugging eleven mods at once while people are trying to play.
And if the date moves, don't act surprised. UE 5.5 was targeting April-May 2025 and landed on 2 June. UE 5.7 targeted March, then April, then late Q3, and then turned into 5.8. Genesis Part 1 was announced for 25 June and shipped on 3 July. Wildcard ship good things late with enough consistency that you should build a week of slack into whatever downtime window you promise your players.